| Age | Commit message (Collapse) | Author |
|---|
|
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>
|
|
Create the bbappend to build intel-common -rt linux-yocto 3.10 kernels
for all intel-common BSPs.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
3.8 is no longer supported, update the remaining 3.8-rt recipes to 3.10.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
3.8 is no longer supported, update the tiny bbappend to 3.10.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
3.4 is no longer supported, drop the 3.4 rt and tiny recipes as well.
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>
|
|
Include support for Intel Active Management Technology version 8+ on the NUC BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
The old URL is not working anymore. Using a new URL for source zip file.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@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>
|
|
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@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>
|
|
Create the intel common override for use in currently machine-specific
recipes which need to make overrides for all the compatible machines,
such as COMPATIBLE_MACHINES in the linux-yocto* recipes.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
The intel-core* BSPs now have their own BSP description in linux-yocto.
Update the recipe accordingly.
All the existing BSPs (with the exception of the emgd variants) are now
supported across these two BSPs.
For machines that derive from the intel-common-pkgarch, allow the
common linux-yocto-dev recipe to build for them by specifying $MACHINE
for the common machine overrides (core2-32-intel-common and
corei7-64-intel-common).
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
The usb webcam media fragment is already included in the
common-pc-64-standard BSP definition which is included by the sugarbay
standard BSP description. There should be no need to duplicate that
here.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Move the "reboot=pci" quirk from the linux-yocto BSP definition to the
machine config APPEND line. This pushes config space stuff up into the
meta-intel machine definition where it is more accessible and allows for
consolidation in the linux-yocto level.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Nitin Kamble <nitin.a.kamble@intel.com>
|
|
Ensure package strip logic stays the
same after oe-core package.bbclass changes.
See http://patches.openembedded.org/patch/65311/
Signed-off-by: Koen Kooi <koen.kooi@linaro.org>
Tested-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
The new intel-common.inc sets the default of the PACKAGE_ARCH for the
linux-yocto kernel recipes to DEFAULTTUNE_kernel. Revert the existing
recipes to MACHINE_ARCH until they can be removed in favor of a more
unified mechanism.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
The new intel-common.inc sets the default of the PACKAGE_ARCH for the
linux-yocto kernel recipes to DEFAULTTUNE_kernel. Revert the existing
recipes to MACHINE_ARCH until they can be removed in favor of a more
unified mechanism.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
The new intel-common.inc sets the default of the PACKAGE_ARCH for the
linux-yocto kernel recipes to DEFAULTTUNE_kernel. Revert the existing
recipes to MACHINE_ARCH until they can be removed in favor of a more
unified mechanism.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
The new intel-common.inc sets the default of the PACKAGE_ARCH for the
linux-yocto kernel recipes to DEFAULTTUNE_kernel. Revert the existing
recipes to MACHINE_ARCH until they can be removed in favor of a more
unified mechanism.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
The new intel-common.inc sets the default of the PACKAGE_ARCH for the
linux-yocto kernel recipes to DEFAULTTUNE_kernel. Revert the existing
recipes to MACHINE_ARCH until they can be removed in favor of a more
unified mechanism.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
The new intel-common.inc sets the default of the PACKAGE_ARCH for the
linux-yocto kernel recipes to DEFAULTTUNE_kernel. Revert the existing
recipes to MACHINE_ARCH until they can be removed in favor of a more
unified mechanism.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
The new intel-common.inc sets the default of the PACKAGE_ARCH for the
linux-yocto kernel recipes to DEFAULTTUNE_kernel. Revert the existing
recipes to MACHINE_ARCH until they can be removed in favor of a more
unified mechanism.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
The new intel-common.inc sets the default of the PACKAGE_ARCH for the
linux-yocto kernel recipes to DEFAULTTUNE_kernel. Revert the existing
recipes to MACHINE_ARCH until they can be removed in favor of a more
unified mechanism.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
The new intel-common.inc sets the default of the PACKAGE_ARCH for the
linux-yocto kernel recipes to DEFAULTTUNE_kernel. Revert the existing
recipes to MACHINE_ARCH until they can be removed in favor of a more
unified mechanism.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
The new intel-common.inc sets the default of the PACKAGE_ARCH for the
linux-yocto kernel recipes to DEFAULTTUNE_kernel. Revert the existing
recipes to MACHINE_ARCH until they can be removed in favor of a more
unified mechanism.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
The new intel-common.inc sets the default of the PACKAGE_ARCH for the
linux-yocto kernel recipes to DEFAULTTUNE_kernel. Revert the existing
recipes to MACHINE_ARCH until they can be removed in favor of a more
unified mechanism.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Sandy Bridge based CPUs benefit from the new corei7 tune file.
Update the XSERVER_* variables to use the new naming.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
Sandy Bridge and Ivy Bridge based CPUs benefit from the new corei7 tune file.
Update the XSERVER_* variables to use the new naming.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Haw Foo Chien <foo.chien.haw@intel.com>
Cc: Ong Boon Leong <boon.leong.ong@intel.com>
|
|
Ivy Bridge based CPUs benefit from the new corei7 tune file.
Update the XSERVER_* variables to use the new naming.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
Nehalem based CPUs benefit from the new corei7 tune file.
Update the XSERVER_* variables to use the new naming.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
Haswell based CPUs benefit from the new corei7 tune file.
Update the XSERVER_* variables to use the new naming.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Ong Boon Leong <boon.leong.ong@intel.com>
|
|
The Z5xx Atom CPUs are supported by the core2 tune file.
Update the XSERVER_* variables to use the new naming.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Nitin A Kamble <nitin.a.kamble@intel.com>
|
Darren Hart
Stefan Stanacar
Nitin A Kamble
Laurentiu Palcu
Richard Purdie
Koen Kooi
Koen Kooi