Sorry for asking the question without checking archives. I answered my own question by looking at other posts in the archives. I should be renaming the bzImage as kernel when I copy to vendor/asus/eee_701 for the newly compiled kernel to take precedence. Thats what I was doing wrong.
Regards, Gani On Apr 22, 8:38 am, Gani Bhagavathula <[email protected]> wrote: > Avtar: > > That is a good question. I have since realized that the kernel binary > is not getting updated at all. Which is probably why the > installer_img is not being built again. > > Am I missing a step after building the new kernel with 'make > bzImage'? I just copy the bzImage file into the vendor/asus/eee_701 > directory as bzImage and then try the compile. Should I be renaming > the bzImage as 'kernel' before trying? > > Regards, > Gani > > On Apr 21, 9:36 am, Avtar Singh <[email protected]> wrote: > > > > Where am I going wrong? > > > You are not going anywhere. It is the way dependencies have been set in the > > makefiles. But your installer_img should have built again without you having > > to compile everything again. > > > I am trying to find out if there is a way to do this in a shorter time> to > > incorporate just the new bzImage, rather than compile everything > > > again? > > > Can you check the timestamps of old and new kernel binaries in > > vendor/asus/eee_701. Is the new kernel binary having a newer timestamp? > > > - Avtar --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
