Q1. I am the package maintainer for <distribution X> and we would like to create a package/distribution/CD that installs/provides the Intel firmware. How does one go about doing this according to Intel terms?
A1. There are three key actions that must be performed:
Generally distributors alert end users to the fact that components of a package may be covered under a variety of licenses, the specific terms of which vary. Some distributors use an initial license page during the OS install that informs the user that various components are governed by a variety of licenses, and use of the components is subject to the user's compliance with the various licensing requirements. Other package systems support an interactive package approach that requires the user to view and accept the license before they can install it, etc.
As a subset of the first requirements above, any description within the package must indicate that the package is covered by the Intel license, and provide the user with information on how to access that license -- making it clear that the user is not granted a license to use the package unless these terms are agreed to.
The package must install the LICENSE file in the same location on the system that the firmware files are installed. If it is standard practice in your distribution to place all license files in a centralized location (for example /usr/share/license), then you are free to place a copy of the license in that location, in addition to placing it in the directory containing the firmware files.
Q2. We do not have any type of a "click through" license for each package that is installed, and our packages aren't typically used to create a new OS image.
A2. The important point is to make sure that the end user is notified that the firmware component is governed by an Intel license and provided with a copy of the license terms prior to downloading or using the software. In the event that the package is automatically downloaded by a package update tool, and that tool provides no provision to indicate to the user that they are installing software that is covered by such a license, following A1.2 and A1.3 above is sufficient.
Q3. I am an end user and I want to be able to make a bootable Linux CD for a friend of mine to use, and I want to include the firmware.
A3. Intel fully supports this type of sharing. The key point to realize is that by becoming the provider of the software, in as much as the Intel license is concerned, you are essentially acting as an ISV (independent software vendor) and as such, you must comply with the Intel license provisions governing ISVs (see A1 above).
This applies to: