In fact, the process is not pushing, it is pulling. The time now is Linus and the kernel contributors together own the copyrights on the kernel. Please let us know your results. The problem is that if you merge a Windows driver into the Linux kernel, the Linux hackers won’t be able to make effective and safe changes to it as the rest of the kernel evolves, because it’s nearly unreadable to them. Grub is ugly anyway unless you know how to theme it.

Uploader: Shaktibei
Date Added: 14 March 2013
File Size: 43.8 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 34052
Price: Free* [*Free Regsitration Required]

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

Would you really merge a bunch of huge cleanups that would potentially break tons of stuff in subtle ways because coding style is that important? Revolution energy saving design. It seems to me that they made no threat. I had a GPU that worked wellfor my purposes, even ran games well enough for me, but you dropped driver support for it, so I was left with no option but to buy another card Because obviously they’ll just move away from Linux or whatever if you’re a dick to them except in the case where Linux effectively subsidizes their existence, making their product even possible.

Hell, even Rockchip, Allwinner and Sony can do it, Qualcomm, Mediatek, Google and Samsung are just not doing it because they are able to skate by without doing it.


Then all the Linux fans that complained to AMD that they don’t deliver open source drivers should from now on better shitstorm the kernel maintainers, since AMD delivered. At some point people what support for the hw they have and they want it to work. Did I miss the mud-slinging and corporate culture bashing from the original rejection? No, it works very well for nVidia.

They’ve had to go to pretty extreme lengths not to go under already eg, selling off their headquarters building, then leasing it back, just to scrape together some quick cash. I sb170 like we constantly refactor the core to deal with that or that quirk or requirement of someone’s hardware and then deal with tons of fallout.


It may be possible in Grub2 to save the functioning TrueCrypt loader to a. You don’t need to operate at a net profit in order to sn710 able to devote resources to a strategy that you value as a company, but you do need cash flow. 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: In a bit of code that rung alarm bells.

However, I don’t think that AMD did things this way just because of short-sighted management. I completely skipped over those portions But then why bother? The south bridge connects.

Datasheets – coreboot

XorNot on Dec 10, Fear of missing out on market segment, as well as support for super-computer configurations. Unlock hidden CPU core and potential.


This is nonsense, a NACK is ,inux near the table-flip you’re portraying here. And I fully kwrnel the Linux kernel maintainers for this. Also, usually the maintainers have far superior technical knowledge of their areas to Linus. Well, as far as I understood, that’s exactly what the entire discussion is about: And this is the thread that bridgman points to: We’re talking about having a constant up-to-date driver on par with Windows for a major GPU card manufacturer.

You can argue whether I should have talked about their net losses, but you can’t claim I’ve confused anything. I agree that there is room for disagreement between the two approaches. How does one discover if AMD X chipset support is in a given kernel?

They made over a billion dollars in alone, and they’ve been knocking around since Email me about changes to this bug report. An unmaintainable mess with lots of users is not a victory linu users are paying you for shitty work. BB code is On. I could make a really cool photo album by taking snapshots of developers and managers who are only familiar with Windows and hear about the challenges involved in writing and upstreaming a non-trivial Linux driver.