Date: Mon, 10 Nov 2003 17:47:02 +0100 From: Bernd Walter <ticso@cicely12.cicely.de> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: current@freebsd.org Subject: Re: New EHCI device ID Message-ID: <20031110164701.GX16726@cicely12.cicely.de> In-Reply-To: <20031110163531.4441f094.Alexander@Leidinger.net> References: <20031109212217.GF16726@cicely12.cicely.de> <1068418579.1822.13.camel@hood.oook.cz> <20031109231136.GI16726@cicely12.cicely.de> <20031110100320.1189515c.Alexander@Leidinger.net> <20031110121911.GL16726@cicely12.cicely.de> <20031110135002.66055c17.Alexander@Leidinger.net> <20031110125538.GP16726@cicely12.cicely.de> <20031110155423.1bb0b145.Alexander@Leidinger.net> <20031110151927.GT16726@cicely12.cicely.de> <20031110163531.4441f094.Alexander@Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 10, 2003 at 04:35:31PM +0100, Alexander Leidinger wrote: > On Mon, 10 Nov 2003 16:19:27 +0100 > Bernd Walter <ticso@cicely12.cicely.de> wrote: > > > USB2 hubs are currently not supported with high speed uplinks. > > That's the reason why there is no EHCI support in GENERIC. > > EHCI needs interrupt transfers first to support usb2.0 hubs at high > > speed uplinks with high speed devices. > > For low and full speed downlink we additionaly need speed conversion > > support in uhub code. > > Is there an easy way of printing something like this instead of halting > the system? Don't know, but if I ever put time in that issue then by implementing the missing points and not by changing symptoms. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031110164701.GX16726>