Re: 2.6.9-rc2-mm2 ohci_hcd doesn't work

[David Brownell]

On Thursday 23 September 2004 1:57 pm, Bjorn Helgaas wrote:
> 
>  ACPI: PCI interrupt 0000:00:0f.2[A] -> GSI 10 (level, low) -> IRQ 10
>  ohci_hcd 0000:00:0f.2: ServerWorks OSB4/CSB5 OHCI USB Controller
>  ohci_hcd 0000:00:0f.2: irq 10, pci mem 0xf5e70000
>  ohci_hcd 0000:00:0f.2: new USB bus registered, assigned bus number 1
>  ohci_hcd 0000:00:0f.2: init err (00002edf 0000)

The "2edf" is fine but the "0000" isn't what was _just_ written
to that second register ... some chips are a bit tricky about
initialization.  Ideally, OHCI_QUIRK_INITRESET would be set
for those chips ... the need for that is new, Linux previously
did it in all cases even though only a few implementations
seemed to want it.  (And some strongly dislike it.)

Maybe ServerWorks needs it.  The flag is tested in ohci-hcd.c;
what happens if you kick in that quirk handling?

- Dave

>  ohci_hcd 0000:00:0f.2: can't start
>  ohci_hcd 0000:00:0f.2: init error -75
>  ohci_hcd 0000:00:0f.2: remove, state 0
>  ohci_hcd 0000:00:0f.2: USB bus 1 deregistered
>  ohci_hcd: probe of 0000:00:0f.2 failed with error -75

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/