David Brownell wrote: > On Thursday 07 December 2006 10:24 am, Geoff Levand wrote: > It'd be advantageous to (re)use the same driver glue. If it > weren't for the fact that each chip/system vendor ends up with > minor differences related to system integration, we could make > do with a lot fewer "ohci-XXX.c" bus glue components. But > having two (or three) for Cell seems excessive, especially > if they're all going to the same IOIF ohci controller...
Well yes, the underlying hardware is the same. But the firmware and/or hypervisor is different, and that is what dictates the interface, not the underlying hardware. >> > If it's a PCI device, I'd rather see it merge with a patch that >> > I will be resending, which will help make PCI quirks easier to >> > manage than just augmenting a big if/else tree. >> >> >> Yes, that is agreeable by me. As I said, Cell Blade represents it >> as a PCI device, but the PS3 does not, so my concern is that your >> new method won't work for me (PS3). Please let me know what you >> would like to do. > > Since your workaround is just to write some registers, I'd try > to do that in the PS3/CELLEB bus glue. But that won't work for Blade's PCI representation, which just uses the ohci-pci code will it? Unless, you see some way that I don't. Or, do you mean have three difffernet places where this fixup is done, one in your new PCI fixup, then two others in the bus glue components? -Geoff ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
