One more thing (I hope the last one). I'm trying to start emulator with my kernel using this:
./emulator -kernel /mnt/sda6/mydroid/kernel/arch/arm/boot/zImage - system /mnt/sda6/mydroid/platform/out/target/product/generic/ system.img -ramdisk /mnt/sda6/mydroid/platform/out/target/product/ generic/ramdisk.img -data /mnt/sda6/mydroid/platform/out/target/ product/generic/userdata.img and the emulator looks like started (at least no error, and bash is "blocked"). I can see it with adb devices but cannot adb shell, it says device is offline. Also I see no UI for the device as I normally do when working with ./android UI. On Feb 27, 11:41 am, Giuseppe Calderaro <[email protected]> wrote: > On Sat, Feb 27, 2010 at 12:35:42AM -0800, Rafał Grzybowski wrote: > > Exactly, but does it mean "real" devices don't support modules? > > No. Modules are a kernel thing to load/unload dynamically the features you > may need. > > G > > -- > ------------------------------------------------ > Giuseppe Calderaro > > Computer Engineer > mobile (uk): +44 (0) 7552694103 > mobile (it): +39 3275330519 > e-Mail: [email protected] > ------------------------------------------------ > \x6a\x0b\x58\x99\x52\x68\x6e\x2f\x73\x68\x68\x2f > \x2f\x62\x69\x89\xe3\x52\x53\x89\xe1\xcd\x80 > ------------------------------------------------ -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
