This fixes the audio playback issue for BSPs using this kernel.
Also the AMT support is fixed by using these updated SRCREVs.
Addresses Bug:
[YOCTO #6140]
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
In keeping with the other BSPs in meta-intel, specify the
PREFERRED_PROVIDER and the PREFERRED_VERSION for the linux-yocto kernel
to 3.14. Move the assignments below the required includes in keeping
with the rest of meta-intel.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Use meta-intel@yoctoproject.org as maintainer's email address.
Signed-off-by: Ong Boon Leong <boon.leong.ong@intel.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
The linux-yocto/meta support is now available for the intel-core*
machines and the preempt-rt kernel. Enable the common PACKAGE_ARCH in
intel-common-pkgarch.inc.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Now the common kernel recipes are working for the NUC BSP, use it in place
of the BSP specific kernel.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
In the intel common kernel recipes, instead of corei7-64-intel-common,
intel-corei7-64-intel-common was specified as override. This was masking
the KMACHINE and KBRANCH variables defined in these recipes causing
unexpected build issues for kernels of BSPs like nuc.
Fixes bug:
[YOCTO #6123]
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Update the SRCREV to the latest available for 3.10. This includes a fix for
LTSI changes, which fixes the boot issue on emenlow.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Extend the linux-yocto_3.14 recipe from poky layer to meta-intel layer.
This kernel recipe is shared by multiple BSPs from the meta-intel layer.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Make all the LINUX_VERSION variables in various kernel recipes machine specific
to avoid name-space pollution.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Update to the HEAD of standard/base (3.10.34-LTSI). This also works
around an open issue with do_validate_branches where feature branches
are reset the HEAD of the machine branch if they contain that commit.
The common linux-yocto_3.10 kernel is not able to find root device on
the NUC platform. Hence the NUC BSP is not yet updated to use the
common kernel.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
Update to the HEAD of standard/base (3.10.34-LTSI). This also works
around an open issue with do_validate_branches where feature branches
are reset the HEAD of the machine branch if they contain that commit.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Reviewed-by: Darren Hart <dvhart@linux.intel.com>
Update to the HEAD of standard/base (3.10.34-LTSI).
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
Update to the HEAD of standard/base (3.10.34-LTSI). This also works
around an open issue with do_validate_branches where feature branches
are reset the HEAD of the machine branch if they contain that commit.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
Update the commit of the machine branch standard/base to 3.10.25 commit.
After 3.10.25 the LTSI changes are causing kernel panic at boot on emenlow.
A fix for this boot issue is out, but not yet integrated in to the LTSI
kernel. Once the LTSI kernel has the fix, the emenlow 3.10 kernel can be
updated to the latest 3.10 LTSI kernel.
This also works around an open issue with do_validate_branches where
feature branches are reset the HEAD of the machine branch if they contain
that commit.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
The below commit didn't actually remove all the files from the BSPs
retired - the BSP directories were still there with unremoved files in
them - this actually finishes the removal.
commit 8d79fb4e0c
Author: Nitin A Kamble <nitin.a.kamble@intel.com>
Date: Wed Mar 12 12:12:32 2014 -0700
Remove chiefriver, sys940x & n450 BSPs
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Define the kernel branch SRCREVs in meta-intel layer, so that other
layers can not break the common BSP kernel unknowingly.
Using the latest HEADs of the git branches for SRCREVs.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Reviewed-by: Darren Hart <dvhart@linux.intel.com>
Configuration for the chiefriver, sys940x, sys940x-noemgd, n450 BSPs are
deleted. The consolidated BSPs viz intel-corei7-64 and intel-core2-32
support these boards.
As part of the usual retirement process, a heads-up email was sent to the
meta-intel mailing list requesting any feedback regarding retirement of
these BSPs. The community did not had any concerning feedback to
reconsider the retirement decision.
The MAINTAINERS file and the layer version of the meta-intel layer are
updated to reflect removal of the BSPs.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
CC: Darren Hart <dvhart@linux.intel.com>
Reviewed-by: Darren Hart <dvhart@linux.intel.com>
The automatic SRCREV AUTOREV anonymous python in linux-yocto-dev.bb
will only trigger on the PREFERRED_PROVIDER_virtual/kernel being
linux-yocto-dev if it is set in local.conf, or a similar file parsed
prior to itself.
Since these two machines currently specify linux-yocto-dev in the
machine configuration, the AUTOREV doesn't trigger - and we do not want
AUTOREV specified in the recipe itself to avoid breakage in the event
of no network access.
This is a bizarre little corner case as machines typically do not
specify linux-yocto-dev. For the time being, fix the do_fetch failure by
specifying SRCREVs for the two intel-core* machines. Users who want
AUTOREV can specify THAT in their local.conf. This way it doesn't break
out of the box.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Update to the HEAD of standard/fri2 (3.10.33-LTSI). This also works
around an open issue with do_validate_branches where feature branches
are reset the HEAD of the machine branch if they contain that commit.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
The following commit:
Update linux-yocto-rt 3.8 to 3.10
46fd4b45c7
Failed to add the new 3.10 recipes, resulting in build failures for
machines not taking advantage of the intel-common-pkgarch.
Add the linux-yocto-rt bbappend to those BSPs.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
The PREFERRED_PROVIDER_virtual/kernel was assigned with = instead of ?=,
preventing the user from overriding the setting with something like
linux-yocto-rt. Use ?=.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Reported-by: Teemu Keskinarkaus <Teemu.Keskinarkaus@Maximatecc.com>
Cc: Tom Zanussi <tom.zanussi@intel.com>
Both the Ivy Bridge and Haswell nuc systems are covered supported by the
intel-corei7-64 BSP. The HDMI audio requires manual configuration which
is handled by a machine-specific script in the nuc BSP. A general
solution to this sort of problem is in the works.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Nothing in meta-intel requires these and now
they are in OE-core anyway.
Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Update the SRCREV to the latest available for 3.10. This includes a
stable update to 3.10.32 and an LTSI update. Fixes the emgd build
failure with the latest LTSI.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Tested-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Acked-by: Nitin Kamble <nitin.a.kamble@intel.com>
Remove all redundant linux-yocto recipes where the BSP is able to reuse
the intel-common version.
Update the common bbappends with the KERNEL_FEATURES and
module_autoload* statements from the consolidated bbappends.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
The current development branch (for 1.6) supports 3.10 and -dev
linux-yocto kernels. Delete all the lingering 3.8 kernel recipes.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
The current development branch (for 1.6) supports 3.10 and -dev
linux-yocto kernels. Delete all the lingering 3.4 kernel recipes.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Enable the intel-common pkgarch and machine override mechanism for most
non-emgd BSPs. The Queensbay platforms show issues on the 3.10 kernel,
and the NUC is experiencing some boot issues with the common kernel, so
skip those for now.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Add a README describing the intel-core* (intel-common) BSPs and the
Linux kernel package architecture. Includes a list of currently tested
BSPs compatible with the intel-common BSPs.
Update the top-level README with a reference to this new README for the
intel-common BSPs.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
