Thanks for the reply, shall I compile a msi specific kernel in the kernel directory then copy that over to vender/eee_pc directory and when android compile it'll use that kernel? or have I mis-understood?
On Jan 7, 12:13 am, "Dima Zavin" <[email protected]> wrote: > You are using an eeepc specific target, which is why you are getting the > eeepc kernel/drivers. > > You'll need to define your own product, e.g. msi_wind, which would probably > live under vendor/msi/wind/. You can use the eeepc target as an example of > how to do this. You'll need to copy the kernel you built, as well as the > drivers into that directory from your kernel build dir. You'll then need to > make the appropriate changes to the init.msiwind.rc/inti.msiwind.sh (or > whatever) to make sure it loads your drivers. > > --Dima > > On Tue, Jan 6, 2009 at 12:23 PM, Martin <[email protected]> wrote: > > > Hello all, I have followed the instructions on howto compile android > > for eeepc and loaded up on my msi wind but obviously it compiles with > > eeepc specific hardware support, could someone direct me on howto > > change this for hardware support for the wind. > > > I downloaded the android source code from the git repo, I menuconfig'd > > under the kernel directory and saved it as a .config file, when > > compiling android would it take that into consideration? > > > Thanks in advance, Martin. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
