I would recommend any of the Google devices. But you could always build out your own kernel for any device that you can flash (Google or HTC phones are easy) with the file system support you need compiled into the kernel or build it as a module and insmod it. You can get the kernel config file on some phones from the /proc/config.gz and use that as a base for configuring a custom kernel. I would recommend an HTC device and throw Cyanogenmod on it. I have come across some devices that have loadable module support turned off, so if your not putting a custom kernel on the phone, you won't even be able to load modules, however I have never found this to be true for a Google device.
On Jul 6, 7:48 am, Rado <andri...@gmail.com> wrote: > Hi everybody! > > I'm working on a kernel module for android. For now it works within an > emulator but I want to switch to a real device. > > What could be the best choice in your opinion? It was given to my > understanting that the kernel built for the emulator is specific so I > have to build an other for a real device. > > My first idea were an Android dev phone / Google Nexus S. > > I need to have ext2/3/4 file system for the device, Gingerbread and to > be able to build specific kernel for the device I will use. > > I made search on the net and it seems to me nexus s is a good (maybe > the best) choice. It uses ext4 file system and gingerbread, and > drivers are available here > :http://code.google.com/intl/fr/android/nexus/drivers.html#crespogrj22 > > Can you give me your opinions? > > I'm thinking of porting to a tablet too but there is no dev-tablet and > last time I check honey comb source was not yet released. > > Thanks, > > Rado -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
