Le dimanche 18 juin 2006 à 10:37 -0700, David Brownell a écrit : > On Sunday 18 June 2006 9:56 am, Frédéric Riss wrote: > > The errors I reported are during a boot sequence, not only > > during resume, so I doubt the missing handlers are the causes for them. > > That was unclear from what you wrote before... $SUBJECT talks > about remote wakeup/resume, not booting.
Well, my first mail that got no response was only about remote wakeup, but then I noticed these errors on the same USB hub that the wakeup device that I've trouble with. I think I mentioned that the errors appeared on boot and resume in the second mail. > > However missing or wrong handlers could break the remote wakeup > > capability for this hub, couldn't it? > > Think of Linux as a stage act with lots of closely coordinated > singing and dancing penguins. Then one of the penguins trips, > and knocks down all penguins on stage right, sort of like a > game of dominos. Sure the audience laughed ... but this wasn't > supposed to be that kind of play! :-) Yeah, that's what I noticed. In the past days, I've begun to read the various USB specs and tried to map that on the kernel code that handles it. Tricky. I've especially a hard time with the relationship between HCI, HID. I don't really get how the fact of loading hci_usb brings up two new HID devices on the corresponding USB hub. Fred. _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
