On Mon, Nov 24, 2003 at 06:43:31PM -0800, David Brownell wrote:
> For now I'd plan on adding Zaurii to /etc/hotplug/usb.usermap to get
> systems working with no kernel changes. Just like you presumably
> added CDCEther to /etc/hotplug/blacklist ... Zaurus "proprietary"
> protocols made a mess. It's much better in 2.6 (CDCEther gone).
That doesn't make sense. There are Zaurus specific additions to
usbnet.c They don't work. They should either be fixed or removed.
I'm not talking about generic class maching here, there are entries
for these specific devices:
#ifdef CONFIG_USB_ZAURUS
/*
* SA-1100 based Sharp Zaurus ("collie"), or compatible.
* Same idea as above, but different framing.
*/
{
.match_flags = USB_DEVICE_ID_MATCH_INT_INFO
| USB_DEVICE_ID_MATCH_DEVICE,
.idVendor = 0x04DD,
.idProduct = 0x8004,
.bInterfaceClass = 0x0a,
.bInterfaceSubClass = 0x00,
.bInterfaceProtocol = 0x00,
.driver_info = (unsigned long) &zaurus_sl5x00_info,
}, {
...
So there are entries in modules.usbmap that don't work and yes I fixed
them first. But to avoid having to repeat that every time I recompile
the kernel, and to try and help others, I tracked down the source in
usbnet and changed that (per the diff I submitted earlier, I removed
USB_DEVICE_ID_MATCH_INT_INFO)
I didn't have to blacklist CDCEther because I never compiled it.
--
Don Reid
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
