Ok I found that mdev -s is called in startup rcS script and it populates /dev nodes. But it doesn't create alarm node. I see log from driver functions module_init and late_init, they work fine. in /sys/bus/platform/driver/alarm there is uevent which doesn't give me major and minor numbers. rtc_alarm_add_device function is never called. This looks suspicious, but I don't know when and who should call it.
Any help appreciated... Petar On Sep 2, 12:59 pm, petar bajic <extra.pedestr...@gmail.com> wrote: > Hi, > > I added alarm.c and it builds fine, but when I deploy kernel to the > board device node is not created in /dev/alarm > I have /dev/binder and /dev/ashmem, and I can't figure out where are > these created. > > best regards, > Petar Bajic -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
