Intel learns from Sandy Bridge mistakes, but is it enough?
Subject: General Tech, Graphics Cards, Processors | June 24, 2011 - 01:13 PM | Scott Michaud
Tagged: linux, Ivy Bridge, Intel
Back when Sandy Bridge launched, Intel had some difficulty with Linux compatibility due to their support software not being available long enough ahead of launch for distribution developers to roll it in to their releases. As a result, users purchasing Sandy Bridge hardware would be in for a frolic in the third-party repositories unless they wished to wait four or five months for their distributions to release their next major version. This time Intel is pushing code out much earlier though questions still remain if they will fully make Ubuntu’s 11.10 release.
You mean there's Intel... inside me?
Intel came down hard on themselves for their Sandy Bridge support. Jesse Barnes, an open-source Linux developer at Intel, posted on the Phoronix Forums his thoughts on the Sandy Bridge Linux issue:
"No, this is our job, and we blew it for Sandy Bridge. We're supposed to do development well ahead of product release, and make sure distros include the necessary code to get things working … Fortunately we've learned from this and are giving ourselves more time and planning better for Sandy Bridge's successor, Ivy Bridge."
Now, six months later as support for Ivy Bridge is getting released and rolled into their necessary places, Intel appears to be more successful than last time. Much of the code that Intel needs to release for Ivy Bridge is already available and rolled in to the Linux 3.0 kernel. A few features missed the deadline and must be rolled in to Linux 3.1 kernel. While Phoronix believes that Fedora 16 will still be able to roll in support in time it is possible that Ubuntu 11.10 may not unless the back-port the changes to their distribution. That is obviously not something Intel would like to see happen given all their extra effort of recent.