Date: Mon, 10 Nov 2003 10:03:20 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: ticso@cicely.de Cc: Pav Lucistnik <pav@oook.cz> Subject: Re: New EHCI device ID Message-ID: <20031110100320.1189515c.Alexander@Leidinger.net> In-Reply-To: <20031109231136.GI16726@cicely12.cicely.de> References: <200311091924.hA9JOP7G073292@Andro-Beta.Leidinger.net> <20031109212217.GF16726@cicely12.cicely.de> <1068418579.1822.13.camel@hood.oook.cz> <20031109231136.GI16726@cicely12.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Bye,
Alexander.
--
"One world, one web, one program" -- Microsoft promotional ad
"Ein Volk, ein Reich, ein Fuehrer" -- Adolf Hitler
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031110100320.1189515c.Alexander>