Originally posted by pal666
View Post
Announcement
Collapse
No announcement yet.
drm_hwcomposer: Allowing Mainline Linux Graphics Drivers To Work On Android
Collapse
X
-
-
Originally posted by Zan Lynx View Postglibc is just not a good libc for embedded and smaller systems. You can tell by how nobody is using it there.
You could run the entirety of the GNU userland on maemo 5 if you so chose.
Samsung's Tizen also runs Wayland, GNU, the enlightenment libraries.
Android does not use the typical UNIX usage model, and opts for per-app permissions which suit mobile far better, as phones generally have one users, and many apps from often untrusted, or semi-trusted sources. Very much a seperate use case. The state of Linux graphics when android started was also somewhat poor.
- Likes 1
Comment
-
Originally posted by pal666 View PostHackfest 2014: Theo de Raadt presented "arc4random" Slides: http://www.openbsd.org/papers/hackfest2014-arc4random/index.html Talk description: http://www.hac...Last edited by microcode; 29 March 2017, 04:25 PM.
Comment
-
Originally posted by artyom.h31 View Post
If so, why Linux desktop developers haven't just borrowed Android technologies?
Comment
-
Originally posted by artyom.h31 View Post
If so, why Linux desktop developers haven't just borrowed Android technologies?
Because they have?
https://en.wikipedia.org/wiki/Hybris_(software)
- Likes 2
Comment
-
Originally posted by artyom.h31 View Post
If so, why Linux desktop developers haven't just borrowed Android technologies?
You have to remember most desktop applications are designed around the idea of having Opengl full not the Opengl ES cut down versions that android ships with. This is just the start of many differences.
The only option has been to look at what android has done and integrate the best features back into the DRI/DRM stack.
Comment
-
Originally posted by artyom.h31 View Post
If so, why Linux desktop developers haven't just borrowed Android technologies?
So the only correct way forwards was integrate the features from Android into the DRM/DRI stack. The most feature containing graphics stack is the graphics stack the Linux Desktop uses not the Android one. The Android graphic stack has contained a few features the Linux has lacked.
So Libhybris/hybris is a very limited work around.
Comment
-
Originally posted by pal666 View Postandroid does not run on smaller systems
ARMv6 single core 528 MHz CPU downclocked to 384 MHz.
192 MB RAM, of which only 96 MB was addressable by Linux, the rest was allocated to the RIL and GPU.
256 MB flash storage, which was for both the RO system, **AND** RW userdata.
Now then the question may be why they haven't switched over to glibc since then, and there are a number of answers to that;
1) Its lots of work with little reward.
2) Some have mentioned security considerations.
3) The license on glibc is LGPL, which is scary for some vendors.
Comment
Comment