EHCI USB MFC?
Bernd Walter
ticso at cicely12.cicely.de
Thu Feb 5 06:37:58 PST 2004
On Thu, Feb 05, 2004 at 06:39:42PM +1030, Daniel O'Connor wrote:
> On Thursday 05 February 2004 17:10, Julian Elischer wrote:
> > > > if not I will give it a try..
> > >
> > > Can it be fixed to work in -current first :-)
> >
> > huh? seemed to work for me when I tested it a few months ago..
There are conditions were EHCI don't work - in the same way as there
are still conditions were OHCI/UHCI don't work.
But it's not unsusual for say OHCI to work and EHCI not on the same
chip.
On the other hand EHCI is not complete - e.g. hub support is missing
and high speed hubs are quite common today, which is the may reason to
not have it in GENERIC.
Porting to -stable should basicly just MFC'ing the -current version and
taking care about the lockmgr usage - at least if lockmgr was not
already MFC'ed.
That said - I don't have stable test machine with required USB hardware
here, so it's up to someone else to do :)
> Well, my trackball works fine, but last time I tried a umass device it worked
> OK on a USB1 port but wouldn't talk on a USB2.0 port :(
>
> My pocket PC is very unreliable when connecting to my new laptop (USB2.0) but
> it was much more solid with my old (USB1.1) one..
PR?
> That said, I guess you can always disable ehci if it's a problem :)
You don't have to enable ehci if its a problem :)
--
B.Walter BWCT http://www.bwct.de
ticso at bwct.de info at bwct.de
More information about the freebsd-current
mailing list