It seems that the kernel that comes with the eee_701 port is based on 2.6.25 while the sources are based on 2.6.27. I also noticed that the kernel.config in vendor/asus/eee_701 is not exactly the config file used when building the 2.6.25, for example the i915 and drm driver aren't enabled there.
My questions: where can I gate the 2.6.25 sources with all the patches and the correct config ? so that I'll be able to compile the same kernel. Is there a correct config file for the 2.6.27? -md On Mar 23, 6:14 pm, Yi Sun <[email protected]> wrote: > You can copy kernel.config from vendor/asus/eee_701 to kernel/.config and > run make menuconfig/make bzImage. > > On Mon, Mar 23, 2009 at 12:43 AM, Avtar Singh <[email protected]> wrote: > > I can build Android for x86-EeePC using the steps listed in the following > > posts (thanks to Chen and everyone else). I am also able to launch Android > > in a VirtualBox virtual machine. > > >http://groups.google.com/group/android-porting/msg/2dedc5fe7ad58ed3?p... > > Installation in VMWare: > >http://groups.google.com/group/android-porting/msg/fe85782f1bc3ad2f > > Installation in VirtualBox: > >http://groups.google.com/group/android-porting/msg/32b3709b4ae4f1d5 > > > I would now like to patch the kernel code and generate a new bzImage. I > > understand that the new binary can be copied to vendor/asus/eee_701/kernel > > and the installer image can be regenerated. However, what is the right way > > to generate the new bzImage for x86 using the toolchain provided by > > prebuilt/linux-x86/toolchain/i686-unknown-linux-gnu-4.2.1 and bionic > > headers? > > > Thanks. > > > - Avtar --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
