Thread: Hardware OTG support
View Single Post
Old 08-13-2012, 12:14 PM   #23
geekmaster
Всё гениальное просто.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 5,070
Karma: 6789001
Join Date: Nov 2011
Location: Щедрость не имеет пределов.
Device: *.*
Quote:
Originally Posted by hawhill View Post
... I think it is only recognizing one USB bus, and I think that would probably be the host-mode bus that's used for e.g. driving the 3G modem (at least on older Kindle models, that was the case). Something must be triggered to present the other USB interface as a Host, too, so the fsl-ehci driver could care for it.
That seems to agree with what I found in an old MobileRead thread, where they mostly decided that the built-in USB gadget drivers were manipulating the INTERNAL USB instead of the external USB port. In which case things become even MORE "non-trivial", requiring solutions similar to what they used to get this stuff working on the Nook Simple Touch.

The "something must be triggered" is probably what the custom Nook Simple Touch program did to configure the external port for OTG. That is why I added that program to the (non-trivial) list of things that may be needed in my earlier post.

Last edited by geekmaster; 08-13-2012 at 12:22 PM.
geekmaster is offline   Reply With Quote