Re: [linux-usb-devel] Via VT6202 problem

2004-12-16 Thread Thomas Dodd
David Brownell wrote: On Monday 13 December 2004 12:10 pm, Thomas Dodd wrote: Did some more digging. Built 2.6.9-1.6_FC with CONFIG_USB_DEBUG=y and ehci_hcd :00:08.2: init command 010009 (park)=0 ithresh=1 period=256 RUN ehci_hcd :00:08.2: USB 2.0 enabled, EHCI 0.95, driver 2004-May-10 ehc

Re: [linux-usb-devel] Via VT6202 problem

2004-12-16 Thread David Brownell
On Monday 13 December 2004 12:10 pm, Thomas Dodd wrote: > > Did some more digging. Built 2.6.9-1.6_FC with CONFIG_USB_DEBUG=y and > found an older 2.6.5-1.358 kernel. > > With the 2.6.5 kernel, I still see: > ehci_hcd :00:08.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Dec-29 > hub 1-0:1.0: ov

Re: [linux-usb-devel] Via VT6202 problem

2004-12-16 Thread Thomas Dodd
Thomas Dodd wrote: David Brownell wrote: On Monday 06 December 2004 11:53 am, Thomas Dodd wrote: It loads, the I get: ehci_hcd :00:08.2: USB 2.0 enabled, EHCI 0.95, driver 2004-May-10" hub 1-0:1.0: USB hub found hub 1-0:1.0: 4 ports detected ehci_hcd :00:08.2: fatal error ehci_hcd :00:

Re: [linux-usb-devel] Via VT6202 problem

2004-12-15 Thread Thomas Dodd
David Brownell wrote: On Tuesday 14 December 2004 12:40 pm, you wrote: Should I try removing the changes in ehci-hcd.c that is marked "turn off port power on all root hub ports" then? Or maybe it the writel(0,&ehci->regs->inter_enable) call after the ehci_reset() there? Maybe just disable key ch

Re: [linux-usb-devel] Via VT6202 problem

2004-12-07 Thread Thomas Dodd
David Brownell wrote: On Monday 06 December 2004 11:53 am, Thomas Dodd wrote: Where can I find a list of problems with the VT6202? VIA hasn't been forthcoming ... we can do no better! :) I mean know issues with the VIA chip and the linux driver. The current mailing list isn't the most searchable,

Re: [linux-usb-devel] Via VT6202 problem

2004-12-07 Thread David Brownell
On Monday 06 December 2004 11:53 am, Thomas Dodd wrote: > > Where can I find a list of problems with the VT6202? VIA hasn't been forthcoming ... we can do no better! :) The main issue I've had with it has been timing-related problems, related to queue processing, and a patch I'll post later tod