On Tuesday 03 May 2005 8:41 am, Doug Maxey wrote: > > > >The handoff between EHCI to its companion controller is controlled > >in the EHCI root hub code, by setting the OWNER bit. The hardware > >handles the rest. > > So when the ehci driver is available (loaded), it always takes first > shot at the ports, correct?
So long as it's bound to the relevant controller, yes. > >> What type of output would you like to see to show this? I don't have > >> anything captured at the moment, but I should be able to get to a system > >> to reproduce this on. > > > >I'm not clear what "this" is. The usual rule of thumb is to enable > >CONFIG_USB_DEBUG and show the relevant enumeration events, from "dmesg". > > Ok. I should confess the folks that are seeing the problem at the nonce > are doing some other "under the covers" things (bus_remove_device()) > before reading the device registers, and seeing unexpected results. That's not generally a good idea. Why do that? > After a while, it appears ehci attempts to take over permanently, > and resets the port registers to show the full complement of 15 ports, > which are not really available. As if maybe something's putting the device into some PCI power state other than D0, for one possibility. - Dave > I will get some more detailed information. ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
