On 2/11/14, 7:52, "[email protected]" <[email protected]> wrote:
>From: "Chang, Rebecca Swee Fun" <[email protected]> > >Provide kernel v3.8 recipe for valleyisland BSP. Valley Island >BSP supports PCI mode and ACPI mode enumeration for its LPSS >I/O devices. Kernel recipe will enable PCI mode enumeration by >default. > >Signed-off-by: Chang, Rebecca Swee Fun <[email protected]> >--- > .../recipes-kernel/linux/linux-yocto_3.8.bbappend | 33 >++++++++++++++++++++ > 1 file changed, 33 insertions(+) > create mode 100644 >meta-isg/meta-valleyisland/recipes-kernel/linux/linux-yocto_3.8.bbappend > >diff --git >a/meta-isg/meta-valleyisland/recipes-kernel/linux/linux-yocto_3.8.bbappend > >b/meta-isg/meta-valleyisland/recipes-kernel/linux/linux-yocto_3.8.bbappend >new file mode 100644 >index 0000000..f46e5c3 >--- /dev/null >+++ >b/meta-isg/meta-valleyisland/recipes-kernel/linux/linux-yocto_3.8.bbappend >@@ -0,0 +1,33 @@ >+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" >+ >+KMETA = "meta" >+ >+############################# >+# MACHINE = valleyisland-32 # >+############################# >+COMPATIBLE_MACHINE_valleyisland-32 = "valleyisland-32" >+KMACHINE_valleyisland-32 = "valleyisland-32" >+KBRANCH_valleyisland-32 = "standard/common-pc/base" This needn't block this series, but we are trying to use standard/base for Intel bsps whenever possible. The common-pc branches are currently (I don't know about 3.8, you'd have to check) at the same commit as standard/base. Since standard/base is the default KBRANCH, you also have the option of not specifying it at all and not specifying the SRCREVs either, relying on the base recipe values. This does add some risk to you however as your BSP can change without your knowledge if the base recipe updates the SRCREVs - this is typically what you want as no effort is required on your part for the stable updates. If you don't specify the KBRANCH or the SRCREVs, you don't have to specify the LINUX_VERSION either as the default matches the default SRCREVs. It is something you will have to weigh and decide what is best for your team. Again, this is fine as it is, just wanted to point that out in case it impacts your choice here. Same below. -- Darren >+KERNEL_FEATURES_valleyisland-32 = >"features/valleyisland-io/valleyisland-io \ >+ >features/valleyisland-io/valleyisland-io-pci.scc \ >+ " >+ >+LINUX_VERSION_valleyisland-32 = "3.8.13" >+SRCREV_machine_pn-linux-yocto_valleyisland-32 ?= >"6f3e338aa9496cf68ad03a98f66c2e98975829c7" >+SRCREV_meta_pn-linux-yocto_valleyisland-32 ?= >"f87180481b12aebd16b9234d922d5f4a25a32dca" >+ >+############################# >+# MACHINE = valleyisland-64 # >+############################# >+COMPATIBLE_MACHINE_valleyisland-64 = "valleyisland-64" >+KMACHINE_valleyisland-64 = "valleyisland" >+KBRANCH_valleyisland-64 = "standard/common-pc-64/base" >+KERNEL_FEATURES_valleyisland-64 = >"features/valleyisland-io/valleyisland-io \ >+ >features/valleyisland-io/valleyisland-io-pci.scc \ >+ " >+ >+LINUX_VERSION_valleyisland-64 = "3.8.13" >+SRCREV_machine_pn-linux-yocto_valleyisland-64 ?= >"6f3e338aa9496cf68ad03a98f66c2e98975829c7" >+SRCREV_meta_pn-linux-yocto_valleyisland-64 ?= >"f87180481b12aebd16b9234d922d5f4a25a32dca" >+ >+module_autoload_i2c-dev = "i2c-dev" >-- >1.7.10.4 > >_______________________________________________ >meta-intel mailing list >[email protected] >https://lists.yoctoproject.org/listinfo/meta-intel > _______________________________________________ meta-intel mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-intel
