I am currently experimenting with the android-3.4 branch from the AOSP common kernel tree. I've setup minimal support for my device so that the whole things boots.
The kernel starts, loads Android initramfs and starts init, which creates /dev (among other directories). I figured it is ueventd's role to populate /dev when receiving ADD uevents. However in my case, /dev remains desperately empty. Thus, init can't mount the Android partitions (since the dev nodes don't show up) and the whole thing hangs. I added some debug prints on ueventd and it seems that very few events are actually caught: [ 4.525970] init: GOT DEVICE EVENT FROM SUB [event_source] [ 4.532470] init: GOT DEVICE EVENT FROM SUB [iio] [ 4.537841] init: GOT DEVICE EVENT FROM SUB [w1] [ 4.543304] init: GOT DEVICE EVENT FROM SUB [w1] [ 4.548675] init: GOT DEVICE EVENT FROM SUB [platform] I suspect ueventd is just too late to catch the ADD events for most devices and thus can't create the dev nodes. On another kernel where everything works fine, these uevents are all received when ueventd starts. I guess my issue is in kernel-space. Any lead on how I could solve this? A general explanation of how ueventd is supposed to catch ADD events that were sent before it started running (which seems to happen on kernels where it works) would be welcome as well! -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel --- You received this message because you are subscribed to the Google Groups "Android Linux Kernel Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
