aboutsummaryrefslogtreecommitdiffstats
path: root/meta-intel-extras/classes
Commit message (Collapse)AuthorAgeFilesLines
* intel: update grub-efi file nameSamuli Piippo2017-08-171-2/+7
| | | | | Change-Id: I732eb903c0e92585e603e52ac8c250364d8cb031 Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
* meta-intel: update to morty branchSamuli Piippo2017-03-221-1/+1
| | | | | | | Fix grub-efi build by using correct variable for image deploy dir. Change-Id: I1298f58dbedbaa9af9b67908a2c99d0c288cecdd Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
* Update image creation recipes, appends etc. to be poky 2.2 compliantMikko Gronoff2017-03-141-1/+1
| | | | | | | | DEPLOY_DIR_IMAGE macro has been replaced with IMGDEPLOYDIR in poky 2.2. Update all instances to make image creation work. Change-Id: I3740730ded84650d3a3a51b85c77ed4fef863a8a Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
* intel-corei7-64: fix race in image generationLouai Al-Khanji2016-07-291-9/+0
| | | | | | | | | | | | | | | | Prepending to IMAGE_CMD_ext3 in order to push files into the rootfs is flaky for a couple of reasons. First, it is conceptually inconsistent with the rest of the build system - files that go into the rootfs should really by installed by packages through the regular mechanisms. Second, and what prompted this patch, with several concurrent image generation tasks this is just unsafe. I regularly experienced .tgz image generation failures, as tar complained that the files changed from under it. Since this is related to the grub-efi packaging on this particular device, just package the microcode into the required initramfs in that recipe. Change-Id: I4e037ddbb017d1764852310b0b77900cde260dd6 Reviewed-by: Gatis Paeglis <gatis.paeglis@qt.io>
* Update license headersSamuli Piippo2016-05-181-7/+15
| | | | | | | License changed to GPLv3 + Commercial Change-Id: I267c97216e717ed29071df064337e1bcf83de973 Reviewed-by: Kalle Viironen <kalle.viironen@theqtcompany.com>
* NUC: use the common intel-corei7-64 BSPSamuli Piippo2016-04-081-0/+45
meta-intel no longer has specific BSPs for each machine, but they share a common BSP based on the architecture. Change-Id: Ibbb7b8b2153103367168ea37d904ce23bc245108 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>