I think my anger for the week is squarely directed at fglrx.ko, though that's more because it's more fresh than what I hold for nvidia.ko (which is easier on the kernel, but has other problems).
fglrx.ko has some annoying kernel requirements.
fglrx is not compatible with CONFIG_PREEMPT_RCU.
fglrx requires CONFIG_UNUSED_SYMBOLS.
fglrx requires CONFIG_PCI_LEGACY (c'mon, guys, pci_find_slot() was deprecated two years ago at this point...).
fglrx is not compatible with CONFIG_PARAVIRT.
And then, even after I got it installed, I was getting "BUG: using smp_processor_id() in preemptible [00000000] code: X/26646" in my dmesg and the system would restart. It would be nice if we could get a performant driver that isn't in danger of being deprecated into inoperability.
With an FX5200, nvidia.ko was giving me strange green corruptions and would cause a crash in the app or an oops if I was unlucky. Highly uncool. Before that, with the 8800 I was borrowing, it was very bad at doing multiple monitors: Twinview is an ugly, ugly hack and nVidia should be ashamed of themselves.
radeon.ko on my r300 chipsets has performed swimmingly. Suspend on my laptop is faster and more reliable, now.
If I can offer any real complaint, it's that the documentation for the whole open stack could really use some amount of cleanup, pruning, updating, etc.
For example...well, I guess the X.org wiki is the "official" documentation for radeon and radeonhd. Is it? I would never be able to tell from the main page. Were it not for Google, I don't know that I would ever have made it to the radeonhd page. And were it not for radeonhd, I'd never be able to find the radeon page for the place. Ahh. this gem caught my eye, too:
"I have an ATI graphics card, which driver should I use ?
The GATOS project..."
Yes, the same GATOS that hasn't seen a commit in four years or so. This is straight from the VideoDriverFAQ at the X.org wiki. If you don't just stop reading after three words, it also states that r300 and up is still highly experimental and doesn't even mention radeonhd.
So I think something definitely needs to be done about documentation management for the open drivers and acceleration: clearly leaving it under the banner of X.org is not working out so well and I feel it ends up being misleading to the end user.
fglrx.ko has some annoying kernel requirements.
fglrx is not compatible with CONFIG_PREEMPT_RCU.
fglrx requires CONFIG_UNUSED_SYMBOLS.
fglrx requires CONFIG_PCI_LEGACY (c'mon, guys, pci_find_slot() was deprecated two years ago at this point...).
fglrx is not compatible with CONFIG_PARAVIRT.
And then, even after I got it installed, I was getting "BUG: using smp_processor_id() in preemptible [00000000] code: X/26646" in my dmesg and the system would restart. It would be nice if we could get a performant driver that isn't in danger of being deprecated into inoperability.
With an FX5200, nvidia.ko was giving me strange green corruptions and would cause a crash in the app or an oops if I was unlucky. Highly uncool. Before that, with the 8800 I was borrowing, it was very bad at doing multiple monitors: Twinview is an ugly, ugly hack and nVidia should be ashamed of themselves.
radeon.ko on my r300 chipsets has performed swimmingly. Suspend on my laptop is faster and more reliable, now.
If I can offer any real complaint, it's that the documentation for the whole open stack could really use some amount of cleanup, pruning, updating, etc.
For example...well, I guess the X.org wiki is the "official" documentation for radeon and radeonhd. Is it? I would never be able to tell from the main page. Were it not for Google, I don't know that I would ever have made it to the radeonhd page. And were it not for radeonhd, I'd never be able to find the radeon page for the place. Ahh. this gem caught my eye, too:
"I have an ATI graphics card, which driver should I use ?
The GATOS project..."
Yes, the same GATOS that hasn't seen a commit in four years or so. This is straight from the VideoDriverFAQ at the X.org wiki. If you don't just stop reading after three words, it also states that r300 and up is still highly experimental and doesn't even mention radeonhd.
So I think something definitely needs to be done about documentation management for the open drivers and acceleration: clearly leaving it under the banner of X.org is not working out so well and I feel it ends up being misleading to the end user.
Comment