From: David Miller <davem@davemloft.net>
To: bjorn@mork.no
Cc: aleksander@aleksander.es, oliver@neukum.org,
linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] rndis_host: support Novatel Verizon USB730L
Date: Tue, 03 Oct 2017 14:31:31 -0700 (PDT) [thread overview]
Message-ID: <20171003.143131.650875825854523184.davem@davemloft.net> (raw)
In-Reply-To: <87k20cmitw.fsf@miraculix.mork.no>
From: Bjørn Mork <bjorn@mork.no>
Date: Tue, 03 Oct 2017 16:01:15 +0200
> We can pretty much ignore the USB-IF and any specs, since that is what
> the vendors appear to do. They provide device specific drivers for
> Windows, so all they care about is that their device "works" with their
> driver.
>
> But in Linux we prefer to create drivers for device classes whenever we
> can, to avoid having to add every single device by ID. So we try to
> guess future patterns based on the devices we have observed, even when
> there is no clear spec. This is what Aleksander does here. He has a
> device with a 'Cls=ef(misc ) Sub=04 Prot=01' function. This device
> works with the rndis_host driver. That is all we know.
>
> We cannot prove that a class match is correct. But it does make sense to
> try it. At least we know that this works for one device.
>
> Adding anything else, e.g. based on the table at
> http://www.usb.org/developers/defined_class/#BaseClassEFh , is a bit
> more risky. We don't know if a driver will work with *any* such device
> until we've actually seen one.
>
> This is just my opinion, and probably full of bogus assumptions as
> usual. I was sort of hoping that some expert would speak up so I didn't
> have to :-)
Ok ;-)
> But FWIW:
>
> Reviewed-by: Bjørn Mork <bjorn@mork.no>
So I'll apply this for now, thanks for your feedback.
next prev parent reply other threads:[~2017-10-03 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 21:31 [PATCH] rndis_host: support Novatel Verizon USB730L Aleksander Morgado
[not found] ` <20170927213103.11987-1-aleksander-Dvg4H30XQSRVIjRurl1/8g@public.gmane.org>
2017-10-02 23:17 ` David Miller
[not found] ` <20171002.161750.1123671129875495210.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-10-03 14:01 ` Bjørn Mork
2017-10-03 21:31 ` David Miller [this message]
2017-10-04 10:44 ` Oliver Neukum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171003.143131.650875825854523184.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aleksander@aleksander.es \
--cc=bjorn@mork.no \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).