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>
Add common values for the various MACHINE_ variables, derived from the
existing BSPs in meta-intel. Include EFI and PCBIOS, 3G and wifi
support, and video decoding. Include the linux-firmware package.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
For the intel-common BSPs, assume a default serial console of
ttyS0 at 115200 BAUD. This will ensure the configuration is
in place and is easy to find and modify on the resulting images.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Include support for x86, ext, i9xx, fbdev, vesa, and modesetting
drivers, as well as matrox for the 64b machines (for the Xeon server
class systems).
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Since the PACKAGECONFIG parameters were changed in the libva.inc file
for the newer version of the libva recipe, this older version of libva
recipe started throwing following QA warning.
WARNING: QA Issue: libva: configure was passed unrecognised options:
--enable-wayland --enable-x11
Fix the warning by nullifying PACKAGECONFIG variables coming from
libva.inc.
Fixes Bug:
[YOCTO #5764]
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
* Disable the dumper since it needs swig and python3;
* refresh the install-fitter.patch;
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
With ${B} != ${S} the build fails due to files being accessed incorrectly.
Disable the functionlaity for now until the software can be fixed.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The trailing S was missing from the variable name, resulting in
the kernel-modules package not being found as the common arch was not
added to the PACKAGE_ARCHS variable used by the package manager.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
For various (good) reasons we needed to adjust bitbake so that PN
is only set in bbappend/bb files, not from conf/inc files since
in many cases this was leading to odd/unexpected behaviour.
The variable can be used in these files however it cannot be
expanded, as it is here. We therefore need to remove the expansion
and replace with the real string. This fixes builds in master.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building GL apps for non-x86 machines (e.g. raspberrypi)
emgd-driver-bin is being dragged in as a valid provider. To avoid
build breakage fix it at the source by limiting emgd-driver-bin to x86
architectures.
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Acked-By: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Support the intel-common package arch and BSPs on linux-yocto-3.10 as
well.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
(cherry picked from commit e75ea81899beb885d892e5f5bf995c445981da3f)
The following commit:
3d270e3 jasperforest: Correct typo in machine config tune file
introduced a bug with an incorrect required include filename, correct
it.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Reported-by: Nitin A. Kamble <nitin.a.kamble@intel.com>
Currently the intel-core*-common.inc files also include the
intel-common-pkgarch.inc, forcing the introduction of the intel-common
PACKAGE_ARCH. Coupling this with the addition of the intel-common
MACHINE_OVERRIDE, means that even MACHINE_ARCH packages can be
influenced by intel-common overrides, which is not desirable.
Remove the intel-common-pkgarch.inc from the intel-core*common.inc
include files, requiring BSPs wanting to use the intel-common mechanism
to explicitly include it. This obviates the need to reset the
linux-yocto PACKAGE_ARCH to MACHINE_ARCH.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
