| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Skylake and Broxton graphics require firmware blobs to run properly.
The firmware must be built into the initramfs since the i915 driver is
built into the kernel and won't have rootfs access on initialization.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
|
| |
This address a boot issue based on using the new bootimg code that
makes a distiction between Live and VM type of image so they can
co-exisit.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
| |
This information is the same across all meta-intel supported MACHINEs,
so we can move it to a shared location.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
|
|
|
|
|
|
| |
This makes us use the new 4.4 kernel by default.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The gma500_gfx driver will match certain devices on which it causes incorrect functionality,
we want to avoid inserting this module, basicallly blacklist it for specific hardware,
but still allow it to work on other hardware by default; usually when we have an already working system,
using udev rules would do the job, but since we are building it, it is impossible to blacklist
a driver when a certain udev rule matches, since rootfs isn't writeable at this point during boot time,
the solution is to use modprobe install, which runs a certain command instead of inserting a matching module
this command needs to insert the module manually afterwards and have a flag --ignore-install
so it doesn't create an infinite loop executing itself everytime it wants to insert the module,
busybox's modprobe doesnt provide this functionality, so a small hack had to be used to avoid
the infite loop instead.
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
| |
This should be SERIAL_CONSOLES with ; setting between baud and device.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By adding the direct path to recipes in common directories we allow
upper layers to further extend the recipes.
Without the patch the extending recipes look like this:
require common/recipes-foo/bar/baz.inc
With this patch the include can be written like in other layers:
require recipes-foo/bar/baz.inc
Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
| |
This causes the build to not use Assembly code which contains invalid
CMOV instructions.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove meta-romley BSP layer from meta-intel master branch
which is targeting for YP 2.0.
A heads-up email was sent to the meta-intel mailing list for
requesting any feedback regarding retirement of these BSP.
Since there is no concern, we assume that it is agreed upon
and thus this patch to retire the BSP.
The "MAINTAINERS file" and "conf/machine/README file" are updated to
reflect removal of the BSP.
We expect intel-corei7-64 machine is continued to be used to support
the platform and dpdk recipe under meta-romley is now supported under
meta-isg/common/recipes-extended/dpdk.
Signed-off-by: WU CHIA CHUAN <chia.chuan.wu@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
|
| |
The padlock code is a subset of x86 hardware acceleration code. It uses
the cmov instruction which is invalid on Quark based hardware, so we
disable this code.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
| |
Adding the ttyPCH0 will allow of the platforms that have the EG20T Hardware
to get both kernel console output and login prompt.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
|
|
|
| |
The intel-core* BSPs supercede these older BSPs therefore it's time
to remove these older platform specific bsps.
Bump LAYERVERSION to 3 to allow the Autobuilder to know that these
BSPs have been removed.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
|
| |
The kernel needs to have the EXTRA_CFLAGS based via a variable as
it does not pick up the CLFAGS from the tune file. Quark based
kernel should not use the lock prefix.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
| |
Use the 4.1 kernel which is now the default in oe-core
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
| |
Use the 4.1 kernel which is now the default in oe-core
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
| |
This new BSP is for the Quark/X1000 and related series that need
the limited no-lock-prefix.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
|
|
| |
add support for the generic NFC stack
Partial fix for [YOCTO #7451].
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
|
|
| |
add support for the generic NFC stack
Partial fix for [YOCTO #7451].
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
|
|
|
|
|
|
| |
No need for a layer of indirection when that layer only has one option.
Previously with EMGD there was a choice, but not anymore.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
|
|
|
|
|
| |
This is handled in oe-core now, remove the redundant code.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
|
|
|
|
|
| |
LSB images prefer to build with LTSI. Update to 3.14, now that 3.10 has
been removed.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
|
|
|
|
|
| |
Now that 3.17 has been removed and linux-yocto-3.19 is available, set
the preferred version to 3.19.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The microcode data file released by Intel has microcode for many Intel
processors, which by default all get installed onto the target image.
In some situations it may desirable to choose microcode for only a
selected processor or processors. This change provides an easier way
to filter and select only the microcode of interest for BSPs from
recipe space.
A new variable, UCODE_FILTER_PARAMETERS, is introduced, which can be
defined to contain parameters to the iucode_tool which will filter the
microcode of interest for the BSP under consideration. More
information on the iucode-tool parameters is available here:
http://manned.org/iucode-tool.
This filtering makes the generated microcode files very
machine-specific, hence making the recipe machine-specific. BSPs using
the common Intel kernel will not be using the filtered microcode, and
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>
Acked-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@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>
Signed-off-by: Tom Zanussi <tom.zanussi@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>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this change, Intel microcode support can be enabled or disabled
for any BSP by controlling the MACHINE_FEATURES variable.
Any BSP from the meta-intel layer can enable Intel microcode loading
support by adding the following line in the machine configuration.
MACHINE_FEATURES += "intel-ucode"
This change keeps the intel-microcode feature disabled by default; it
can however be enabled as an "opt-in" feature via the MACHINE_FEATURES
variable.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
|
|
|
|
|
|
| |
v3.10 is now the latest LTSI kernel. Use it for all the poky-lsb
images, so that it gets validation in the QA cycles.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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 is to enable ASPEED Technology graphic card
that is bundled inside certain Intel customer reference
board.
Signed-off-by: Ong Boon Leong <boon.leong.ong@intel.com>
Acked-By: Nitin A Kamble <nitin.a.kamble@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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Use the latest linux-yocto kernel for the intel-corei7-64 BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
|
|
|
|
| |
Use the latest linux-yocto kernel for the intel-core2-32 BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@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 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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
To be consistent with the renaming in oe-core, use X86 instead of IA32
in the XSERVER_X86* variables.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|