[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171002.161750.1123671129875495210.davem@davemloft.net>
Date: Mon, 02 Oct 2017 16:17:50 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: aleksander@...ksander.es
Cc: oliver@...kum.org, linux-usb@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH] rndis_host: support Novatel Verizon USB730L
From: Aleksander Morgado <aleksander@...ksander.es>
Date: Wed, 27 Sep 2017 23:31:03 +0200
> I'm not sure if binding this logic to a specific vid:pid (1410:9030)
> would be more appropriate here, or if it's ok to just bind
> class/subclass/protocol (as in the activesync case). Let me know
> what you think.
I don't have enough USB Networking knowledge to make a decision here.
Some things seem confusing. For example, if we should be matching
USB_CLASS_MISC, subclass=4, protocol=1 for RNDIS over Ethernet, then
we why aren't we also matching USB_CLASS_MISC, subclass=4, protocol=2
for RNDIS over wireless and instead are matching "Remote RNDIS" in
the form of USB_CLASS_WIRELSS, subclass=1, protocol=3?
I really don't understand any of this magic :-)
So someone more knowledgable needs to review this.
Powered by blists - more mailing lists