Intel Releases Ivy Bridge Programming Docs Under CC License
An anonymous reader writes "The Ivy Bridge graphics processor from Intel is now fully documented under the Creative Commons. Intel released four volumes of documents (2400+ pages) covering their latest graphics core as a complete programming guide with register specifications. Included with the graphics documentation is their new execution unit and video engine."
nVidia should have bit the bullet and done the same thing. Could have benefited them financially and boosted consumer satisfaction.
If you won't allow us to write software for your crappy cards, then they'll be no software for your cards. I don't understand why these Microsoft-style closed source morons always think not allowing people to use what they sell will help them. They're letting their paranoia get in the way of good business.
And a showstopper for those other graphic card makers (AMD/NVIDIA) with their halfbaked support for Linux.
I would've got first post, but I'm still reading TFA. Only two thousand pages to go...
The documentation referenced is available from Intel Linux Graphics: Documentation.
We've come a long way since the 47 registers and paltry documentation of the Commodore 64's 6567 video chip. My question is, who can actually master these modern systems before they are obsolete? No one person, I think, can gobble 2400 pages of documentation to work with a graphics system. Are people now merely specialists of one tiny subset of a system, never to understand what is going on overall? That might explain why we need 600M device drivers these days.
This is a release of a large and very complete set of formal documents, but open source driver code (GPL'd and part of the mainline Linux kernel) has been released under a public development process since just after Sandy Bridge first came out in preparation for the Ivy Bridge launch. This code is written by paid Intel employees.
Incidentally, large portions of the DRM infrastructure in the kernel *and* the X server *and* the upcoming Wayland project are all being made by paid Intel employees. Note that this development work also has major benefits to the open-source AMD driver development and we would all be better off if AMD (not to mention Nvidia) adopted Intel's approach to paying people for open-source work.
In a similar manner, there is already 100% GPL'd code that is available for the next-generation Haswell graphics engines. Obviously at this stage it isn't complete, but things are not hidden behind closed doors and, just like Ivy Bridge, there should be solid launch-day support for the Haswell IGP. Considering the rumours going around about the extra resources that Haswell will offer for the GPU, this could chip could provide very solid launch-day out-of-the-box graphics support in notebooks and other devices that don't require a dicrete GPU.
AntiFA: An abbreviation for Anti First Amendment.
This is a good thing - it means that open-source drivers can now be written that will be adequate for most users. Unless you are doing heavy 3D gaming or HTPC, Intel's products are fine.
For HTPC, Intel would be a great choice if only they'd finally fix that lingering 23.976 FPS bug. They just don't seem to be taking it that seriously, though, since it's existed since the G45 days at least. Also, I don't know if this is supported through the registers (even the documents may not make it clear) but it would be great to have real YCbCr 4:2:2 output – AMD cards claim to do this, but they are actually converting the data from YCbCr (on DVD/Blu-Ray) to RGB and then back to YCbCr for output. Allowing source-direct YCbCr output (which currently only dedicated SoCs can do) and fixing the 23.976 FPS problems would make Intel-based HTPCs a viable option at the high end. (Advanced videophiles want to use a dedicated scaler device, which offers much better scaling and/or deinterlacing results than what software and average standalone players can do.)
Direct link without the Phoronix fluff:
http://intellinuxgraphics.org/documentation.html
...by releasing their documentation under the Creative Commons license, Intel saved enough money in lawyer fees to purchase a new fab...
http://www.beanleafpress.com
Well, both Intel and Linux have come a long way since the Pentium 4 era, so I don't think it's fair to use a 10-year-old chipset as an example to avoid Intel GPUs now. Is also isn't fair comparing a 2002 iGPU to a 2007 iGPU. Of course the 7025 still works and is supported - it's much newer. My 2003 FX card, however, won't render anything GTK3 properly, it's completely abandoned by Nvidia and a very low priority for nouveau developers.
Intel publishes ( for free ) nearly all their architecture documents. It's been their business model since the beginning... how else would the X86 platform exist?
Someone clearly fell asleep in the 1990s, when Intel were so terrified of the V86 extensions being copied by AMD that they wouldn't tell anyone except Microsoft how they worked. People actually reverse-engineered it and released their own documentation before Intel was willing to allow things like Linux DOSEMU to use it. This did not endear me to Intel back in the day.
Indeed, an interesting relic from that era is my Turbo Assembler 5 manual. It has a number of blank entries in it for Pentium instructions, e.g.
RDTSC (Proprietary instruction. Contact Intel for more Information.") - Turbo Assembler Quick Reference, p.118
Man, it seems like every other sentence in that article is a link to another Phoronix article. I count 14 Phoronix links in there, and the actual link to the Intel docs is buried in the middle of that.
http://intellinuxgraphics.org/documentation.html
Mada mada dane.
That's a great press release and AMD is better than Nvidia since AMD does publish at least partial documentation.. *but*... support for newer AMD cards in the open source drivers has major issues. As of right now, the 7 series cards that have been out for over 6 months have basically no support under the open source drivers. The 6 series and older cards are improving, but Catalyst is still leagues ahead in OpenGL performance and support. The documentation for the AMD cards is not release until months after the cards ship, and there is basically zero open-source development done prior to launch, so there is a long lead time between the cards being available and the cards being usable in any form under Linux (except through Catalyst, which has its own issues).
One big issue is that the Mesa & open source graphics stack has just recently even gotten support for OpenGL 3.0. The standards support under the proprietary Nvidia & AMD cards is, ironically, far ahead of the open source implementations.
AntiFA: An abbreviation for Anti First Amendment.
Intel has enough hardware developers that the don't typically need to license third party IP to get the job done. Many silicon vendors don't have that luxury and cannot risk incidental leaks of IP details for which they could be held liable. Lets see how much documentation Intel releases for the Atom smartphone chips with PowerVR GPUs.