It turns out my issue was the battery driver hanging, thus causing the
whole /dev enumeratino process to freeze.
--
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
---
You received this message because you are subscribed to the
Le jeudi 18 juillet 2013 à 00:30 +0200, Paul Kocialkowski a écrit :
> 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.
After read
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 ro
