Date: Mon, 10 Nov 2003 13:19:12 +0100 From: Bernd Walter <ticso@cicely12.cicely.de> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: Pav Lucistnik <pav@oook.cz> Subject: Re: New EHCI device ID Message-ID: <20031110121911.GL16726@cicely12.cicely.de> In-Reply-To: <20031110100320.1189515c.Alexander@Leidinger.net> References: <200311091924.hA9JOP7G073292@Andro-Beta.Leidinger.net> <20031109212217.GF16726@cicely12.cicely.de> <1068418579.1822.13.camel@hood.oook.cz> <20031109231136.GI16726@cicely12.cicely.de> <20031110100320.1189515c.Alexander@Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 10, 2003 at 10:03:20AM +0100, Alexander Leidinger wrote: > On Mon, 10 Nov 2003 00:11:37 +0100 > Bernd Walter <ticso@cicely12.cicely.de> wrote: > > > On Sun, Nov 09, 2003 at 11:56:19PM +0100, Pav Lucistnik wrote: > > > It's that easy? Just adding device ID? I was under impression that you > > > need to write/modify a driver for a new chip. > > > > Adding the ID is just beautifying the boot messages. > > EHCI controllers are all compatible (modulo bugs) from the software > > point of view. > > We have a problem then. Normally this is a headless system, but I had a > mouse attached once and it caused a hard hang. Something with "int 10" > or too much interrupts or something like this (the mouse works on my > desktop system and it works on the machine in question in Windows). When > I test the new apic code on this system, I will attache a mouse again > and report back. I really doubt that you have a high speed mouse. EHCI only supports high speed devices itself. -- 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?20031110121911.GL16726>