This feud really needs to be resolved...
|
| Author | Content |
|---|---|
| JaseP Aug 12, 2010 9:43 AM EDT |
This feud really needs to be resolved... Keeping Google's code contributions at arm's length is going to get difficult for hardware vendors to support Linux, and give creedence to the competitive claims that Linux is too fragmented... It's simple, really... Google's code contributions can be set up in the kernel configs in most mainstream kernels to be turned off, rather than turned on... It happens all the time in terms of hardware support for various devices that conflict with one another. For me, the bigger problem with Android is the frame-buffer graphics and their "incompatibility" (if that's the right way to describe it) with the current set of Xorg drivers. On one hand, it allows for video chipset hardware manufactueres to support Android and keep their little binary snippets proprietary and APIs not disclosed. On the other hand, it limits what chipsets that will be supported under mainstream Linux. On top of the frame-buffer graphics, it's the whole Java machine thing... To me, Meego will be a better solution. With Maemo it will be easier to port existing Linux apps to mobile. But, the more, the merrier. The more mobile distros, the more innovation we will see. |
| djohnston Aug 12, 2010 4:13 PM EDT |
Quoting:Keeping Google's code contributions at arm's length is going to get difficult for hardware vendors to support Linux, and give creedence to the competitive claims that Linux is too fragmented... It's beginning to happen, bit by bit. http://www.theregister.co.uk/2010/08/10/android_kernel_readm... |
| herzeleid Aug 12, 2010 5:57 PM EDT |
Much ado about nothing. Things are getting resolved - noisily and messily, but moving towards convergence. |
Posting in this forum is limited to members of the group: [ForumMods, SITEADMINS, MEMBERS.]
Becoming a member of LXer is easy and free. Join Us!