2009-12...@20:45 Alex (Maxious) Sadleir > You should explain why you need to do this. I would think any device > that communicates with an MTP device would also be willing to > communicate with a mass storage device. The moko can pretend to be a > mass storage device (like a USB hard drive) under certain conditions - > http://wiki.openmoko.org/wiki/Using_the_Neo_as_an_USB_Mass_storage_device >
configure moko's usb to act as a MTP responder device is better than usb mass storage class because the file system is _NOT_ "owned" by the host and thus the device itself can for example add, remove, play or rename files during this time without risking corruption of the file system also, it's possible to keep any filesystem eg ext2 or reiser or *** and still being readable from anyone compatible with MTP with mass storage class you should have a dedicated fat partition if you like to be readable all around and while connected with usb you cannot even only read your files in openmoko! also, I'd like to encrypt the fsystem on my sd card, so if you remove it from my moko you have to enter the key. if you encrypt it and use mass storage class, you have to install a compatible decipher on every host you want to connect your moko to. (and maybe you just want to give a file to a friend, once) I'd like to develop a simple tool for shr to configure and manage this task because imho it could be of some use for many people in my situation, but I'm not able to find any doc about configuring linux in general as a mtp responder -- ALFA21 IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
