On Monday 02 August 2004 14:22, Todd Fischer wrote: > My understanding is that if I want to support USB OTG, I need 3 hardware > specific pieces: USB host support (subset), USB device support, and a few > routines that allow the hardware to switch host/device roles as specified in > the USB OTG specification.
Those "few routines" can actually be tricky, especially HNP. Are you using an external transceiver? > I suspect that since most hardware supports one of the *hci standards, there > isn't much development activity related to creating hci drivers that touch > the hardware. Because of this, I haven't found much information. That's part of why. Another part is that in 2.6 we're only now starting to get to the "functionally complete" milestone, and the code has sort of evolved. Merging usb_bus and usb_hcd into one thing (usb_host?) has seemed like a 2.7 project for someone. > I believe the hardware I am using is capable of supporting full USB host > functionality. Is the best approach to develop a USB host driver using the > SL811 as a model or is there a simpler way (which doesn't require the > "virtual root hub" logic found in the SL811)? You'll need a virtual root hub, regardless, unless you want to rewrite big chunks of usbcore. Given the problems folk have had, I'd suggest using OHCI as your model. Unless you're talking about a pure PIO controller (no DMA)? SL811 does PIO, as does dummy_hcd. - Dave ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
