move intel bsps to v3.4 kernel

From: Nitin A Kamble <[email protected]>

These commits move Intel BSPs to v3.4 kernel.
The crownbay v3.4 kernel is not quet ready yet, so for crown bay the default kerenl is still v3.2

The following changes since commit f5dcebe57832551219da048945237a7cf7bda369:

linux-firmware: Fix FILESEXTRAPATHS typo (2012-06-20 13:12:12 -0700)

are available in the git repository at:
git://git.yoctoproject.org/meta-intel-contrib nitin/work
http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/work

Nitin A Kamble (7):
FishRiver: add recipe extention for linux-yocto_3.4
FishRiver: set v3.4 as the default kernel recipe version
emenlow: add recipe extention for linux-yocto_3.4
emenlow: set v3.4 as the default kernel recipe version
sugarbay: add recipe extention for linux-yocto_3.4
sugarbay: set v3.4 as the default kernel recipe version
crownbay: add recipe extention for linux-yocto-3.4

 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |   15 +++++++++++++++
 meta-emenlow/conf/machine/emenlow.conf             |    2 +-
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |    8 ++++++++
 meta-fishriver/conf/machine/fishriver.conf         |    2 +-
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |    8 ++++++++
 meta-sugarbay/conf/machine/sugarbay.conf           |    2 +-
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |    9 +++++++++
 7 files changed, 43 insertions(+), 3 deletions(-)
 create mode 100644 meta-crownbay/recipes-kernel/linux/linux-yocto_3.4.bbappend
 create mode 100644 meta-emenlow/recipes-kernel/linux/linux-yocto_3.4.bbappend
 create mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
 create mode 100644 meta-sugarbay/recipes-kernel/linux/linux-yocto_3.4.bbappend

1.7.3.4

From: Nitin A Kamble <[email protected]>

Tested this on FishRiver hardware, and it works as expected.

---
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)
 create mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend

new file mode 100644
index 0000000..eaa6229
@@ -0,0 +1,8 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+COMPATIBLE_MACHINE_fishriver = "fishriver"
+KMACHINE_fishriver  = "fishriver"
+KBRANCH_fishriver  = "standard/fishriver"
+
+SRCREV_machine_pn-linux-yocto_fishriver ?= "49f1599b2ce0288599805b5364b895f5a9febb3e"
+SRCREV_meta_pn-linux-yocto_fishriver ?= "a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5"

1.7.3.4

From: Nitin A Kamble <[email protected]>

---
 meta-fishriver/conf/machine/fishriver.conf |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

index 289e41d..ec2e87f 100644
@@ -4,7 +4,7 @@
 #@DESCRIPTION: Machine configuration for Fish River Island systems
 # i.e. Z530/E660 + EG20T
 
-PREFERRED_VERSION_linux-yocto ?= "3.2%"
+PREFERRED_VERSION_linux-yocto ?= "3.4%"
 
 require conf/machine/include/tune-atom.inc
 require conf/machine/include/ia32-base.inc

1.7.3.4

From: Nitin A Kamble <[email protected]>

This is tested on the emenlow hardware, and it works as expected.

---
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)
 create mode 100644 meta-emenlow/recipes-kernel/linux/linux-yocto_3.4.bbappend

new file mode 100644
index 0000000..2146864
@@ -0,0 +1,8 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+COMPATIBLE_MACHINE_emenlow = "emenlow"
+KMACHINE_emenlow  = "emenlow"
+KBRANCH_emenlow  = "standard/emenlow"
+
+SRCREV_machine_pn-linux-yocto_emenlow ?= "1ed16752ff068c2a3f33d78d8a53be32416fb56e"
+SRCREV_meta_pn-linux-yocto_emenlow ?= "a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5"

1.7.3.4

From: Nitin A Kamble <[email protected]>

---
 meta-emenlow/conf/machine/emenlow.conf |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

index 26ca43b..afb3866 100644
@@ -4,7 +4,7 @@
 #@DESCRIPTION: Machine configuration for eMenlow based systems, like the
 # Webs-2120 box.
 
-PREFERRED_VERSION_linux-yocto ?= "3.2%"
+PREFERRED_VERSION_linux-yocto ?= "3.4%"
 
 require conf/machine/include/tune-atom.inc
 require conf/machine/include/ia32-base.inc

1.7.3.4

From: Nitin A Kamble <[email protected]>

This is tested on the HuronRiver (sugarbay laptop) platform, and it works as expected.

---
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |    9 +++++++++
 1 files changed, 9 insertions(+), 0 deletions(-)
 create mode 100644 meta-sugarbay/recipes-kernel/linux/linux-yocto_3.4.bbappend

new file mode 100644
index 0000000..581b18e
@@ -0,0 +1,9 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+COMPATIBLE_MACHINE_sugarbay = "sugarbay"
+
+KMACHINE_sugarbay  = "sugarbay"
+KBRANCH_sugarbay  = "standard/common-pc-64/sugarbay"
+
+SRCREV_machine_pn-linux-yocto_sugarbay ?= "49f1599b2ce0288599805b5364b895f5a9febb3e"
+SRCREV_meta_pn-linux-yocto_sugarbay ?= "a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5"

1.7.3.4

From: Nitin A Kamble <[email protected]>

---
 meta-sugarbay/conf/machine/sugarbay.conf |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

index adb1fa7..a80c938 100644
@@ -4,7 +4,7 @@
 #@DESCRIPTION: Machine configuration for Sugar Bay systems
 # i.e. Sandy Bridge + Cougar Point
 
-PREFERRED_VERSION_linux-yocto ?= "3.2%"
+PREFERRED_VERSION_linux-yocto ?= "3.4%"
 
 require conf/machine/include/tune-x86_64.inc
 require conf/machine/include/ia32-base.inc

1.7.3.4

From: Nitin A Kamble <[email protected]>

In testing on the crownbay hardware found that, X is failing due to missing emgd driver. Hence the v3.4 kernel is not made the default kernel for crownbay bsps yet.

---
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |   15 +++++++++++++++
 1 files changed, 15 insertions(+), 0 deletions(-)
 create mode 100644 meta-crownbay/recipes-kernel/linux/linux-yocto_3.4.bbappend

new file mode 100644
index 0000000..60c1a0c
@@ -0,0 +1,15 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+COMPATIBLE_MACHINE_crownbay = "crownbay"
+KMACHINE_crownbay  = "crownbay"
+KBRANCH_crownbay  = "standard/default/crownbay"
+
+COMPATIBLE_MACHINE_crownbay-noemgd = "crownbay-noemgd"
+KMACHINE_crownbay-noemgd  = "crownbay"
+KBRANCH_crownbay-noemgd  = "standard/crownbay"
+
+SRCREV_machine_pn-linux-yocto_crownbay ?= "49f1599b2ce0288599805b5364b895f5a9febb3e"
+SRCREV_meta_pn-linux-yocto_crownbay ?= "a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5"
+
+SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?= "49f1599b2ce0288599805b5364b895f5a9febb3e"
+SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?= "a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5"

1.7.3.4

Sorry for the delay, took awhile partly because some higher-priority things intruded, and partly because I had doubts that emenlow would work with just a simple version bump - historically emenlow has caused a lot of pain with kernel upgrades and needed extensive modifications to work. So I had to test it myself and found that indeed it works fine.

Pulled in all of the above, and added my Tested-by: to emenlow.

I didn't pull this in since as you mention, it breaks graphics, and we really can't pull it in if that's the case, even if it isn't made the default...

Thanks,

Tom