May 17, 2019 posted by

Not too mention oddities and artifacts, I get from time to time. If there’s an exploit in the kernel or xorg, tough. The FD issue is resolved. I checked my motherboard’s website and there are no linux drivers for For example, I have an AMD rig with SB and the kernel modules for. Much more constructive interactions, I think. Do the kernel devs feel a pressure for the kernel to stay relevant in the Android world? TD-Linux on Dec 10,

Uploader: Yozshugrel
Date Added: 5 August 2008
File Size: 49.83 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 92900
Price: Free* [*Free Regsitration Required]

That may have been true of their driver quality in the past, but it’s really not so true now.

The kernel demanded they drop the idea of a cross-platform driver to get merged into the kernel. Well, whatever Intel has been doing, they’re just successful as merging their codebase.

You can go look at the code right now, ‘git pull’ it and install it on your machine. Comment on this change optional. If the kernel developers just don’t give a shit about proprietary vendor kernel forks I really, really don’t think they really do, at least nobody with actual meaningful, large scale influence cares at alland want to force involvement by “getting them in the cycle” and being buddy-buddy and just not-giving-a-fuck about people outside the source tree, making sure constant churn is how people ajd to keep up — they should just use the BSD license.

His arguments seem really weak.


The way AMD have done things is ksrnel enough to confuse the core maintainer, and he has reasonably said that he doesn’t want to accept a commit like this. And now nVidias approach has been completely vindicated. The end result of the thread is that they’re going to split thislines of hardware abstraction into much smaller chunks and merge it piece by piece. Please let us know your results.


They too may go the closed source, taped together with a HAL way and that’s not good for the long run. Try reading the article and doing some digging through this thread to understand the context. The use of gross profit here is severely misleading. Share your knowledge at the LQ Wiki.

Also, they seem quite willing to maintain it. There were certainly implications that the AMD coders were making technically compromised decisions: For instance, there apparently are some standard idioms that have emerged from within the atomic code. I am not familiar at all with this stuff but honestly people should be working on a way to isolate external code in the kernel at runtime somehow.

Linux Is A Huge Update For Both AMD CPU & Radeon GPU Owners – Phoronix

I’m personally very happy to see the gpu subsystem maintainers paying attention and having the maturity to know a fool’s errand when they ljnux it. Honestly I hear this quite often from big companies and it always is the biggest load of BS ever.

eb710 Instead, they wrote to the linux kpi. The SoC-specific drivers can be written and updated separately just like apps. Stuff like depreciation though less of an issue now without the fabs and writing off “goodwill” from e. If it weren’t for those kernel devs, good luck getting a Linux system to “boot and function as a normal user’s desktop” because of all the crap that would be in there.


If the hygiene isn’t there, maybe the quality kernnel either. The kernel maintainers don’t necessarily want your code. He even acknowledged the political situation but it wasnt even his job to care about that. The reasoning is that this system results in a more accurate picture of a company’s finances. An email from one of the Intel devs clarified that the validation was actually happening in the correct place, it just was hard to see that on first reading because the code was too foreign: Waterluvian on Dec 10, You may be right but do you have any evidence?

Do the kernel devs feel a pressure for the kernel to stay relevant in the Android world? It will allow additional upstream developers to examine the issue.

No, it works very well for nVidia. This wasn’t an open source driver, this was a hardware abstraction layer that they wanted in the kernel so xmd Windows driver could be distributed under a proprietary license and used without a kernel recompile.