The simplest way for you to get those changes is to pull my gadget-2.6 tree. Alternatively take 2.6.1 and apply:
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107281400904072&w=2 http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107325845324500&w=2 http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107329882620130&w=2 http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107369460101804&w=2
I've tried it. It seems a bit better than the preceding situation (the kernel seems less confused) but it still does not work:
- after reset, the device changes its ID from 0763:2804 to 0763:2004 and this is not reflected in /proc/bus/usb/devices
Actually, that's a "device morphed" path which we still don't expect to work. You'll notice a big FIXME right at the end of that fourth patch, which is approximately where Alan was going to start adding goodness ...
- perhaps because of this change, we get weird things in lssub: cannot get string descriptor 1, error = No such device(19) cannot get string descriptor 2, error = No such device(19).
Sounds right. Previous device morphed into a new one. The kernel doesn't yet know how to handle that ... it can mark the old device gone, but can't clean it up or replace it.
- Dave
Regards,
David Monniaux http://www.di.ens.fr/~monniaux Laboratoire d'informatique de l'�cole Normale Sup�rieure, Paris, France
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
