| Age | Commit message (Collapse) | Author |
|---|
|
Enable the Intel microcode feature for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
|
|
Enable the Intel microcode feature for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
|
|
Enable the Intel microcode feature for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
|
|
Enable the Intel microcode feature for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
|
|
Enable the Intel microcode feature for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
|
|
Enable the Intel microcode feature for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
|
|
Enable the Intel microcode feature for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
|
|
Enable the Intel microcode feature for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
|
|
Starting a new documentation section to describe the layer specific hardware
features. At this point the intel-ucode machine feature is described here.
In the future more such features will be described in this section.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
The microcode data file released by Intel has microcode for many Intel
processors. And all these get installed on the target image. In some
situations it may desired to pick microcode for only selected processor
or processors.
This change provides an easier way to filter and pick only the microcode
of interest for BSPs from the recipe space.
A new variable, UCODE_FILTER_PARAMETERS is introduced, which can be
redefined containing parameters of the iucode_tool to filter the microcodes
of interest for the BSP under consideration. The information on the
iucode-tool parameters are available here: http://manned.org/iucode-tool .
The filtering makes the generated microcode files very machine specific,
hence making the recipe machine specific. The BSPs using the common Intel
kernel will not be using the filtered microcode, and these will be able to
share the intel-microcode packages with the common Intel package arch for
the recipe.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
With this change, the Intel microcode support can be enabled or disabled
for any BSP by controlling the MACHINE_FEATURES variable.
Any BSP from meta-intel layer can enable the Intel microcode loading support
by adding the following line in the machine configuration.
MACHINE_FEATURES += "intel-ucode"
This change keeps the intel-microcode loading feature disabled by default,
and it is enabled as an "opt-in" feature using the MACHINE_FEATURES variable.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
The iucode-tool is needed to apply microcode updates from user land.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
Use the latest HEADs of the git branches from the linux-yocto v3.17
kernel repository.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The gmx500 graphics driver does not work on this BSP, but it takes the
ownership of the graphics hardware at boot time, blocking other
drivers from using the graphics hardware.
Fix the issue by blacklisting the gma500_gfx kernel module in the kmod
configuration, so that it doesn't get loaded at boot time.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The gmx500 graphics driver does not work on this BSP, but it takes the
ownership of the graphics hardware at boot time, blocking other
drivers from using the graphics hardware.
Fix the issue by blacklisting the gma500_gfx kernel module in the kmod
configuration, so that it doesn't get loaded at boot time.
Fixes Bug:
[YOCTO #6807]
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The Huron River platform targeted by this BSP has wifi capability.
The common kernel used by the BSP has already enabled wifi drivers.
Enable the user space wifi tools, which give functional wifi
networking to the Huron River platform.
Fixes Bug:
[YOCTO #6342]
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
Added support for DPDK v1.7.0.
Added PACKAGECONFIG mechanism to explicitly disable the use of fuse
and qat which are dependencies for example apps dpdk_qat and vhost.
Added config variables CONFIG_EXAMPLE_DPDK_QAT and
CONFIG_EXAMPLE_DPDK_VHOST to enable or disable the compilation of
example apps dpdk_qat and vhost.
Resolved the installation failure found in example app ip_pipeline by
cherry-picking the patch from dpdk.org.
Resolved the test failure found in example app ring_pmd_autotest by
cherry-picking the patches from dpdk.org.
Signed-off-by: Sreeju Selvaraj <sreeju.armughanx.selvaraj@intel.com>
Acked-by: Ong Boon Leong <boon.leong.ong@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
Added include file dpdk.inc to share common functionality based on
dpdk_1.6.0r2
Added a new variable EXAMPLE_BUILD_DIR. this points to apps build
directory which is different in dpdk v1.6.0r2 and v1.7.0.
Users of dpdk.inc have to define EXAMPLE_BUILD_DIR for the
installation of example apps.
Signed-off-by: Sreeju Selvaraj <sreeju.armughanx.selvaraj@intel.com>
Acked-by: Ong Boon Leong <boon.leong.ong@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The layer priority is getting ignored because the same set of files
are visible in the meta-intel layer as well as any of its sub layers.
The layer pattern for recipe files is changed from "^${LAYERDIR}/" to
"^${LAYERDIR}/common" to stop unintentionally including the sub-layer
recipe files in the meta-intel layer.
Fixes Bug:
[YOCTO #6552]
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The linux-yocto_3.17 recipe is available for this BSP. Make it the
default kernel for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The linux-yocto_3.17 recipe is available for this BSP. Make it the
default kernel for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The linux-yocto_3.17 recipe is available for this BSP. Make it the
default kernel for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The linux-yocto_3.17 recipe is available for this BSP. Make it the
default kernel for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The linux-yocto_3.17 recipe is available for this BSP. Make it the
default kernel for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The linux-yocto_3.17 recipe is available for this BSP. Make it the
default kernel for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The linux-yocto_3.17 recipe is available for this BSP. Make it the
default kernel for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The linux-yocto_3.17 recipe is available for this BSP. Make it the
default kernel for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
Extend the linux-yocto_3.17 recipe from the oe-core layer for the use
of meta-intel BSPs.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
Use the common kernel as now it supports the gma500 driver.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
So that it can be easily overridden from local.conf.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
Fixes [YOCTO 6710] linux-yocto-rt recipe failing to build
This meta update reorganizes the intel-common ktype and driver meta
data which was causing the wrong branch to be checked out, resulting in
a build failure for the rt kernel. Update both linux-yocto and
linux-yocto-rt to use the updated intel-common meta data.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Bruce Ashfield <bruce.ashfield@windriver.com>
Acked-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
When the target sysroot is populated the binaries are not coppied over (as they
can't be executed) but intel-gen4asm.pc is. This pkg-config file is only used
to determine what version of the binary is installed, which confuses the
libva-intel-driver configure script as it thinks that intel-gen4asm is installed
when it isn't.
Resolve this by removing intel-gen4asm.pc from the sysroot.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
As we've retired some BSPs we'll need to bump LAYERVERSION so
that the autobuilder does not fail out on them.
Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
Some of the platforms supported by the intel-corei7-64 BSP have AMT feature
on the platform. Enable it so that it can get utilized with this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
|
|
The xserver-xorg-1.9.3 recipe was needed only for the EMGD graphics driver.
After removing the EMGD support from the meta-intel layer there is no need
to keep this old recipe and it's files.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
As all the EMGD based BSPs have been retired, there is no need for the
proprietary EMGD support in the meta-intel layer.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The fri2 machine has been retired with this commit. This does not affect
the fri2-noemgd machine and it is supported as usual.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The crownbay machine has been retired with this commit. This does not affect
the crownbay-noemgd machine and it is supported as usual.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The emenlow machine has been retired with this commit. This does not affect
the emenlow-noemgd machine and it is supported as usual.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
package_deb doesn't yet handle non-ASCII characters in control files, so remove
a unicode "registered trademark" character.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Use the latest HEADs of the git branches from the linux-yocto
v3.10 kernel repository.
Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com>
Acked-By: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
For the BSPs using the meta-intel.inc file enable the early boot-time kernel
as well as the user space microcode loading support.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
This recipe provides the microcode datafile for Intel Processors.
The recipe provides:
1. microcode.dat file for microcode updating from user space with the
iucode-tool utility.
2. the microcode cpio file which gets bundled with the initrd to support
microcode loading at early boot time.
[ YOCTO #5114 ]
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
iucode_tool is a program to manipulate Intel i686 and X86-64 processor
microcode update collections, and to use the kernel facilities to update
the microcode on Intel system processors.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-Off-By: Nitin A Kamble <nitin.a.kamble@intel.com>
Reviewed-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
To get common intel BSP configurations such as user land microcode loading
support, each Intel BSP configuration needs to include the meta-intel.inc
file. With the exception of few, many of the meta-intel BSP configuration
files already include the meta-intel.inc file. With this commit now, all
the remaining BSPs from the meta-intel layer also include the meta-intel.inc
file.
The Intel platforms BSPs hosted outside of the meta-intel layer, such as
minnow, need to include the meta-intel.inc file to get the common features
from the meta-intel layer.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Reviewed-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
Some modules in the KERNEL_MODULE_AUTOLOAD list were removed when including
the meta-intel layer. It turns out the problem happens due to using the +=
operator together with machine overrides. Using _append_machine fixes this.
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
Acked-By: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
After introducing new machine conf file, bitbake will take
"crystalforest" as the MACHINE name in build/local.conf.
This patch is to update the README with this new build
settings for users who need to build crystalforest images.
Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Machine configuration for both crystalforest-gladden and
crystalforest-server platforms are sharing similiar settings.
This patch is to merge the machine conf by creating one machine
configuration file namely crystalforest.conf.
Signed-off-by: Chan Wei Sern <wei.sern.chan@intel.com>
Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Take a patch from upstream to fix configure when building against GStreamer 1.4.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
The SRCREV lines were removed in:
8b4ab82 intel-common: Remove SRCREVs from linux-yocto-dev
The LINUX_VERSION override should have been removed/commented at the
same time as it is of course directly tied to the SRCREV.
Reported-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Acked-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
Nitin A Kamble
Sreeju Selvaraj
Darren Hart
Ross Burton
Elizabeth Flanagan
Chang Rebecca Swee Fun
Josep Puigdemont
Chan Wei Sern