Hi again, I assume you are building a kernel that has a new char device "driver" with a specific device major/minor number associated with it. However, you will require a char device "file" in /dev for a process to control the device driver. That requires you to write a udev descriptor or static dev file using mknod with major/minor number to mapping your char device driver.
Hope that helps. kmatzen wrote: > You can build it the same way as any Linux kernel. If building for > the dev 1 then get the .config from the phone itself. If building for > the emulator, switch to the kernel-goldfish-2.6.27 branch and run > 'make goldfish_defconfig' to get the correct .config. Finally, run > 'make'. > > The question I have is, where do you place the zImage and vmlinux when > building the Android software stack? Right now I'm overwriting kernel- > qemu and vmlinux-qemu in the prebuilt directory. The modification > that I made to the kernel was adding a character device. However, > this charact er device does not appear in /dev. Any ideas? > > On Feb 15, 11:57 pm, "chin...@tw-roc" <[email protected]> wrote: > > Hello > > > > There is no android.mk in kernel folder of andoid platform source > > codes, so I could not use "mm" to build the whole folder. I am > > wondering if any script for android build system to build Android's > > linux kernel? > > > > Thanks > > > > Chinlin --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
