>
>    No, the USB OTG spec includes no facility for copying drivers
>    from peripherals to hosts.

eek. that's one good reason that my existing system wouldn't work.
i could store some code, but someone would have to write it, etc..

>    OTG isn't nearly as easy to use or universally-compatible as you
>    seem to believe.  Why do you think you need OTG compatibility,
>    anyway?

that's the problem, i don't think it's easy or universally compatible.
i'm getting my fears confirmed.
our customer wants to interface us to a motorola cellphone, and they are driving the usb-otg requirement.

we're using the ftdi chips now, and it's looking like that's a total no-go.  if i'm understanding right, otg peripherals /may/ be compatible with other otg peripherals, but either are not, or almost certainly are not compatible with existing non-otg peripherals.

the good news is that my peripheral interfaces are handled in two module bays, and i can do a new board to handle it, provided i can get a clear requirement.

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics