The Letter That Started AMD's Open-Source Strategy
An anonymous reader writes "In marking the fourth anniversary of AMD's open-source strategy for their Radeon graphics, Phoronix has published the letter that launched this open-source effort. It was a letter written by Novell SUSE X engineers and submitted to AMD management with their open-source proposal."
Even their closed-source driver sucks, it's not just the open source one.
The OSS driver works pretty good for antique hardware. Unfortunately, it doesn't work very well for anything vaguely modern, while fglrx pretty much doesn't support anything more than a few years old (and it does more or less suck.) Consequently, if you have anything but the fanciest (unless it's very very new) or shabbiest ATI card, you can expect it to suck rocks through straws on Linux. nVidia is better but shares many of the same flaws. However, middle-aged hardware is well-supported by the official driver, and amazingly old hardware is supported as well. That makes support much easier, and while shopping for older computers with Linux compatibility in mind, it makes avoiding ATI a no-brainer as well. This reduction in resale value causes me to value ATI less up front... But to the masses who will never run Linux on a desktop, it's fairly irrelevant. Most people don't buy used hardware.
Anyone want to buy a P4 desktop with an ATI Rage Pro in it? It runs Ubuntu just fine :)
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
And a non-free firmware blob is required to operate the motherboard, nic, wireless card, etc on a linux install. Can we really call linux free, then?
All I see is an article talking about the letter, where's the actual letter?
--
Stay tuned for some shock and awe coming right up after this messages!
The difference there is that Intel doesn't have any IP in this area worth protecting.
Also, what you're conveniently ignoring is that most of the source that AMD has came from ATI and was prior to the change in strategy. It's not easy to go back and retroactively open source things for which you may or may not already have the rights. I'm guessing that there's probably a fair amount of other people's IP involved. And even if there isn't, the legal team does still need to go through and make sure that they aren't going to be sued for releaseing something they shouldn't.
To ensure an open development process NOVELL would require that it will not make use of any specifications or programming documentation that can not be made available to other developers from the open source community also under a suitable documentation publication program which will permit the release of source code under an open source license.
This step will help to ensure continued maintenance for hardware components beyond the maintenance cycle of the manufacturer and will help customer to secure their investment. Furthermore it will demonstrate and underline AMD's full commitment to the open source development model and send a positive signal to the open source community which this has been waiting for for a long time.
NOVELL will ensure that a driver with at least base functionalities is available for earlier releases of the X Window System at least back to X11 R6.9 to be integrated in existing enterprise products by their respective vendors.
Consider that the "binary blob" in most drivers is in reality the firmware for the card, without which it's a fairly dull FPGA with maybe some spiffy maths goodness tacked on.
Now, how exactly does that differ from the closed binary firmware in your hard disk, or keyboard, or mouse?
Well it works fine as a marketing lie apparently. I recently had the joy of upgrading my home PC, and there was hundreds of mid-range graphfcs cards to choose from. I got the AMD mainly because they support open source (or so I thought), and I may want to switch to Linux some time in the future if they can finally get the video rendering up to the same level as Windows.. (I have used laptops with AMD and NVidia graphics card on Linux and I haven't noticed much difference actually. The most recent one was an NVidia card, and I could never get rid of the tearing artifacts on the secondary display)
lspci | grep -i radeon && exit 1
done.
Exactly
Stallmantitis is ridiculous.
YOUR COMPUTER requires a non-trivial amount of closed-source information. It doesn't matter if it's in hardware or software.
And of course the 1st post is a troll, it's anonymous.
how long until
I beg to differ: I've run R600 and R700 (read: 3000 and 4000 series) cards with the FOSS driver and I find it miles better than fglrx: at least it does play nicely with all other components in the system.
A CC-licensed illustrated horror novel
I sure wish my X1250 hardware would work. I have a subnotebook on which I can only run Vista because of drivers. It has R690M chipset and L110 CPU and it's generally poorly supported under linux, the power scaling stuff doesn't work right either.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Well now it doesn't _require_ firmware to be closed-source. And my understanding was that typically, devices that absolutely require firmware to even work at all, well those would be the cheap corner-cutters a-la WinModem - an unfortunate plague in the hardware industry. Really, if that's where we are, then motherboards might as well just give us a thousand socketed general-purpose output pins, and we'll push on whatever connectors we want and turn the whole thing into a glorified FPGA emulator.
There's always this pendulum swing - shitty mfgs push more functionality into SW/FW, things get too slow, so along comes a bright-eyed new guy with real hardware again, that runs nice and fast. Then the new guy falls in love with money, starts peddling garbage again, and the cycle repeats.
-Billco, Fnarg.com
The "what have you done for me lately" crowd has an interesting way with words that never fails to amuse me.
Everyone else? There are three horses in this race, and a few ticks hitched to the feathers surrounding the coffin bone. 90% of the cells in the human body are bacterial. Sometimes you have to integrate over quorum.
Intel isn't especially huffed about offloading high-demand computing to a GPU chip manufactured by somebody else. Without somebody else poised to siphon an artery, Intel would do everything in their power to level the field. We would have one coefficient of Moore's law governing performance, rather than two. Generally when you lash two horses together, the slower horse governs the pace.
Fortunately, the GPU swallowed the blue pill before Intel could do much about it. On the side of the fence with the big Cheshire grin, we have precisely two spectral lines of any significance: red and green. But you have to remember that both of these companies exist in an ecosystem where the bully in the china shop hoovers up the vast majority of the resources like the human race arrived on a shiny new continent.
It ain't easy feeding the sourdough culture known as Fab. It's the pudding mix in Sleeper, the plant in Little Shop of Horrors.
If your Fab blows a bubble, you're in a world of hurt. Around this nightmare, you have to knock off some of the most technically demanding design projects known to man, year in and year out. After you build a Saturn V, everyone wants a Saturn VI. The Saturn VI blows everyone away--for a year or two--then everyone starts to itch and scratch for a Saturn VII.
Back when the original Saturn V was crawling toward heaven at a top speed of 1mph, who exactly was "everyone else"? But let's not give the Americans any credit for trumping anyone else.
The painful truth here is that if you love open source, sometimes you have to settle for second best. AMD is slowly making good on the promise of taking this track, although it's truly frightened to think of how much oxygen has boiled off in their seemingly perpetual state of launch readiness. It ain't called Fusion for nothing.
At the bottom of the process this is an IP issue. Some people seem to think that open source happens in Wikileak time frames. It could work that way, but billion transistor designs would really stress out your onion router, and customs might seize your next mask set.
I played a chess game not long ago where I settled into the Siberian Winter defense. In other words, my opponent was better than me, but he fired his powder a moment too soon.
I was boxed in by the mate threat, and his mate threat was boxed in by my passed wing pawn on the other side of the board. If his quill armada didn't crush me first, my winter pawn would crush him later.
If you're asking "what has AMD's wing pawn done for you lately" I suppose the answer is that it sits there doing not very much.
In my case, not very much won me the game after 10 rounds of desperately accurate counter-parries.
Three cheers for the winter pawn.
Yes. Firmware is just an enabler that lets your hardware expose the features you read on the hardware's box before buying it. It's not related to the specific uses you want to make of your hardware, it's software-independent, so you as an end user have no interest in tinkering with firmware (although being able to do so can be an extra bonus, in some specific scenarios).
Drivers, on the other hand, bind your hardware to a specific operational environment, and limit your freedom to use the hardware in any way you want. They limit the CPU architectures you can run your hardware on. They limit the choice of operating systems you can run your hardware with. They limit the adaptability of your hardware to new operating system releases. An open source driver that, even by interfacing to closed-source firmware, sets me free from all of these limits, is perfectly free to me.
There are some hardware solutions that suck so bad you wouldn't want Linux on their anyways.
- Dan.
~ People that think they are better than anyone else for any reason are the cause of all the strife in the world.
DON'T BUY FROM ATI enemy of your freedom
That picture is looking sillier and sillier as time goes on.
Funny you mention WinModems. They are so simple the exactly opposite is true. They usually don't require a firmware (since it's the tiniest amount of hw to plug your computer to a phone line). On the other hand, a 'upload when using' fw for a 'Hard modem' would make lots of sense (this is used on some DSL USB Modems)
But yeah, it doesn't have to be closed source, still, I'm doubting Intel is releasing their processor's VHDL/Verilog files any time soon...
There's always this pendulum swing - shitty mfgs push more functionality into SW/FW, things get too slow, so along comes a bright-eyed new guy with real hardware again, that runs nice and fast. Then the new guy falls in love with money, starts peddling garbage again, and the cycle repeats.
Correct, but Moore's law is very helpful for money lovers. I'm sure something like desktop effects waste more CPU than a Winmodem today.
how long until
my amd fusion e-350 begs to differ on that. it works very well on the foss drivers.
A winmodem is basically a sound card with an analog telephone line interface. This means all the modulation and channel coding that needs to be done to send/receive data is done in software. Real modems use a DSP to implement the modulation, and have the firmware for the DSP in a Flash chip. The only cost-cutting involved would be to do away with the Flash chip and have the device driver download the firmware each time the modem is power-cycled. Nobody did this with any modems I'm aware of, partly because being external from the PC case, it's hard to say if the modem DSP has already booted and is running firmware or not. With an expansion card, this is not an issue. Back in '98, I was able to update the firmware on a Zyxel 28.8k modem and have it support 56k, since it used a programmable DSP and allowed Flash reprogramming. Greedy marketers would usually prevent this from happening so I'd spend more $$$ to buy the 56k modem - somehow Zyxel were different at the time.
It depends on what you mean by "blob". Does an average motherboard use a BIOS? Yes. Does the Linus kernel contains blobs for the average motherboard? No. Likewise NICs. Wifi cards, yes, sometimes the driver contains a blob, but many common cards don't (e.g. Madwifi dropped the HAL blob in 2007). If you are going to argue that being able to drive a device that has onboard firmware makes the Linux kernel non-free, even when that firmware is not distributed as part of the Linux kernel, then I would argue that you are using an extreme definition for the sake of making a point ("omg your Linux isn't be free because your Intel CPU isn't free!") It is perfectly possible, and in fact quite common, to have a working Linux system that uses no closed driver blobs.
obvious troll is obvious.
YOUR COMPUTER requires a non-trivial amount of closed-source information. It doesn't matter if it's in hardware or software.
It matters from a practical perspective. If there is a bug in open software, then you can fix it. If some driver threatens the stability of your system, then you can do something about it. You can't really do that if you find a hardware bug, though you might be able to work around it in software. If the open software suffers bitrot then you can update it to the latest APIs. You can't really do that with closed software. Open source software gives a skilled programmer the ability to fix pretty much any problem on their system in a way that just isn't possible with closed source.
Most do, but a few run Coreboot.
In capabilities the graphics are worlds ahead of anything from intel. And the CPU is also pissed off. It works great under Vista. I get 4:30 battery life (no, really) and everything works, I can play games, whatever. Under Windows 7 I get 2:30 battery life, and many games blow up the driver. Under Linux I get 1:30 battery life and even with RenderAccel, GLX etc disabled I get trashing of the display whether I use vesa or ati.
AMD royally screwed the pooch on Linux support for R690M and L110 and I am forced to run Vista on my portable as a result.
Yes, I should have done more research. This is what I get for trusting AMD to provide Linux support. Never again.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
ATI has great quality hardware, but lower quality drivers/software. Nvidia it is the opposite.
I switched from Nvidia to ATI for this reason. My ATI 5750 does run Beryl suprising well. I game only on Windows 7 and I doubt performance would be good in Linux, but that can change. If ATI could get good quality drivers for Linux we would be happy to support them. The specs and code open are cryptic and only cover what appears to be a dispatcher which then transmit the code to the different parts of the GPU according to other posters here.
It is not like we are going to compete agaisnt ATI with trade secrets unless one of us has a 1 billion dollar chip fab plant.
Intel opened their speced and it helped them tremendously. Now since ATI has great integration with their bulldozer and Llamo chips new innovations would help sales. We could even improve the drivers to the point where some of the code can be contributed back to their team who develops drivers for Windows.
I have noticed that World of Warcraft runs slower in DirectX 11 vs DirectX 9 which is odd and points to the drivers needing work as Nvidia users get a 20% performance increase. Opening will help.
http://saveie6.com/
AMEN Brother!
Except there's this as well to worry... http://www.coreboot.org/Embedded_controller
how long until
Those and datasheets with half truths are a real issue.
The other side is that AMD actively contributes :-)
I do. Or rather, I did...
http://www.geeks.com/details.asp?invtid=SAMBA845V-24-4-R&cat=SYS
At that price, it's a great deal. Start a kickstart install of CentOS5.x, and deliver it to customers who need a bunch of office desktops, terminals, etc. These days, you can spend a lot of money to get super-efficient components, and still end up drawing more power, and making much more noise (above PC idles at under 40watts, and is impressively damn-near silent).
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
Well now it doesn't _require_ firmware to be closed-source. And my understanding was that typically, devices that absolutely require firmware to even work at all, well those would be the cheap corner-cutters a-la WinModem
I think you have some fundamental misunderstanding of what firmware is and does. Your CPU contains firmware to implement x86 instructions. Your HDD contains firmware to implement the ATA protocol. In fact, pretty much every piece of equipment including your motherboard and graphics card too depends on firmware, they typically all have a level between the instructions and the hardware. The only real difference is whether it's stored on the device itself or loaded by the driver during initialization.
The crazy thing here is really where the line of zealotry goes, if it's on the device itself it's fine, if the open source code must load it then it's unacceptable. Why exactly? I mean the code is there either way, if you wanted OSS purity then you should refuse everything with upgradable firmware.but without source code and documentation, since the firmware can have bugs that in theory are fixable. Except you'd be hard pressed to find any hardware at all that meets that qualification.
However in practice you have to be extremely familiar with the hardware design, most don't consider it software but more like a tweakable hardware. Like, we can alter this a little bit by flashing but it's really more for development, once the customers have it then the vast majority will never upgrade their firmware, ever. And even there is a bug it'll be so tied to the hardware that really only the people with the hardware schematics can fix it.
I guess it matters to some, but then you've moved from the <1% of the market into the <0.0001% area...
Live today, because you never know what tomorrow brings
Question: Have you tried SIW to find out what the exact chips you are running that are having Win 7 driver problems, and then replacing them with an updated driver from another model with the same chip?
Yep. I searched long and hard to find a driver that would work, and finally did. On the second resume from suspend, I get a free reboot. There is no improved power saving driver, either.
You just have to remember that with Windows there is ALWAYS more than one way to skin a cat.
The cat is a lie.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
The tearing on the secondary display is present in every card. I've had it since my first GeForce2 MX 10 years ago, GF4MX, GF 5200, 7300GT, 6150 IGP, intel GMA950 (i think), and now with Intel Core i5 on-CPU graphics. Seen it with VGA, DVI, Component, and HDMI outs. The secondary display always has tearing. That's why I have to switch primary/secondary screens when I want to watch a movie on my TV.
Not sure how it is in AMD land, but on nVidia and Intel, that's what it's like.
Name the part and I'll be happy to find the driver FOR you. Just let me know which one you tried so I don't duplicate the effort. You can then get a copy of "Windows 7 Tiny" to test it, which only uses 3Gb of HDD space installed.
Hell did you just try using the Vista driver? because the Vista/7 driver model is damned near identical, just as you could run Win2K/XP/2K3 drivers interchangeably unless you were switching from 32bit to 64bit. I personally have Vista X64 drivers running on my Windows 7 install simply because nobody bothered to write a Windows 7 driver for my USB capture card. Works beautifully BTW, great picture and integrates perfectly with WMC.
BTW did you notice I got modded down for daring to try to help you? How sad that the Moonies here.....err...I mean FOSSies, have such a groupthink circle jerk that the one and ONLY posting allowed within a thousand yards of a FOSSie story is "Gee Biff, isn't Linux perfect? Why it sure is Skip, and RMS's farts smell like roses!"
Sadly as you found out trying to run it on a laptop and I as a retailer found out trying to actually sell Linux it is MORE WORSE NOW THAN EVER thanks to Torvalds constant kernel fiddling and the driver mess. Out of the 8 machines I picked at random to test Linux on, tried a half dozen distros BTW, guess how many survived with full functionality after first upgrade? NONE. Zip, zero, nada, squat. Wireless, sound, video, Ethernet, there was ALWAYS something broken.
I could provide links to fellow retailers running away from Linux, or point out that Dell has to run their own repo just to keep drivers from breaking, but what's the point? Just like Moonies they'll just stick their fingers in their ears and go "CLI is leet! copypasta into term makes our neckbeard thick! You must be M$ Ninja!" and go back to their circle jerk, so why bother. let them enjoy 1% and ignore their crazy asses I say.
ACs don't waste your time replying, your posts are never seen by me.
This is not the case for AMD's firmware which has been happily traveling with the Linux kernel since day zero.
Stallmantitis is ridiculous.
Mod +1 Insightful.
I've been a FOSS developer for 10 years, but I still think RMS is crazier than a shithouse rat.
in AMD land you get some minor screen tearing but on all displays. At least that is my experience with a 4200HD (on board) and a dedicated 6850HD.
It isn't a showstopper though and thus I haven't tried to fix it.
The above goes for all driver editions radeon, fglrx, mesa-dri-[a-z]{3,8}-exp.*
-- no sig today
Depends on if anyone would ever consider changing the firmware. I'd say yes, it's free enough unless there was some good reason to ever change the firmware which there probably isn't.
You probably got modded down for insisting there is a solution. Of course I tried the Vista driver. I tried over a half-dozen drivers. Just finding one willing to install was a bit of a nightmare. And I must add that I never did get a driver to charge my Motorola cellphone even, and I tried like ten of those that said they would work. Windows 7 is a bit of a driver nightmare.
When I tell you that the CPU is Athlon L110 and the chipset is R690M I have told you literally everything you need to know, because that's the whole fucking computer and it's the CPU and Video I'm having problems with. But if you really want to know in detail what it is, it's a Gateway LT3103u. You should be able to find a lspci if you look around.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
No. The binary firmware is software and updatable just like any other software. When the software is not freely distributable, when you can't modify it's source, and when you can't distribute your modifications, then that software is not free-as-in-freedom.
You can't be in compliance with the GPL if you distribute an operating system with such proprietary binaries. This is problematic because some hardware these days require firmware to be loaded by the operating system. That's why distributions like Debian separate them out and require you to download these yourself.
You can distribute a GPL operating system containing non-free firmware. Linux is GPL and still it comes with firmware blobs inside its source code tarball. Debian are very strict GPL observers, yet they distribute an unsupported CD containing non-free firmware ( http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/ ).
The problem is when the firmware, beyond being non-free, is not even redistributable. In that case your only option to obtain it legally is to download it from the hardware manufacturer's (or one of its licensee's) web site, or possibly to perform surgery on the Windows drivers that came with the product.
This is not the case for AMD's firmware, which is shipped officially by themselves with the Linux kernel.
You can distribute a GPL operating system containing non-free firmware.
You can, but you won't be in compliance with the GPL if you do. Just because people ignore the rules out of practicality doesn't mean the rules aren't being broken.
Debian are very strict GPL observers, yet they distribute an unsupported CD containing non-free firmware
Interesting. I wasn't aware that they were doing this. It is, of course, a compromise on their principles. They went through a big effort to get firmware out of main and into non-free after years of compromising for the sake of practicality.
It looks like they are trying to rationalize this CD as an "unofficial" net install CD only. It might even be OK. However, if there are GPL bits included in this net install CD, then it's still the same problem.