thanks for the info i think that solves my doubts...let me try and get back to u bye shivap
On Dec 19, 8:17 pm, Anil Sasidharan <[email protected]> wrote: > Hi, > > The UDEV event handling logic is embedded in devices.c. Based on > the UDEV events, the appropriate device nodes get created by the "init" > process during Android boot-up. > > Warm Regards, > Anil > > On Fri, Dec 18, 2009 at 11:34 PM, shivap <[email protected]> wrote: > > Michael > > > what should i do in these files (system/core/init/devices.c and system/ > > core/init/init.c) which will help me create proper device nodes? i > > know its a dumb question but > > i am fairly new to all this. > > > bye > > shivap > > > On Dec 18, 4:00 pm, Michael Trimarchi <[email protected]> > > wrote: > > > shivap wrote: > > > > hello all > > > > i got android kernel 2.6.27 (downloaded from android git) running on > > > > my mainstone II dev.board. now i want to add android over this. when i > > > > build android source code i get three images system.img , userdata.img > > > > and ramdisk.img. i unpacked system and userdata images using unyaff > > > > tool and ramdisk with gzip/cpio tool. i get dev directory which is > > > > empty. so how to create my device nodes? should i just copy device > > > > nodes from my working linux rootfs? while building android kernel i > > > > have enabled binder and ashmem. i see that these two will be added to / > > > > dev directory. but the dev directory i hav is empty? how to link > > > > android kernel with android source code? what is the right way of > > > > building android? please help me. i am under lot of confusion. > > > > thanks in advance > > > > system/core/init/devices.c and system/core/init/init.c > > > > Michael > > > > > bye > > > > shivap- Hide quoted text - > > > > - Show quoted text - > > > -- > > unsubscribe: > > [email protected]<android-porting%[email protected]> > > website:http://groups.google.com/group/android-porting -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
