summaryrefslogtreecommitdiffstats
path: root/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
Commit message (Collapse)AuthorAgeFilesLines
* meta-intel: update kernel SRCREVs and pin LINUX_VERSIONTom Zanussi2012-10-291-0/+2
| | | | | | | | | | Update all the linux-yocto .bbappends with the latest kernel SRCREVs and add explicit LINUX_VERSIONs for the 1.3 release, to prevent a mismatch between the kernel version actually used in the machine branch vs the version the recipe uses for the kernel image, which can change with stable updates. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* meta-chiefriver: update kernel SRCREVsTom Zanussi2012-09-211-2/+2
| | | | | | To pick up the latest meta and machine commits. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* chiefriver: update kernel SRCREVsTom Zanussi2012-07-101-2/+2
| | | | | | | To pick up most recent changes, including the matching kernel changes for the perf-scripting/perf-tui features. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* meta-intel: update some kernel SRCREVsTom Zanussi2012-05-301-2/+2
| | | | | | | Update linux-yocto_3.2 kernel SRCREVS for crownbay, emenlow, fishriver, jasperforest, sugarbay, and chiefriver. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* meta-chiefriver: use the mei kernel featureTom Zanussi2012-05-301-0/+2
| | | | | | | | Add AMT/mei support as a kernel feature here instead of in the linux-yocto metadata - mei support is currently a feature in staging, and not everyone might want a tainted kernel. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* meta-chiefriver: new layer for Chief River (Ivy Bridge/Panther Point) systemsTom Zanussi2012-05-301-0/+8
This layer provides support for Ivy Bridge + Panther Point Intel systems. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>