From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problem with hotplug-2001_01_16 + quick solution
Date: Tue, 23 Jan 2001 16:14:05 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98026647526226@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98014154830651@msgid-missing>
Martin --
Thanks for that problem report for 2.2 hotplugging!
> My USB mouse (Genius Netmouse Pro) has PRODUCTE8/2/0.0
^^^
> (DEVICE=/proc/bus/usb/001/002, INTERFACE=3/1/2, TYPE not set)
> in kernel 2.2.19pre6, so usb.agent aborts its execution
> in usb_convert_vars function. In the kernel 2.4.0 it is OK.
Greg, that looks like hotplug in 2.2.* needs to get a bugfix
from a few months back -- changing the product version code
to be straight hex, not a BCD-ized string. Can you get that
fix to Alan? (A case of ripping out ugly to_bcd code ... :-)
> With modutils 2.4.1 the file /lib/modules/`uname -r`/modules.usbmap
> exists even in the 2.2 kernel, but contains only one line, so usb.distmap
> is not used.
Looks like modutils is not going to ensure that file only exists
on kernels that support MODULE_DEVICE_TABLE sections in dynamically
linked modules. I'll check in a fix (this AM) that will test the
kernel version.
(So Keith, that means you needn't bother tweaking modutils to
avoid generating empty "modules.usbmap" files.)
For the record, I hate testing software version stamps, because
that's known to be a fragile scheme. Feature tests are reliable,
but we don't seem to have a way to test "do modules on this system
support MODULE_DEVICE_TABLE" -- so "is kernel version 2.4/2.5/..."
is the best heuristic I can identify.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-01-23 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-22 5:31 Problem with hotplug-2001_01_16 + quick solution Martin Volf
2001-01-23 16:14 ` David Brownell [this message]
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-98026647526226@msgid-missing \
--to=david-b@pacbell.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.