tech-kern archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: uhci on non-x86
I guess we're talking about two different problems. People here are
talking about hangs, i/o errors, and the like. What I've seen is a silent
failure. That is, I write to a flash card on a port connected to ehci0,
and all appears to work fine. Then, I unmount the flash card, remount the
card, and compare the contents of the newly remounted card with what I
wrote initially. The contents now differs, meaning the contents of the
flash card are corrupt. If I take the same flash card and write it on a
port connected via uhci or ohci, it works fine, meaning I can unmount it,
remount it, and the contents are correct. I've seen this on a number of
ehci chips, Nvidia, Intel, and Via, I think. My most recent experience is
with Nvidia on NetBSD-4.x sources. I think it's an old bug, though,
because I saw it on NetBSD-3.x sources as well.
-Brian
On May 16, 3:36pm, Rhialto wrote:
} Subject: Re: uhci on non-x86
} On Wed 14 May 2008 at 10:45:12 +0200, Anders Lindgren wrote:
} > FWIW, I can at least confirm that..
} >
} > ehci0 at pci0 dev 11 function 1: NVIDIA nForce4 USB2 Host Controller
} > (rev. 0xa4)
} >
} > on NetBSD 4.0 (GENERIC.MP) is utterly, utterly broken. The motherboard in
} > that box is an ASUS A8N32-SLI Deluxe. Connecting any kind of umass device
}
} And strangely enough, on my box with an ASUS A8V DeLuxe, this one works
} just fine with 4.0:
}
} ehci0 at pci0 dev 16 function 4: VIA Technologies VT8237 EHCI USB Controller
(rev. 0x86)
} ehci0: interrupting at ioapic0 pin 21 (irq 5)
} ehci0: BIOS has given up ownership
} ehci0: EHCI version 1.0
} ehci0: companion controllers, 2 ports each: uhci0 uhci1 uhci2 uhci3
} usb4 at ehci0: USB revision 2.0
}
} although a similar other motherboard at work, with afaik the same
} chipset but different mobo manufacturer, causes a hang during autoconfig
} if ehci is probed. I had to restrict it to uhci only (either by kernel
} config or by disabling ehci in the BIOS setup) - and the UHCIs probe
} identically nearly (the irq differs) indicating the same chipset:
}
} mobo where ehci fails:
}
} uhci0 at pci0 dev 16 function 0: VIA Technologies VT83C572 USB Controller
(rev.
} 0x81)
} uhci0: interrupting at ioapic0 pin 21 (irq 12)
} usb0 at uhci0: USB revision 1.0
} uhub0 at usb0
} uhub0: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
} uhub0: 2 ports with 2 removable, self powered
} ...
}
} mine (working):
}
} uhci0 at pci0 dev 16 function 0: VIA Technologies VT83C572 USB Controller
(rev. 0x81)
} uhci0: interrupting at ioapic0 pin 21 (irq 11)
} usb0 at uhci0: USB revision 1.0
} uhub0 at usb0
} uhub0: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
} uhub0: 2 ports with 2 removable, self powered
} ...
}
} The biggest differences between the mobos is probably the BIOS type and
} settings, and that on mine there are 4 DIMM slots rather than 3.
}
} -Olaf.
} --
} ___ Olaf 'Rhialto' Seibert -- You author it, and I'll reader it.
} \X/ rhialto/at/xs4all.nl -- Cetero censeo "authored" delendum esse.
>-- End of excerpt from Rhialto
Home |
Main Index |
Thread Index |
Old Index