[meta-intel] [PATCH 0/4] Use */intel branches in genericX86 BSPs

In order to provide more timely support for Intel platforms, this patchset switches the genericX86 BSPs over to using a set of dedicated */intel branches created for linux-yocto 4.1 and 4.4 kernels. These branches and the corresponding kernel metadata branches provide a place to add

[meta-intel] [PATCH 4/4] linux-yocto/4.4: Make standard/intel branches available

meta-yocto-bsp BSPs inherit SRCREV_meta - update it to include some new branches for the BSPs there. Signed-off-by: Tom Zanussi --- meta/recipes-kernel/linux/linux-yocto_4.4.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[meta-intel] [PATCH 1/4] meta-yocto-bsp: Switch linux-yocto 4.4 genericx86* BSPs to standard/intel

There is now a dedicated standard/intel branch for Intel platforms, so have the genericx86* BSPs use it. Signed-off-by: Tom Zanussi --- meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff

[meta-intel] [PATCH 2/4] meta-yocto-bsp: Switch linux-yocto 4.1 genericx86* BSPs to standard/intel

There is now a dedicated standard/intel branch for Intel platforms, so have the genericx86* BSPs use it. Signed-off-by: Tom Zanussi --- meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff

[meta-intel] [PATCH 5/8] intel-common-pkgarch: Set common PACKAGE_ARCH for linux-yocto-tiny

The linux-yocto-tiny metadata assumes the common PACKAGE_ARCH but without this is actually machine-specific and broken. Signed-off-by: Tom Zanussi --- conf/machine/include/intel-common-pkgarch.inc | 1 + 1 file changed, 1 insertion(+) diff --git

[meta-intel] [PATCH 4/8] linux-yocto-rt/4.1: Switch to standard/preempt-rt/intel

We now have a dedicated standard/preempt-rt/intel branch for Intel platforms, so have the the 4.1 rt kernel recipe make use of it. Signed-off-by: Tom Zanussi --- common/recipes-kernel/linux/linux-yocto-rt_4.1.bbappend | 2 +- 1 file changed, 1 insertion(+), 1

[meta-intel] [PATCH 2/8] linux-yocto-rt/4.4: Switch to standard/preempt-rt/intel

We now have a dedicated standard/preempt-rt/intel branch for Intel platforms, so have the the 4.4 rt kernel recipe make use of it. Signed-off-by: Tom Zanussi --- common/recipes-kernel/linux/linux-yocto-rt_4.4.bbappend | 2 +- 1 file changed, 1 insertion(+), 1

[meta-intel] [PATCH 6/8] linux-yocto-tiny/4.4: Switch to standard/tiny/intel

We now have a dedicated standard/tiny/intel branch for Intel platforms, so have the the 4.4 tiny kernel recipe make use of it. Signed-off-by: Tom Zanussi --- common/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend | 2 +- 1 file changed, 1 insertion(+), 1

[meta-intel] [PATCH 8/8] linux-yocto-tiny: Fix broken SRCREV specifications

linux-yocto-tiny uses hyphens rather than underscores between SRCREV and the machine or meta specification, preventing it from actually taking effect. Fix it by changing the hyphens to underscores. Signed-off-by: Tom Zanussi ---

[meta-intel] [PATCH 0/8] Add and use */intel branches

In order to provide more timely support for Intel platforms, this patchset makes use of a set of dedicated */intel branches being created for linux-yocto 4.1 and 4.4 kernels. These branches and the corresponding kernel metadata branches provide a place to add Intel-specific features and updates

[meta-intel] [PATCH 1/8] linux-yocto/4.4: Switch to standard/intel

We now have a dedicated standard/intel branch for Intel platforms, so have the the 4.4 kernel recipe make use of it. Signed-off-by: Tom Zanussi --- common/recipes-kernel/linux/linux-yocto_4.4.bbappend | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[meta-intel] [PATCH 3/8] linux-yocto/4.1: Switch to standard/intel

We now have a dedicated standard/intel branch for Intel platforms, so have the the 4.1 kernel recipe make use of it. Signed-off-by: Tom Zanussi --- common/recipes-kernel/linux/linux-yocto_4.1.bbappend | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [meta-intel] [PATCH] canterbury-corpus: Use base_libdir in FILES

> So I doubt they're loaded by the firmware loader (they are random data files, > a > compression test corpus) but maybe they are being used in a test inside the > kernel and > the firmware directory is hack to find them? > > I'm CCing some people who have touched the qat16 recipe lately (as it