sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity
generic-poky/meta/recipes-kernel/linux/linux-yocto_3.4.bb

33 lines
1.2 KiB
BlitzBasic
Raw Normal View History

linux-yocto: add 3.4 recipe Introducing the 3.4 kernel recipe. At this point there are three supported kernel 3.4, 3.2 and 3.0. Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and qemuppc (From OE-Core rev: f85c3f727fd326fe6dd2f2c2b68c692515867737) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-06-07 19:59:47 +00:00
require recipes-kernel/linux/linux-yocto.inc
linux-yocto/3.4: remove explicit KBRANCH designations A BSP specific KBRANCH assignment is no longer a required element to locate and build a yocto kernel. As such we can set the default kbranch, and remove all other explicit assignments. KBRANCH is still used, and if it is changed from the default, that branch will be built. (From OE-Core rev: 7984a9f6ccd00bf282c9eedab7ab933add68448c) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-05 18:39:17 +00:00
KBRANCH_DEFAULT = "standard/base"
KBRANCH = "${KBRANCH_DEFAULT}"
linux-yocto: add 3.4 recipe Introducing the 3.4 kernel recipe. At this point there are three supported kernel 3.4, 3.2 and 3.0. Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and qemuppc (From OE-Core rev: f85c3f727fd326fe6dd2f2c2b68c692515867737) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-06-07 19:59:47 +00:00
linux-yocto/3.4: update to v3.4.24 Updating the 3.4 recipes to v3.4.24 stable version. (From OE-Core rev: c3e97905f423e2bab2a0aadf5099ef445f0dd138) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-07 15:43:04 +00:00
SRCREV_machine_qemuarm ?= "50986c7d971c28505acdbdcab6601f4d5b6dbff4"
SRCREV_machine_qemumips ?= "4d355c57fe0d9f117c272f1679fa3d3f451a8c8e"
SRCREV_machine_qemuppc ?= "1c8a1aa8cc839f0328edbfe0d755100368bc4ae6"
SRCREV_machine_qemux86 ?= "5432e2acb6053f9f7563cf63abd101ed2fdc1b6f"
SRCREV_machine_qemux86-64 ?= "5432e2acb6053f9f7563cf63abd101ed2fdc1b6f"
SRCREV_machine ?= "5432e2acb6053f9f7563cf63abd101ed2fdc1b6f"
SRCREV_meta ?= "7e0cd2990798aae80565baa17d3b6c771874f284"
linux-yocto: add 3.4 recipe Introducing the 3.4 kernel recipe. At this point there are three supported kernel 3.4, 3.2 and 3.0. Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and qemuppc (From OE-Core rev: f85c3f727fd326fe6dd2f2c2b68c692515867737) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-06-07 19:59:47 +00:00
linux-yocto/3.4: inform the fetcher if the meta branch changes The meta data branch for the kernel can be varied by changing the KMETA variable, but that change wasn't reflected in the SRC_URI, which means that the fetcher won't check for changes on that branch and is a potential source of errors. Making the meta branch specification KMETA vs meta solves the problem. (From OE-Core rev: 5bfc678aeb65b50710384e93b64add3a62146908) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-29 21:37:33 +00:00
SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},${KMETA};name=machine,meta"
linux-yocto: add 3.4 recipe Introducing the 3.4 kernel recipe. At this point there are three supported kernel 3.4, 3.2 and 3.0. Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and qemuppc (From OE-Core rev: f85c3f727fd326fe6dd2f2c2b68c692515867737) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-06-07 19:59:47 +00:00
linux-yocto/3.4: update to v3.4.24 Updating the 3.4 recipes to v3.4.24 stable version. (From OE-Core rev: c3e97905f423e2bab2a0aadf5099ef445f0dd138) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-07 15:43:04 +00:00
LINUX_VERSION ?= "3.4.24"
linux-yocto: add 3.4 recipe Introducing the 3.4 kernel recipe. At this point there are three supported kernel 3.4, 3.2 and 3.0. Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and qemuppc (From OE-Core rev: f85c3f727fd326fe6dd2f2c2b68c692515867737) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-06-07 19:59:47 +00:00
qemux86-64: Support for KVM, paravirt and virtio added KVM, paravirtualization and virtio drivers are now activated in runqemu using the kvm option flag for qemux86-64. Host CPU features are also exported to guest OS (Yocto Linux). Usage example: runqemu qemux86-64 core-image-x11 kvm Implements [YOCTO #2550]. (From OE-Core rev: cbb6431b3ee9128ea15c9ae0a19e7d2998ffc561) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-19 07:06:55 +00:00
PR = "${INC_PR}.3"
linux-yocto: add 3.4 recipe Introducing the 3.4 kernel recipe. At this point there are three supported kernel 3.4, 3.2 and 3.0. Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and qemuppc (From OE-Core rev: f85c3f727fd326fe6dd2f2c2b68c692515867737) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-06-07 19:59:47 +00:00
PV = "${LINUX_VERSION}+git${SRCPV}"
KMETA = "meta"
linux-yocto: Remove parens from COMPATIBLE_MACHINE regexp This helps in appending to this regexp from bbappends coming from other layers who want to leverage linux-yocto with minimum tweaks by using a standard prefefined machine from linux-yocto (From OE-Core rev: 32ba716e71fb7a16f13c83ab6c8cc51de56b3be2) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-08-22 17:59:48 +00:00
COMPATIBLE_MACHINE = "qemuarm|qemux86|qemuppc|qemumips|qemux86-64"
linux-yocto: add 3.4 recipe Introducing the 3.4 kernel recipe. At this point there are three supported kernel 3.4, 3.2 and 3.0. Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and qemuppc (From OE-Core rev: f85c3f727fd326fe6dd2f2c2b68c692515867737) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-06-07 19:59:47 +00:00
# Functionality flags
KERNEL_REVISION_CHECKING=""
linux-yocto*: append to KERNEL_FEATURES instead of assigning It is sometimes useful for KERNEL_FEATURES to be set in a machine or other configuration file. The linux-yocto recipes currently initialize the variable, which clobbers any values set by .conf files. Appending to the variables allows these settings to propagate to the kernel configuration, while maintaining the existing set of added kernel features. (From OE-Core rev: 7121fe8d836fc178e9ab8f0e6f8eb34a99325c81) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-11 13:05:14 +00:00
KERNEL_FEATURES_append = " features/netfilter"
linux-yocto: add 3.4 recipe Introducing the 3.4 kernel recipe. At this point there are three supported kernel 3.4, 3.2 and 3.0. Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and qemuppc (From OE-Core rev: f85c3f727fd326fe6dd2f2c2b68c692515867737) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-06-07 19:59:47 +00:00
KERNEL_FEATURES_append_qemux86=" cfg/sound"
KERNEL_FEATURES_append_qemux86-64=" cfg/sound"
qemux86: Support for KVM, paravirt and virtio added KVM, paravirtualization and virtio drivers are now activated in runqemu using the kvm option flag for qemux86. Host CPU features are also exported to guest OS (Yocto Linux). Usage example: runqemu qemux86 core-image-x11 kvm Implements [YOCTO #2550]. (From OE-Core rev: a35d03e2eb905de4eadc9c7df5b50bff1fb7f897) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-19 07:06:54 +00:00
KERNEL_FEATURES_append_qemux86=" cfg/paravirt_kvm"
qemux86-64: Support for KVM, paravirt and virtio added KVM, paravirtualization and virtio drivers are now activated in runqemu using the kvm option flag for qemux86-64. Host CPU features are also exported to guest OS (Yocto Linux). Usage example: runqemu qemux86-64 core-image-x11 kvm Implements [YOCTO #2550]. (From OE-Core rev: cbb6431b3ee9128ea15c9ae0a19e7d2998ffc561) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-19 07:06:55 +00:00
KERNEL_FEATURES_append_qemux86-64=" cfg/paravirt_kvm"
linux-yocto/3.4: add x32 configuration fragment When x32 is the tuning for a x86 MACHINE, the kernel should also have CONFIG_X86_X32=y. This adds a x32 fragment that can be used to trigger the right ABI. The commit also contains a check for mx32 in TUNE_FEATURES, and if present, the new fragment will be appended to KERNEL_FEATURES and trigger the support in the kernel. cc: Saul Wold <sgw@linux.intel.com> (From OE-Core rev: bf689c60caa905eb8866101b9e99dd4ae246a2ca) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-11 15:04:41 +00:00
KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32", "" ,d)}"