Hi!
> > The obvious change with this device is that usb_set_configuration() is never
> > called, but that should not matter.
>
> No, I think you're barking up the wrong tree.
>
> Pavel, did you have CONFIG_USB_MULTITHREAD_PROBE turned on? I bet you did
> -- there's no other way to generate the messages in your syslog.
Yep, you are right.
> Don't use that kconfig option. It's broken (as you saw) and needs to be
> either removed or replaced.
Perhaps it should be disabled before 2.6.20? This is actually
regression...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
