Date: Mon, 10 Nov 2003 00:11:37 +0100 From: Bernd Walter <ticso@cicely12.cicely.de> To: Pav Lucistnik <pav@oook.cz> Cc: Alexander Leidinger <netchild@Leidinger.net> Subject: Re: New EHCI device ID Message-ID: <20031109231136.GI16726@cicely12.cicely.de> In-Reply-To: <1068418579.1822.13.camel@hood.oook.cz> References: <200311091924.hA9JOP7G073292@Andro-Beta.Leidinger.net> <20031109212217.GF16726@cicely12.cicely.de> <1068418579.1822.13.camel@hood.oook.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > In that case I'm here with my own motherboard: > > ehci0: <EHCI (generic) USB 2.0 controller> mem 0xdffeff00-0xdffeffff irq 21 at device 16.3 on pci0 > ehci0: (New EHCI DeviceId=0x31041106) > > ehci0@pci0:16:3: class=0x0c0320 card=0x71201462 chip=0x31041106 rev=0x82 hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT6202 USB 2.0 Enhanced Host Controller' > class = serial bus > subclass = USB > > But not that it does not work correctly ATM. USB2 devices have problems attaching. That must be for a different reason. > I'm willing to test any patches you can come up with. Well - I need to see the errors first :) -- 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?20031109231136.GI16726>