> grep "open_binder", "/dev/ashmem" in the android source code . This will > provide you clue on how android utilizes the drivers.
While binder is a kernel driver, it's used primarily for communication between userspace components, not between the userspace components and functionality in the kernel. But most functionality in the kernel that is android specific rather than generic *nix (and even some that is standard but semi privileged) likely uses binder to connect the application to an android service in userspace, which in turn uses one of a variety of interface into the kernel. -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
