Commit Graph

13 Commits

Author SHA1 Message Date
Nitin A Kamble
b77b3504de chiefriver: linux-yocto_3.8 recipe extension
Provide the chiefriver BSP specific extension for the linux-yocto_3.8
recipe from the oecore layer. This configures the right git branches of
the kernel repository for the chiefriver BSP.

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2013-03-06 15:33:58 -06:00
Nitin A Kamble
443a85b572 chiefriver: linux-yocto-dev recipe extension
Provide the chiefriver BSP specific extension for the linux-yocto-dev
recipe from the oecore layer. This configures the right git branches of
the kernel repository for the chiefriver BSP.

This commit is addressing this bug:
[YOCTO #3931]

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2013-03-04 16:54:44 -06:00
Tom Zanussi
575f93dd4b meta-intel: remove kernel AUTOREVs
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>
2013-02-04 10:39:06 -06:00
Tom Zanussi
787d5d8c93 meta-intel: remove explicit kernel SRCREVs
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>
2012-11-13 09:24:46 -06:00
Tom Zanussi
3898886e63 meta-intel: update kernel SRCREVs and pin LINUX_VERSION
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>
2012-10-29 18:04:05 -05:00
Nitin A Kamble
81f53c90aa chiefriver: update kernel repo srcrevs
Keeping up2date with the latest HEADs of the branches
from kernel v3.4 repository

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2012-10-16 21:13:25 -05:00
Nitin A Kamble
7a5aec127d chiefriver: uprev v3.4 kernel commit ids
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2012-10-04 14:20:44 -05:00
Tom Zanussi
7051c73970 meta-chiefriver: update kernel SRCREVs
To pick up the latest meta and machine commits.

Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2012-09-21 15:24:27 -05:00
Tom Zanussi
5d0c08cd8b meta-chiefriver: switch to linux-yocto-3.4 kernel
Switch chiefriver to the 3.4 kernel and update kernel SRCREVs.

Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2012-07-17 22:07:15 -05:00
Tom Zanussi
cad140b804 chiefriver: update kernel SRCREVs
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>
2012-07-10 15:34:04 -05:00
Tom Zanussi
ceab55d2d6 meta-intel: update some kernel SRCREVs
Update linux-yocto_3.2 kernel SRCREVS for crownbay, emenlow,
fishriver, jasperforest, sugarbay, and chiefriver.

Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2012-05-30 14:22:52 -05:00
Tom Zanussi
d5ebd785cb meta-chiefriver: use the mei kernel feature
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>
2012-05-30 14:22:51 -05:00
Tom Zanussi
37dee2e3ea meta-chiefriver: new layer for Chief River (Ivy Bridge/Panther Point) systems
This layer provides support for Ivy Bridge + Panther Point Intel systems.

Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2012-05-30 14:22:51 -05:00