summaryrefslogtreecommitdiffstats
path: root/meta-crystalforest/recipes-kernel/linux/linux-yocto-rt_3.4.bbappend
Commit message (Collapse)AuthorAgeFilesLines
* Remove linux-yocto rt and tiny 3.4 recipesDarren Hart2014-03-121-20/+0
| | | | | | 3.4 is no longer supported, drop the 3.4 rt and tiny recipes as well. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* intel-common: Make using intel-common override opt-inDarren Hart2014-02-051-2/+0
| | | | | | | | | | | | | | | | Currently the intel-core*-common.inc files also include the intel-common-pkgarch.inc, forcing the introduction of the intel-common PACKAGE_ARCH. Coupling this with the addition of the intel-common MACHINE_OVERRIDE, means that even MACHINE_ARCH packages can be influenced by intel-common overrides, which is not desirable. Remove the intel-common-pkgarch.inc from the intel-core*common.inc include files, requiring BSPs wanting to use the intel-common mechanism to explicitly include it. This obviates the need to reset the linux-yocto PACKAGE_ARCH to MACHINE_ARCH. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
* crystalforest: Set PACKAGE_ARCH to MACHINE_ARCH explicitlyDarren Hart2014-01-271-0/+3
| | | | | | | | | The new intel-common.inc sets the default of the PACKAGE_ARCH for the linux-yocto kernel recipes to DEFAULTTUNE_kernel. Revert the existing recipes to MACHINE_ARCH until they can be removed in favor of a more unified mechanism. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* meta-intel: remove kernel AUTOREVsTom Zanussi2013-02-041-4/+6
| | | | | | | | Using AUTOREV turns out to cause problems with unreproducible autobuilder builds and unwanted network access. This patch removes kernel AUTOREVs and locks down SRCREVs and LINUX_VERSIONs. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
* meta-intel: remove explicit kernel SRCREVsTom Zanussi2012-11-131-4/+4
| | | | | | | | | | | | | | | To ease development on unreleased BSPs, let the kernel SRCREV float. This avoids constantly having to update the SRCREVs manually, and assures we won't get into a situation where LINUX_VERSION doesn't match the version set by the kernel recipe. We'll lock down the kernel SRCREVs and set the matching LINUX_VERSION when we do releases, but in the meantime, we can use AUTOREV. Note that individual BSPs are always free to override this maintain their own SRCREVs if they want to. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* crystalforest: Change the machine namesKishore Bodke2012-10-291-11/+10
| | | | | | | | | | Change the Machine names for the two machines that will be used to publish the BSP on the Yocto Project website. And add the Yocto Project Compliance information for the 1.3 release. Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* meta-crystalforest: Update SRCREV for meta.Kishore Bodke2012-10-151-2/+2
| | | | | | | | Update SRCREVs of meta branch to include the new PCI config options added. Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* meta-crystalforest: Crystal Forest BSP Created.1.3_M4.rc11.3_M4Kishore Bodke2012-09-071-0/+18
Initial checkin for the new Crystal Forest BSP. This BSP is based on Sandybridge CPU and Cave Creek Chipset. Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>