X

Intel, Red Hat cure open-source hiccup

Red Hat and Intel come up with a solution to a licensing problem that threatened to prevent the Linux company from contributing to the tech giant's open-source project.

Stephen Shankland Former Principal Writer
Stephen Shankland worked at CNET from 1998 to 2024 and wrote about processors, digital photography, AI, quantum computing, computer science, materials science, supercomputers, drones, browsers, 3D printing, USB, and new computing technology in general. He has a soft spot in his heart for standards groups and I/O interfaces. His first big scoop was about radioactive cat poop.
Expertise Processors, semiconductors, web browsers, quantum computing, supercomputers, AI, 3D printing, drones, computer science, physics, programming, materials science, USB, UWB, Android, digital photography, science. Credentials
  • Shankland covered the tech industry for more than 25 years and was a science writer for five years before that. He has deep expertise in microprocessors, digital photography, computer hardware and software, internet standards, web technology, and more.
Stephen Shankland
3 min read
Red Hat and Intel have settled a licensing hiccup that threatened to prevent the Linux company from contributing to Intel's open-source project--a reminder of the frictions that can arise between the commercial tech world and the open-source community.

The wrangling came to an end last week when Intel changed licensing terms for the software project. It involved one component of power management software used in Linux and several other operating systems. The component--an "interpreter," which interprets a computer's power management abilities--is an Intel open-source project that Red Hat had been trying to help with. But legal complications connected to the licenses governing the interpreter had hampered Red Hat from contributing.

Intel's interpreter was originally governed by two licenses--the open-source General Public License (GPL) and the proprietary "component architecture" (CA) license. However, when Red Hat wanted to submit improvements covered under the GPL, that license prohibited Intel from incorporating those changes in the proprietary version of the software covered by the CA license.

Intel says it has now expanded the interpreter licensing for the GPL version, adding a variant of the BSD license, which is more liberal than the GPL. The dual licensing essentially bypasses a GPL provision that requires all improvements to GPL-covered software to also be brought under the GPL--which means now improvements may be made proprietary as well as open-source.

"It allows everyone to help improve the code, while still allowing the code to be used by everyone, not just Linux," said Guy Therien, principal engineer of mobile software architecture in Intel's mobile platforms group, in a statement to CNET News.com.

Intel's move illustrates the legal complications that crop up as the open-source community intersects ever more frequently with the closed, proprietary world of the traditional computing industry.

Alan Cox, a Red Hat employee and one of the top deputies to Linux leader Linus Torvalds, appears mollified by the new approach. "The business about how to feed patches is one that's--I think--resolved," he said in a posting to the Linux mailing list for power management.

The interpreter at the center of the wrangling is part of a technology called Advanced Configuration and Power Interface (ACPI), the successor to the older Advanced Power Management technology. ACPI was developed by Compaq Computer, Intel, Microsoft, Phoenix Technologies and Toshiba.

Red Hat is working to make contributions to the power management software--which computers use to control tasks such going into hibernation mode--and to ACPI, to bring these into its version of Linux. ACPI is moving from the domain of development project to shipping product. The latest test version of Red Hat Linux, code-named "Phoebe," included ACPI and was released in December.

It's not the first time open-source licenses have been changed to better accommodate the proprietary computing world. Ximian adopted a more liberal license for some of its Mono software to create an open-source version of Microsoft's .Net, so that Intel software could be incorporated into the project.

Intel proposed the BSD license change in December on the Linux kernel mailing list. Torvalds was among those who chimed in about the move, saying that dual licenses cover several other important sections of Linux kernel software.