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.
Hmm? They _do_ work, else "usbnet" would never bind and you'd never be able to talk to your Zaurus. And you confirmed that it does work with your Zaurus, once it's loaded into the kernel.
Your problem is only that "hotplug" won't "modprobe usbnet". It's simple to work around this in config files, pending a deeper fix.
I didn't have to blacklist CDCEther because I never compiled it.
Which is part of why your patch seemed like "enough" to you.
The more severe problem is that on normal systems (distros) hotplug loads CDCEther, and the kernel will happily bind that to Zaurus hardware -- which can't talk to CDCEther! So you can't connect both a Zaurus and a real CDC Ethernet device to the same 2.4 system at the same time, and talk to them. Your patch doesn't affect that more serious problem at all.
Any full solution must solve both problems. That's why I had mentioned 2.6, which does solve them. And that's why I suggested you stick to user mode workarounds until a real fix is available; ideally one that works like 2.6 does, that'll be the least work all around.
- Dave
------------------------------------------------------- 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
