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_at_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_at_bwct.de info_at_bwct.deReceived on Sun Nov 09 2003 - 14:11:50 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:28 UTC