Future
Uh, that is really a bit hard to digest. The way you're explaining it: you are a programmer and non-native English speaker.
A BIG THANK YOU for your explanation, I am sure, it will help me along the way.
In case the illustration http://en.wikipedia.org/wiki/File:Th...and_glamor.svg is correct, and also, in case AMD is going to switch from their own in-kernel blob to the DRM/TTM combo of the FOSS driver, then, the illustrated stack is the one to put your money on:
Originally posted by jrch2k8
View Post
A BIG THANK YOU for your explanation, I am sure, it will help me along the way.
In case the illustration http://en.wikipedia.org/wiki/File:Th...and_glamor.svg is correct, and also, in case AMD is going to switch from their own in-kernel blob to the DRM/TTM combo of the FOSS driver, then, the illustrated stack is the one to put your money on:
- kernel-space:
- we can expect the DRM/TTM in-kernel solution to support the conversion of CPU/GPU in a performant way, I mean the HSA hardware implementations (e.g. http://en.wikipedia.org/wiki/AMD_Acc...Implementation)
- user-space:
- the Wayland-based user-land is a "fat"-free start engineered for the future
- that thanks to XWayland continues to support software that relies on libX/libXCB instead of using libwayland-client
- thanks to GLAMOR, the fuss with the additional graphics driver for the xserver will go away (finally)
Comment