Re: [android-kernel] Re: Flashing Kernel Image

2010-02-22 Thread Tirtha Kanti Ghosh
you can try installing busybox on your Android FS and run all those commands(insmod, rmmod and many more) that are not provided in Android shell. to install busybox follow these steps mentioned in http://omappedia.org/wiki/Android_Getting_Started#Installing_Busybox_Command_Line_Tools_.28Optional.2

[android-kernel] Re: Flashing Kernel Image

2010-02-21 Thread perumal316
Yes, I just need to plug in the phone to the PC and do adb shell. Thanks for the tip! On Feb 19, 9:07 am, Chew Esmero wrote: > You can still use the adb shell. > > On Feb 18, 11:41 am, perumal316 wrote: > > > Hi, > > > Thanks for the tips, will try them out! The reason why I want to > > modify

[android-kernel] Re: Flashing Kernel Image

2010-02-18 Thread Chew Esmero
You can still use the adb shell. On Feb 18, 11:41 am, perumal316 wrote: > Hi, > > Thanks for the tips, will try them out! The reason why I want to > modify the kernel is to enable modules loading/unloading in Android > Developer Phone. > > Is there any way to load/unload modules in the Android De

[android-kernel] Re: Flashing Kernel Image

2010-02-17 Thread perumal316
Hi, Thanks for the tips, will try them out! The reason why I want to modify the kernel is to enable modules loading/unloading in Android Developer Phone. Is there any way to load/unload modules in the Android Developer Phone? In emulator it can be done through the adb shell. But suppose I have a

[android-kernel] Re: Flashing Kernel Image

2010-02-17 Thread perumal316
Hi, Thanks for the tips, will try them out! The reason why I want to modify the kernel is to enable modules loading/unloading in Android Developer Phone. Is there any way to load/unload modules in the Android Developer Phone? In emulator it can be done through the adb shell. But suppose I have a

[android-kernel] Re: Flashing Kernel Image

2010-02-16 Thread Chew Esmero
what I did to speed up development was, instead of building the source everytime (1.5 hrs in my pc), I'll just make another boot.img with my compiled kernel. boot.img contains the boot header, kernel image, ramdisk, and other stuff. To make the new boot.img, issue the "mkbootimg --cmdline 'no_conso