From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Bug in USB Generic Serial driver
Date: Tue, 09 Jan 2001 07:11:35 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97902448220635@msgid-missing> (raw)
Hi all,
It seems that the last round of hotplug changes broke a few more things.
If you load (or compile in) the USB Generic Serial driver, it will
_always_ grab any device that it is offered, if the user does not
specify a product and vendor id for it on the 'insmod' command line.
This is because its vendor and product id are set to 0 initially, with
_no_ match_flags setting either. In the function, usb_match_id, a value
of 0 means accept any as a wild card.
So to fix this, either the Generic Serial driver can change its default
values to something like 0xffff for both the vendor and product id, or
we can change the usb_match_id function somehow, or something else?
I thought that the usb scanner driver would also have this problem, but
it looks like the ability to specify the vendor and product ids as a
module load parameter have been removed.
And I also don't like the ordering specificness of the new USB_DEVICE
macro, and liked the named initializers better, but can't think of a
better way to do it right this second.
Comments?
Thanks Randy, for pointing this problem out to me.
greg k-h
--
greg@(kroah|wirex).com
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2001-01-09 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 7:11 Greg KH [this message]
2001-01-09 8:09 ` Bug in USB Generic Serial driver Adam J. Richter
2001-01-09 15:37 ` Dunlap, Randy
2001-01-09 16:06 ` Matthew Dharm
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=marc-linux-hotplug-97902448220635@msgid-missing \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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).