The differences change from version to version (both of Linux and of Android), and the exact kernel is different for each device. A kernel for Android is a mainstream Linux kernel, with additional drivers for the specific device, and other additional functionality, such as enhanced power management or faster graphics support.
Many features in the Android kernel are later added to upstream Linux after the open-source community has accepted (and perhaps modified) them, but others are never upstreamed, either because they're not acceptable to the Linux kernel developers, or because they're only applicable to Android or to specific hardware.
Most drivers for android specific hardware was accepted into mainline kernel; but some features, such as the wake lock which caused a huge controversy some time ago, remains problematic because mainline and android kernel developer disagree whether it's a good idea. –
Lie RyanJun 21 '13 at 0:57
Beside the device specific differences and wake lock that Dan Hulme and Lie Ryan mentions, Android removed System V IPC features (message queues, shared memory segments, semaphores) that could lead to resource leaks (http://www.kandroid.org/ndk/docs/system/libc/SYSV-IPC.html). This probably is just a matter of configuring the kernel build. Also the Android IPC of choice, called Binder, has some support in the kernel that to my knowledge is not included in standard Linux kernels.
The differences change from version to version (both of Linux and of Android), and the exact kernel is different for each device. A kernel for Android is a mainstream Linux kernel, with additional drivers for the specific device, and other additional functionality, such as enhanced power management or faster graphics support.
Many features in the Android kernel are later added to upstream Linux after the open-source community has accepted (and perhaps modified) them, but others are never upstreamed, either because they're not acceptable to the Linux kernel developers, or because they're only applicable to Android or to specific hardware.
Most drivers for android specific hardware was accepted into mainline kernel; but some features, such as the wake lock which caused a huge controversy some time ago, remains problematic because mainline and android kernel developer disagree whether it's a good idea. –
Lie RyanJun 21 '13 at 0:57
Beside the device specific differences and wake lock that Dan Hulme and Lie Ryan mentions, Android removed System V IPC features (message queues, shared memory segments, semaphores) that could lead to resource leaks (http://www.kandroid.org/ndk/docs/system/libc/SYSV-IPC.html). This probably is just a matter of configuring the kernel build. Also the Android IPC of choice, called Binder, has some support in the kernel that to my knowledge is not included in standard Linux kernels.
扫一扫
到【灌水乐园】发言
