The COMPATIBLE_MACHINE entry for dpdk recipes is set to 'null'. This
will prevent arbitrary machines from trying to use the dpdk functionality.
A compatible MACHINE must define itself as such for the dpdk recipes. Also
the BSP aware target machine was similarly moved to the BSP. Embedding BSP
specific knowledge into the recipe will cause the recipe to slowly get out
of date.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
meta-dpdk / meta-qat:
* Move content from meta-intel/common
* Create new basic README/LICENSE files from meta-intel
* Create new layer.conf files
* Fill out the maintainers files
meta-intel:
* update the maintainers files
* bump the meta-intel layer version
* add layer recommend
No other content changes made in this commit.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
A machine configuration file wasn't the correct place to put this in the
first place. It should be in a bbappend, which we now have.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Since we want to support the out of tree modules for wifi and ethernet
we need to also have them as common for all machines in the common arch.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This lets the uefi-comboapp and new kickstart template work well
together out of the box.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
The recent patch from Todor to split the RMC recipe into lib and efi app
allows us to revert this override.
This reverts commit a0ca03a32b.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Since the existing rmc library does not build correctly for x32
target disable it with an ARCH based OVERRIDE.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This means mismatched layers are more clearly identified to the user in
cases where compatibility has not been tested.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
bb.utils.contains checks if ALL items are in the variable, and since we
check for systemd-boot or rmc-boot, it would always be false, assigning
mkefidisk as the WKS_FILE in all cases. bb.utils.contains_any checks if
one or more items are in the variable, so use that instead.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
If someone changes their EFI_PROVIDER to grub-efi, we shouldn't be
building a systemd-boot based wic image. Use bb.utils.contains to
be default to mkefidisk.wks if we aren't using a systemd-boot based
EFI_PROVIDER.
mkefidisk.wks is the same as systemd-bootdisk.wks, except it uses grub
and sets rootwait on the kernel command line, so its nearly equivalent.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This was initially added as a stopgap, as OE-core's systemd-bootdisk.wks
was using a static device node name rather than device UUID as the root
target. Since OE-core's systemd-bootdisk has caught up, we don't need
this. OE-core's systemd-bootdisk also includes console=ttyS0, which is
common on many platforms and we were missing.
Also change the default WKS_FILE to be OE-core's systemd-bootdisk on
appropriate MACHINEs.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Adding to KERNEL_FEATURES causes the kernel tools to try to add the
feature to all kernels, even custom kernels not using the
yocto-kernel-cache. By moving it to KERNEL_FEATURES_INTEL_COMMON, it
will only affect the kernels the layer supplies.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
We added -rt to available kernel, and will likely have -tiny and -dev
in the future, so add them now also.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This lets us use ovmf firmware with runqemu without building ovmf
manually beforehand.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
linux-intel does not provide a 4.1 kernel, which is needed for -lsb
images since they use the current LTSI kernel.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Moves common MACHINE_EXTRA_RRECOMMENDS to a common include file and
add thermald to MACHINE_EXTRA_RRECOMMENDS.
Signed-off-by: Jussi Laako <jussi.laako@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
The latest OE's runqemu script by default uses the following
SLIRP options
-netdev user,id=net0,hostfwd=tcp::2222-:22,hostfwd=tcp::2323-:23
which are suitable for meta-intel too. And what is more important
they don't follow the deprecated syntax currently present in the
option values overriden by meta-intel.
The patch drops the meta-intel specific overrides.
Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Enable the linux-intel production kernel for meta-intel by default for 4.9,
this will enable using the Intel production kernel.
This is a well tested 4.9 tree that will start to include additional
support for the Apollolake and Joule hardware.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Although the machines definitions in meta-intel are meant to target
real hardware, begin able to start the resulting images under qemu is
nevertheless useful for testing.
Doing that via runqemu depends on a per-image runqemu.conf that
describes how to run qemu for the image. Ineriting qemuboot.bbclass in
image recipes with QB_ variables set for the current architecture via
overrides creates that file.
The new qemuboot-intel.inc was copied from OE-core's qemuboot-x86.inc
and adapted to the three common machines in meta-intel:
$ diff ../openembedded-core/meta/conf/machine/include/qemuboot-x86.inc conf/machine/include/qemuboot-intel.inc
3,5c3,5
< QB_SYSTEM_NAME_x86 = "qemu-system-i386"
< QB_CPU_x86 = "-cpu qemu32"
< QB_CPU_KVM_x86 = "-cpu kvm32"
---
> QB_SYSTEM_NAME_intel-core2-32 = "qemu-system-i386"
> QB_CPU_intel-core2-32 = "-cpu coreduo"
> QB_CPU_KVM_intel-core2-32 = "-cpu kvm32"
7,9c7,13
< QB_SYSTEM_NAME_x86-64 = "qemu-system-x86_64"
< QB_CPU_x86-64 = "-cpu core2duo"
< QB_CPU_KVM_x86-64 = "-cpu kvm64"
---
> QB_SYSTEM_NAME_intel-corei7-64 = "qemu-system-x86_64"
> QB_CPU_intel-corei7-64 = "-cpu Nehalem"
> QB_CPU_KVM_intel-corei7-64 = "-cpu kvm64"
>
> QB_SYSTEM_NAME_intel-quark = "qemu-system-i386"
> QB_CPU_intel-quark = "-cpu coreduo"
> QB_CPU_KVM_intel-quark = "-cpu kvm32"
For performance reasons, runqemu uses virtio for the boot disk. The
kernel therefore must have the necessary drivers enabled. This may
also be useful when running a meta-intel machine image on other
virtual platforms and therefore the default kernel configuration gets
changed to enable virtio.
However, OE-core's qemu.inc also enables various other tweaks for
running under qemu, like deriving the wired Ethernet address from the
kernel boot parameters. This is probably less desirable for a
meta-intel machine and thus not enabled in the new qemu-intel.inc. The
downside is that the resulting images then come up without assigned IP
address when used under qemu. Distros which want that feature can
still add it to their images by copying settings from OE-core's
qemu.inc.
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
EFI_PROVIDER is set in meta-intel.inc for all machines
so the one set in intel-quark.conf has no effect and can be
removed.
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
do_image_wic (in image_types.bbclass) deals with the task dependency
to do_bootimg if live images are built.
It's redundant to set do_bootimg as a recrdeptask in the machine
configurations so remove it.
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
intel-* machines default to an EFI bootloader which runs from an EFI
system partition (ESP). Also, the ESP needs to be vfat formatted.
Make sure the dosfs/mtools used by wic and its plugins that deal with
vfat are built and available (without depending on do_bootimg) when
wic images are being created.
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
libva and gstreamer-vaapi are now part of oe-core, so remove them.
The package names were changed to reflect the naming scheme, so update the
machine configurations to follow.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
RMC was previously configured to work only with the systemd-boot EFI
bootloader. With this commit we can specify alternative bootloaders by
setting the RMC_BOOTLOADER variable in local.conf. If RMC_BOOTLOADER is
not set systemd-boot will be used by default.
Signed-off-by: Todor Minchev <todor.minchev@linux.intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Include support for ASPEED Technology graphics card driver to
intel-corei7-64 and intel-core2-32. So that intel common BSP can
support platforms like MohonPeak (Intel Atom Processor C2000 Product
Family) which using this graphics card.
Signed-off-by: Rahul Kumar Gupta <rahul.kumarxx.gupta@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Some of Intel boards are using ttyS1 also. So ttyS1 is added to
SERIAL_CONSOLES inorder to provide login prompts on the console.
Signed-off-by: Rahul Kumar Gupta <rahul.kumarxx.gupta@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Overriding systemd-bootdisk.wks unconditionally was against Yocto
Project's compatibility requirements, so our version needed to be
renamed.
Change our conf files to use the renamed version.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This allows to have one override mechansim for meta-intel instead of having
multiple machine overrides.
This replaces using rmc in DISTRO_FEATURES which was a bad idea to set in
layer.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Some Intel boards use ttyS0 and others use ttyS2, include both serial
ports inorder to provide login prompts on the console.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
We cannot override the current EFI bootloader selection with
another "EFI_PROVIDER=..." in a local.conf in a build/conf
directory when it is specified by "=" syntax in the current
conf file for quark.
Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This is to get rid of "install" option when booting quark with
an image in hddimg format. EFI installer doesn't work on quark
at this point.
Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This enables the Runtime Machine Configuration feature, which
allows use to support multiple machines that have different
kernel commandline option as well as different startup requirements
to work from the base MACHINE configuration.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This adds WIC Image support to the Quark Intel BSPs, these
are all designed to be copied to MicroSD Cards via dd. This will create
an efi boot partition along with a user space partition.
It is not currently setup to have an install target, it only has a live boot
target.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This adds WIC Image support to the core2 and corei7 Intel BSPs, these
are all designed to be copied to USB sticks via dd. This will create
an efi boot partition along with a user space partition.
It is not currently setup to have an install target, it only has a live boot
target.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This makes it easier for others inheriting meta-intel to use their own
kernel.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
RMC Feature is based on RMC project, systemd-boot, EFI installer
to enable a single generic image, built for multiple platforms,
automatically applies customization and quirks specific to a type
of boards at runtime.
In another word, you will see a single image behaves differently
and intelligently according to the type of board it is running on.
To Enable this feature: add the two lines in conf file:
DISTRO_FEATURES_append = " rmc"
EFI_PROVIDER = "rmc-systemd-boot"
Based on Saul Wold's initial work on a feature switch, RMC patches
in systemd-boot, installer and gnu-efi aren't built unless the
feature is enabled.
For a supported board, this feature can :
() show and boot with board-specific boot entries in boot menu
in live-boot and post-installation.
() apply a kernel cmdline fragment to the end of cmdline to boot
Linux kernel. This is effective for any boot entry user chooses in
boot menu.
() create directory and deploy files only for the type of the
running board to target's file systems. What left on target after
installation is just same as the result from installing a conventional
image customized for a single type of hardware.
To add support of new boards, a new variable RMC_BOARD_DATA_DIRS
is the interface to developers. How-to information will be provided
with examples in following patches.
Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com>
Reviewed-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
The systemd-boot is the old gummiboot merged into systemd project.
We have enabled systemd-boot as a standalone EFI bootloader in OE,
also with updated wic plugin to support specifying "systemd-boot"
as bootloader in wks files.
Assuming these are good enough to replace gummiboot for quark,
this change does it.
Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
The linux-yocto-tiny metadata assumes the common PACKAGE_ARCH but
without this is actually machine-specific and broken.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
