Form datasheet: i.MX508 has USB OTG port and data in USB downloader mode could be transferred specifically and only through USB OTG port. Kindle Touch could be switched into USB downloader mode with successful data transferring through it's USB port. Ergo, KT's USB port is the USB OTG port. And USB OTG port can act as a host port.

Form datasheet: i.MX508 has USB OTG port and data in USB downloader mode could be transferred specifically and only through USB OTG port. Kindle Touch could be switched into USB downloader mode with successful data transferring through it's USB port. Ergo, KT's USB port is the USB OTG port. And USB OTG port can act as a host port.

I was referring to the HOST-ONLY mode available on the other USB pins, used for 3G. The external port is OTG, and can be switched between multiple modes. It may not have the connection needed to detect a host mode OTG cable, in which case you would need a software OTG mode-switch program (like the Nook Simple Touch hack uses).

With just a speed-read of the specs and without the required careful study...
It seems that it may be possible that one of these OTG devices can support only Device and Battery charging (I.E: might not be capable of supporting Host).

ref. OTG/host/usb stuff in general... the idea is cool enough but is it worth the effort? lots of software, etc. are needed and i think we can do more efficient. just modify my idea and add a bluetooth device instead of the sensor. then it would be truly wireless. i have already done something like this when i developed the "kindle touch personal weather station". i've hooked up a bluetooth module to "talk" to the kindle without wires - all for the sake of debugging. after i put everything together i just removed the bluetooth module and wired everything in side of the kindle. if it's of any interest i think i can put it all back together and publish it here. after all it was only a "serial bridge" using nothing but a bluetooth module...

ref. OTG/host/usb stuff in general... the idea is cool enough but is it worth the effort? lots of software, etc. are needed and i think we can do more efficient. just modify my idea and add a bluetooth device instead of the sensor. then it would be truly wireless. i have already done something like this when i developed the "kindle touch personal weather station". i've hooked up a bluetooth module to "talk" to the kindle without wires - all for the sake of debugging. after i put everything together i just removed the bluetooth module and wired everything in side of the kindle. if it's of any interest i think i can put it all back together and publish it here. after all it was only a "serial bridge" using nothing but a bluetooth module...

Just deal with the mechanical differences -
The indexed HowTo is for the DX(G) and posts to that thread show it has been tried on the K2 also.

My own first choice - use a ZigBee module (because I have them) -
Unlike Bluetooth modules, they are low enough power to be left on all of the time.
Like, months of run-time on a single 1.5v AAA sized battery. The Kindle's Li-Ion battery will "self discharge" faster than these ZigBee modules will run them down.

Just deal with the mechanical differences -
The indexed HowTo is for the DX(G) and posts to that thread show it has been tried on the K2 also.

My own first choice - use a ZigBee module (because I have them) -
Unlike Bluetooth modules, they are low enough power to be left on all of the time.
Like, months of run-time on a single 1.5v AAA sized battery. The Kindle's Li-Ion battery will "self discharge" faster than these ZigBee modules will run them down.

(Just have to find a place for it inside my K3)

which zigbee modules do you use/own? i have some low power bluetooth modules but i also want to try something new out like measuring distances with the help of the KT...

Then merge the changes into a 5 tree (with some judicious lookage before leapeage)
and shove it through buildroot as a patch for all 5'ish devices. (paperwhite 5.2 I'm looking at you)

Getting this procedure standardised in a simple "patch" (since we can affect the _def_config anyway before build in buildroot and provide our own) would make providing OTG USB a near-reality. Also the chances of someone actually doing some more work on the drivers would go up a great deal I would be bound.

So yeah. my thoughts.

Grab Git, Diff against a 4 clean, merge to a 5 src, build via BR.

Caveats anyone? please? Any patches out there for building the source that anyone knows of (obviously I'll try to search myself), fixes for name-space problems? anything?

I'm thinking I'll use the Linaro 2012.04 as that provides the route of least resistance for the average user.

For my money: think this goes on the RSN pile myself as the low-hanging fruit is far too juicy to let bit-rot on the vine...

Come on... external storage? games controllers? Keyboards? all pretty basic stuff that will fall in the "probably supported" category according to my reading of what is there right now.

Surely this is a must do. especially with the paperwhite bringing the lo-calorie pain in so many quarters.