Originally posted by birdie
View Post
Announcement
Collapse
No announcement yet.
AMD Releases New "AMDGPU" Linux Kernel Driver & Mesa Support
Collapse
X
-
Originally posted by RussianNeuroMancer View PostSame question here. It would be nice if someone from devteam comment on that
Well there is XDC video, that should answer some questions
Last edited by dungeon; 21 April 2015, 01:08 PM.
Comment
-
Originally posted by birdie View PostI'd love NVIDIA to do something similar.
I.e. break their driver into two parts: a kernel driver which is 100% open source and provides a set of APIs to access the hardware and a userspace blob to talk to the driver/hardware beneath it.
This way the kernel driver might be included in the Linux kernel and we could safely update kernels as often as we want to without having to recompile anything else.
I'm a dreamer, ain't I?
It has already been discussed in the past, and the kernel guys will not add a kernel driver with the sole purpose of exposing an ABI only to support a proprietary blob - which actually makes sense, if you investigate the reasoning behind.
AMD however can pull of this trick exactly because they also make a fully functional Open Source user space layer (in good faith!) such that the kernel driver has an ABI that can be used by both drivers. In principle AMD could also make Catalyst working upon the current Radeon/RadeonSI kernel DRM drivers, but the current kernel ABI is probably not a good fit for the Catalyst driver. (Can somebody elaborate?)
Until Nvidia changes their minds, you will have to live in pain (or buy AMD)...
Comment
-
Originally posted by 89c51 View PostI don't see a reason to buy nvidia if you want FOSS drivers. Nouveau is AFAIK in a worst state than Radeon. If AMD fixes a few glitches here and there it will be perfect.
Comment
-
Originally posted by Veto View PostYes, you are
It has already been discussed in the past, and the kernel guys will not add a kernel driver with the sole purpose of exposing an ABI only to support a proprietary blob - which actually makes sense, if you investigate the reasoning behind.
AMD however can pull of this trick exactly because they also make a fully functional Open Source user space layer (in good faith!) such that the kernel driver has an ABI that can be used by both drivers. In principle AMD could also make Catalyst working upon the current Radeon/RadeonSI kernel DRM drivers, but the current kernel ABI is probably not a good fit for the Catalyst driver. (Can somebody elaborate?)
Until Nvidia changes their minds, you will have to live in pain (or buy AMD)...
Comment
-
Originally posted by RussianNeuroMancer View PostSame question here. It would be nice if someone from devteam comment on that
Comment
-
Originally posted by nanonyme View PostMaybe Windows would suit your mood better?
I pledge no allegiance to any OS. And the least thing I care about is "openness" because this word doesn't guarantee anything at all except it's useful for the preservation of our digital history but even that isn't that important since we can run most ancient software in virtual machines.
Comment
-
Originally posted by nanonyme View PostMaybe Windows would suit your mood better?
Comment
-
Originally posted by agd5f View PostMainly to support enterprise Linux distros. Most of them do not ship the latest xserver with built in glamor and modesetting. It also enables us to implement device specific options, if necessary, for certain workstation features, etc.
Comment
Comment