EHCI considered harmful?

Tai-hwa Liang avatar at mmlab.cse.yzu.edu.tw
Mon Nov 1 06:41:10 PST 2004


On Sun, 31 Oct 2004, Ian Dowse wrote:
> In message <20041029123322.GA7181 at bingo.tenfour>, Dick Davies writes:
>> * Andre Guibert de Bruet <andy at siliconlandmark.com> [1026 11:26]:
>>> This is my understanding of the current state of our USB ehci support:
>>> ehci only works with certain chipsets. On the ones that it does work with,
>>> you do not want to have a USB2 hub connected (With ehci in your config) as
>>> it will not be supported. Removing ehci from your kernel lets you use a
>>> USB2 hub in 1.1 mode.
>>
>> Just thought I'd mention that netbsd CURRENT got usb2 hub support in its echi
>> driver last week. I don't know how easy a merge would be, but if anyone needs
>> usb2 hub support, might be worth a look.
>
> Yes, the basic usb2 hub support that was added to FreeBSD in August
> has recently looped around via OpenBSD to NetBSD and picked up some
> enhancements along the way (OpenBSD added improved suspend/resume
> support, and NetBSD have begun adding transaction translation
> support). There's a patch against FreeBSD -CURRENT at
>
> 	http://people.freebsd.org/~iedowse/usb2_sync.diff
>
> that attempts to sync up our USB stack to include the latest USB2
> changes from NetBSD. If you've been having trouble with EHCI it would
> be worth trying it.

   FWIW, I tried the patch on my Intel 865 box and still got sporadically
lockup at boot time....

 	http://lists.freebsd.org/pipermail/freebsd-current/2004-October/041783.html

   Not sure whether this is correlated to EHCI since it's also boot time 
locking up with corrupted OHCI version:

 	http://lists.freebsd.org/pipermail/freebsd-current/2004-October/039973.html


More information about the freebsd-current mailing list