I should clarify that by "most arm distributions" I mean most by
installed base - ie, the locked-down consumer oriented ones.

Probably if your time is worth anything and you want to do this, you
would be better off with a beagle board than trying to adapt the
emulator to proxy your pc's USB ports so you can test drivers against
hardware.

On Jan 15, 10:15 am, Chris Stratton <[email protected]> wrote:
> While noble, that sounds like an ambitious project at a time when most
> arm distributions of android aren't AFAIK shipping with an enabled USB
> host mode, or a way for users to gain permission to load kernel
> modules.
>
> To really test your drivers it may be necessary to find hardware or
> make massive modifications to the emulator.  But just making sure your
> code will compile, and having it well documented (along with any
> quirks of the USB peripheral) would put someone in a position to try
> building the driver for their arm-based android device in a good
> position.
>
> On Jan 14, 12:20 am, sugnan prabhu <[email protected]> wrote:
>
> > Hello People,
>
> >           I have written few usb drivers for android which works fine on the
> > android-x86 (tested using virtualbox), now i want to test the same for
> > android-arm using android emulator. I have built the android for arm
> > including my usb drivers, but there is no support for the usb connectivity
> > on android emulator, so can some one give some pointer how can i add the usb
> > support for it. If any one with the knowledge on this stuff, please suggest.
>
> >           I thought of using qemu directly instead of emulator, but misses
> > lot of android hardware support, i want to contribute this for the android
> > opensource, some one give me some pointers.
>
>

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-kernel

Reply via email to