| |||||||||||||
MeeGo to return next month with Jolla phone launch (The H)MeeGo to return next month with Jolla phone launch (The H)Posted Oct 10, 2012 20:27 UTC (Wed) by dlang (✭ supporter ✭, #313)In reply to: MeeGo to return next month with Jolla phone launch (The H) by Cyberax Parent article: MeeGo to return next month with Jolla phone launch (The H)
> Again, what's wrong with the drivers?
The fact that so many manufacturers have closed source drivers that are specific to their particular android release.
This makes it very difficult to compile a replacement kernel (let alone an upgraded kernel) to run on that hardware. This prevents compiling a new kernel that enables something that wasn't enabled on the 'stock' kernel, as well as being a large blocker to running anything other than the vendor provided image (including running newer versions of android).
Putting some of the drivers in userspace, but with a kernel interface that breaks from release to release, is just adding insult to injury.
(Log in to post comments)
MeeGo to return next month with Jolla phone launch (The H) Posted Oct 10, 2012 21:24 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link]
> The fact that so many manufacturers have closed source drivers that are specific to their particular android release.
These drivers are mostly for two things: video and wifi. Both are well problems in DESKTOP Linux. Most of other drivers are open source.
Besides, I dare say, the closed source drivers in Android are easy to work around. CyanogenMod has no problem building custom kernels, I also did this myself for my Samsung Galaxy S.
MeeGo to return next month with Jolla phone launch (The H) Posted Oct 10, 2012 21:37 UTC (Wed) by dlang (✭ supporter ✭, #313) [Link]
As someone who owns one of the less popular devices, I can say that the closed drivers are not easy to work around.
CyanogenMod picks what devices they support in part based on how hard it is to deal with the drivers (with the bigger part being how popular the device is)
|
|||||||||||||