Re: [meta-intel] [Patch v4 3/6] intel-microcode: a recipe for Intel microcode datafile
On Mon, Jul 28, 2014 at 01:57:08PM +0100, Burton, Ross wrote: On 25 July 2014 17:49, Kamble, Nitin A nitin.a.kam...@intel.com wrote: Maybe we can wait for the intel microcode to go intoe linux-firmware, then this recipe will not be needed at all. But for that to happen intel-microcode needs to show up in the linux-firmware repo, and I will push on that instead of pushing this recipe. This seems like the path of least pain for us certainly. What does this mean for this series? Is it on hold until such time as linux-firmware includes the necessary bins? Are we confident it will be updated frequently enough? -- Darren -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [Patch v4 3/6] intel-microcode: a recipe for Intel microcode datafile
-Original Message- From: Darren Hart [mailto:dvh...@linux.intel.com] Sent: Tuesday, July 29, 2014 8:33 AM To: Burton, Ross Cc: Kamble, Nitin A; meta-intel@yoctoproject.org; Zanussi, Tom; Hart, Darren Subject: Re: [meta-intel] [Patch v4 3/6] intel-microcode: a recipe for Intel microcode datafile On Mon, Jul 28, 2014 at 01:57:08PM +0100, Burton, Ross wrote: On 25 July 2014 17:49, Kamble, Nitin A nitin.a.kam...@intel.com wrote: Maybe we can wait for the intel microcode to go intoe linux-firmware, then this recipe will not be needed at all. But for that to happen intel- microcode needs to show up in the linux-firmware repo, and I will push on that instead of pushing this recipe. This seems like the path of least pain for us certainly. What does this mean for this series? Is it on hold until such time as linux- firmware includes the necessary bins? Are we confident it will be updated frequently enough? These are the open questions for now. And I am trying to find the responsible person for this effort to get answers. Nitin -- Darren -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [Patch v4 3/6] intel-microcode: a recipe for Intel microcode datafile
On 7/29/14, 9:25, Kamble, Nitin A nitin.a.kam...@intel.com wrote: -Original Message- From: Darren Hart [mailto:dvh...@linux.intel.com] Sent: Tuesday, July 29, 2014 8:33 AM To: Burton, Ross Cc: Kamble, Nitin A; meta-intel@yoctoproject.org; Zanussi, Tom; Hart, Darren Subject: Re: [meta-intel] [Patch v4 3/6] intel-microcode: a recipe for Intel microcode datafile On Mon, Jul 28, 2014 at 01:57:08PM +0100, Burton, Ross wrote: On 25 July 2014 17:49, Kamble, Nitin A nitin.a.kam...@intel.com wrote: Maybe we can wait for the intel microcode to go intoe linux-firmware, then this recipe will not be needed at all. But for that to happen intel- microcode needs to show up in the linux-firmware repo, and I will push on that instead of pushing this recipe. This seems like the path of least pain for us certainly. What does this mean for this series? Is it on hold until such time as linux- firmware includes the necessary bins? Are we confident it will be updated frequently enough? These are the open questions for now. And I am trying to find the responsible person for this effort to get answers. I don't know for sure, but I would *guess* David Woodhouse - or at least start with him. Nitin -- Darren -- Darren Hart Open Source Technology Center darren.h...@intel.com Intel Corporation -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [Patch v4 3/6] intel-microcode: a recipe for Intel microcode datafile
On 25 July 2014 17:49, Kamble, Nitin A nitin.a.kam...@intel.com wrote: Maybe we can wait for the intel microcode to go intoe linux-firmware, then this recipe will not be needed at all. But for that to happen intel-microcode needs to show up in the linux-firmware repo, and I will push on that instead of pushing this recipe. This seems like the path of least pain for us certainly. Ross -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [Patch v4 3/6] intel-microcode: a recipe for Intel microcode datafile
This recipe is in current state marked as click-through license, needing a special license specified in LICENSE_FLAGS_WHITELIST var. In this state the recipe can not be enabled by default. Also worth noting here is that, * This recipe is similar to linux-firmware recipe, which does not use the whitelist flags for license. * Linux distributions like redhat are enabling microcode loading without any special license agreement requirements * AMD is shipping microcode in the linux-firmware package * Intel microcode is also planned to be distributed through the linux-firmware repo. (https://fedorahosted.org/microcode_ctl/) I will ping internally who is responsible for it, as this is not happening as of now. Maybe we can wait for the intel microcode to go intoe linux-firmware, then this recipe will not be needed at all. But for that to happen intel-microcode needs to show up in the linux-firmware repo, and I will push on that instead of pushing this recipe. Thanks, Nitin -Original Message- From: Kamble, Nitin A Sent: Friday, July 18, 2014 5:18 PM To: Zanussi, Tom; Hart, Darren; richard.pur...@linuxfoundation.org; Burton, Ross Cc: meta-intel@yoctoproject.org; Kamble, Nitin A Subject: [Patch v4 3/6] intel-microcode: a recipe for Intel microcode datafile From: Nitin A Kamble nitin.a.kam...@intel.com This recipe provides the microcode datafile for Intel Processors. The recipe provides: 1. microcode.dat file for microcode updating from user space with the iucode-tool utility. 2. the microcode cpio file which gets bundled with the initrd to support microcode loading at early boot time. Note that this recipe has LICENSE_FLAGS so will need to be whitelisted before it's usable. [ YOCTO #5114 ] Signed-off-by: Ross Burton ross.bur...@intel.com Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- common/custom-licenses/Intel-Microcode-License | 123 + .../microcode/intel-microcode_20140624.bb | 53 + 2 files changed, 176 insertions(+) create mode 100644 common/custom-licenses/Intel-Microcode-License create mode 100644 common/recipes-core/microcode/intel- microcode_20140624.bb diff --git a/common/custom-licenses/Intel-Microcode-License b/common/custom-licenses/Intel-Microcode-License new file mode 100644 index 000..af5b41c --- /dev/null +++ b/common/custom-licenses/Intel-Microcode-License @@ -0,0 +1,123 @@ +INTEL SOFTWARE LICENSE AGREEMENT + +IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING. +Do not use or load this software and any associated materials +(collectively, the Software) until you have carefully read the +following terms and conditions. By loading or using the Software, you +agree to the terms of this Agreement. If you do not wish to so agree, do not install or use the Software. + +LICENSES: Please Note: +- If you are a network administrator, the Site License below shall +apply to you. +- If you are an end user, the Single User License shall apply to you. +- If you are an original equipment manufacturer (OEM), the OEM License +shall apply to you. + +SITE LICENSE. You may copy the Software onto your organization's +computers for your organization's use, and you may make a reasonable +number of back-up copies of the Software, subject to these conditions: + +1. This Software is licensed for use only in conjunction with Intel +component products. Use of the Software in conjunction with non-Intel +component products is not licensed hereunder. +2. You may not copy, modify, rent, sell, distribute or transfer any +part of the Software except as provided in this Agreement, and you +agree to prevent unauthorized copying of the Software. +3. You may not reverse engineer, decompile, or disassemble the Software. +4. You may not sublicense or permit simultaneous use of the Software by +more than one user. +5. The Software may include portions offered on terms in addition to +those set out here, as set out in a license accompanying those portions. + +SINGLE USER LICENSE. You may copy the Software onto a single computer +for your personal, noncommercial use, and you may make one back-up copy +of the Software, subject to these conditions: + +1. This Software is licensed for use only in conjunction with Intel +component products. Use of the Software in conjunction with non-Intel +component products is not licensed hereunder. +2. You may not copy, modify, rent, sell, distribute or transfer any +part of the Software except as provided in this Agreement, and you +agree to prevent unauthorized copying of the Software. +3. You may not reverse engineer, decompile, or disassemble the Software. +4. You may not sublicense or permit simultaneous use of the Software by +more than one user. +5. The Software may include portions offered on terms in addition to +those set out here, as set out in a license accompanying those portions. + +OEM LICENSE:
[meta-intel] [Patch v4 3/6] intel-microcode: a recipe for Intel microcode datafile
From: Nitin A Kamble nitin.a.kam...@intel.com This recipe provides the microcode datafile for Intel Processors. The recipe provides: 1. microcode.dat file for microcode updating from user space with the iucode-tool utility. 2. the microcode cpio file which gets bundled with the initrd to support microcode loading at early boot time. Note that this recipe has LICENSE_FLAGS so will need to be whitelisted before it's usable. [ YOCTO #5114 ] Signed-off-by: Ross Burton ross.bur...@intel.com Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- common/custom-licenses/Intel-Microcode-License | 123 + .../microcode/intel-microcode_20140624.bb | 53 + 2 files changed, 176 insertions(+) create mode 100644 common/custom-licenses/Intel-Microcode-License create mode 100644 common/recipes-core/microcode/intel-microcode_20140624.bb diff --git a/common/custom-licenses/Intel-Microcode-License b/common/custom-licenses/Intel-Microcode-License new file mode 100644 index 000..af5b41c --- /dev/null +++ b/common/custom-licenses/Intel-Microcode-License @@ -0,0 +1,123 @@ +INTEL SOFTWARE LICENSE AGREEMENT + +IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING. +Do not use or load this software and any associated materials (collectively, +the Software) until you have carefully read the following terms and +conditions. By loading or using the Software, you agree to the terms of this +Agreement. If you do not wish to so agree, do not install or use the Software. + +LICENSES: Please Note: +- If you are a network administrator, the Site License below shall +apply to you. +- If you are an end user, the Single User License shall apply to you. +- If you are an original equipment manufacturer (OEM), the OEM License +shall apply to you. + +SITE LICENSE. You may copy the Software onto your organization's computers +for your organization's use, and you may make a reasonable number of +back-up copies of the Software, subject to these conditions: + +1. This Software is licensed for use only in conjunction with Intel +component products. Use of the Software in conjunction with non-Intel +component products is not licensed hereunder. +2. You may not copy, modify, rent, sell, distribute or transfer any part +of the Software except as provided in this Agreement, and you agree to +prevent unauthorized copying of the Software. +3. You may not reverse engineer, decompile, or disassemble the Software. +4. You may not sublicense or permit simultaneous use of the Software by +more than one user. +5. The Software may include portions offered on terms in addition to those +set out here, as set out in a license accompanying those portions. + +SINGLE USER LICENSE. You may copy the Software onto a single computer for +your personal, noncommercial use, and you may make one back-up copy of the +Software, subject to these conditions: + +1. This Software is licensed for use only in conjunction with Intel +component products. Use of the Software in conjunction with non-Intel +component products is not licensed hereunder. +2. You may not copy, modify, rent, sell, distribute or transfer any part +of the Software except as provided in this Agreement, and you agree to +prevent unauthorized copying of the Software. +3. You may not reverse engineer, decompile, or disassemble the Software. +4. You may not sublicense or permit simultaneous use of the Software by +more than one user. +5. The Software may include portions offered on terms in addition to those +set out here, as set out in a license accompanying those portions. + +OEM LICENSE: You may reproduce and distribute the Software only as an +integral part of or incorporated in Your product or as a standalone +Software maintenance update for existing end users of Your products, +excluding any other standalone products, subject to these conditions: + +1. This Software is licensed for use only in conjunction with Intel +component products. Use of the Software in conjunction with non-Intel +component products is not licensed hereunder. +2. You may not copy, modify, rent, sell, distribute or transfer any part +of the Software except as provided in this Agreement, and you agree to +prevent unauthorized copying of the Software. +3. You may not reverse engineer, decompile, or disassemble the Software. +4. You may only distribute the Software to your customers pursuant to a +written license agreement. Such license agreement may be a break-the- +seal license agreement. At a minimum such license shall safeguard +Intel's ownership rights to the Software. +5. The Software may include portions offered on terms in addition to those +set out here, as set out in a license accompanying those portions. + +NO OTHER RIGHTS. No rights or licenses are granted by Intel to You, expressly +or by implication, with respect to any proprietary information or patent, +copyright, mask work, trademark, trade secret, or other intellectual
