Appending IMAGE_INSTALL with the kernel and device tree is a bad idea
because it will bring these packages to every images, like a container
image or sysroot image to pivot to, where the kernel artifacts are
not wanted.
Instead use the MACHINE_ESSENTIAL_EXTRA_RDEPENDS which results
in having the kernel artifacts where they should be, part of
packagegroup-core-boot.
(From meta-yocto rev: d4cbe0e43393ec70e98caf006372b5311597d377)
Signed-off-by: Vivien Didelot <vdidelot@pbsc.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If BBLAYERS contains a layer providing a package for
virtual/bootloader, building for the beaglebone-yocto machine will
fail. Setting u-boot as the preferred provider for virtual/bootloader
ensures u-boot is choosen and the build succeeds.
(From meta-yocto rev: 2ffbaf54f4d88ba251d282c90755ea964d224ba6)
Signed-off-by: Vivien Didelot <vdidelot@pbsc.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
5.14 has been removed from core, so we change our default version
to the 5.15 LTS kernel.
(From meta-yocto rev: a0241305e3785930f806529fd1b1d1a3831203d0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Introduce the bbappend for v5.14 and also set the default kernel to
v5.14 for all the boards.
(From meta-yocto rev: bed70a64b5b772fd71a7ff88a9f3719082e9398c)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Build and boot test for all the boards.
(From meta-yocto rev: b296bf6b0cadcff7c9000a3f4a3ca162785b9a33)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This marks the layers as compatible with honister now they use the new override
syntax.
(From meta-yocto rev: ea637ebd5a79e5d023bbf347d633568bcb7506a2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This converts the two layers to the new override syntax. This was done using
<oe-core>/scripts/contrib/convert-overrides.py <this-layer>
with no manual fixes.
(From meta-yocto rev: 387eab70f343966267c2a68746aea1bbb8525191)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The beaglebone-yocto machine currently hardcodes "u-boot" as a
dependency for the image and the wic format, and this prevents one
from choosing a different bootloader via:
PREFERRED_PROVIDER_virtual/bootloader = "non-u-boot-bootloader"
Depending on "virtual/bootloader" instead of "u-boot" fixes this.
Cc: Denys Dmytriyenko <denis@denix.org>
(From meta-yocto rev: 4c4c8327645457a5d68762ff64b64d4b5845cd20)
Signed-off-by: Vivien Didelot <vdidelot@pbsc.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Build and boot for all these machines and also explicitly set the
preferred kernel version for the x86 machines so that we can override
the default setting in oe-core.
(From meta-yocto rev: a93344439e01e8aba4ba15d3123ce31b4500add1)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This reverts commit da27ca50eebf80463cb8d7b85f3b705254823413.
We usually select the preferred kernel version in the machine conf. This
is also what recommend in the BSP Developer's Guide. The beaglebone-yocto
and edgerouter have already done this in their machine conf files.
Resetting it in the layer conf is redundant. So revert this patch first,
we will also explicitly select the kernel version for the x86 machines
in the following patch.
(From meta-yocto rev: 825645ff2b663ae5c5845e8ae4679f6e346eac8c)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We already have the following variables defined above IMAGE_BOOT_FILES:
SPL_BINARY = MLO
KERNEL_IMAGETYPE = zImage
KERNEL_DEVICETREE = am335x-bone.dtb am335x-boneblack.dtb am335x-bonegreen.dtb
So use them instead of repeating their values.
(From meta-yocto rev: be07cc4f4e729905065ac6fbf1d46ebfdd79cf8f)
Signed-off-by: Vivien Didelot <vdidelot@pbsc.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When we are bumping the default kernel version for the qemu*
reference boards, but before the h/w reference boards have been
updated, we need to explicitly set the default kernel version
for those boards. Otherwise, we'll end up with warnings about
preferred versions of kernel modules not being available
(From meta-yocto rev: da27ca50eebf80463cb8d7b85f3b705254823413)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Boot test for all the supported boards. There is a kernel config
check warning for beaglebone-yocto, the fix [1] has been sent to
kernel-meta for merging.
[1] https://lists.yoctoproject.org/g/linux-yocto/message/8992
(From meta-yocto rev: ccc825335f257ca2259440c561eea02538edd762)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Build and boot test for the beaglebone and edgerouter.
(From meta-yocto rev: db4247b8c95ec997fa90226a49df36d7366c469f)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This hardware is old/obsolete and unobtainable. Its proving hard to support
with nobody fixing bugs or helping keep the platform running/up to date.
Whilst there is value in real hardware testing, this platform ist just too
old and obsolete to support. This does leave a gap for the power architecture
but at this point there is nobody willing to step up to cover it.
The TSC did discuss and agree support for this platform should be removed.
It calls into question the support/testing of the architecture by Yocto
Project which is being discussed by the TSC and governing board.
(From meta-yocto rev: aa691d49ceb6700eb1881b789fe34f8369bcb0ef)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
replace .wks with .wks.in and refer loader to EFI_PROVIDER
to enable different bootloader.
soft assign default EFI_PROVIDER "grub-efi" for genericx86.
(From meta-yocto rev: 11ecd2febed95e923c8cc68e2c438cd846a88d02)
Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Boot test for all the supported boards. Also drop the v5.0 bbappend
since we no plan to support it anymore. There are some
kernel_configcheck warning when building some boards, the patches [1]
for them have been sent to kernel-meta for merging.
[1] https://lists.yoctoproject.org/pipermail/linux-yocto/2019-August/007908.html
(From meta-yocto rev: c6e974e12c1d7fe0d155b6cf1bc0c1f4a6ee69d0)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is done for the sake of using the same default
everywhere; see here for details:
http://lists.openembedded.org/pipermail/openembedded-core/2019-August/285900.html
(From meta-yocto rev: f4ba98ed3c866ec3db90404f894d5aeaa5d79dfd)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
QB_SYSTEM_NAME set in qemuboot-x86.inc will be removed,
so set QB_SYSTEM_NAME in these two configuration files.
(From meta-yocto rev: 6748c925817da0e7ae2a84d1214e3595515962b5)
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Append the necessary QB_ flags to the MACHINE configuration of
beaglebone-yocto. Using Qemu with "-machine virt" simplifies things
greatly because for this machine the dtb is compiled into qemu. Since
the beaglebone-yocto kernel config also supports this cpu architecture,
it just works. However, u-boot is not involved and the virt machine is
not 100% equal to a am335x SoC.
A MACHINE configuration suitable for Qemu as well as for the real
hardware allows to provide just one eSDK where both runqemu and devtool
build-image work. Otherwise a qemuarm and a beaglebord-yocto MACHINE
eSDK would be required to support development in Qemu as well as on real
hardware.
(From meta-yocto rev: 48bf40749cc63e8e951c76abbe65b1b9620b2481)
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The wic image built for beaglebone-yocto needs the u-boot deployed artefacts but
there is no direct dependency. Usually this happens to work but if the u-boot
build fails, the image built with -k exposes this race.
Add the missing dependnecy.
[YOCTO #13280]
(From meta-yocto rev: d0abe4a39ad261bcd4993ebd3340c2160870959a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[YOCTO #13145]
This was announced at 2019.01:
https://www.mail-archive.com/u-boot@lists.denx.de/msg305424.html
Basically, am335x_boneblack is just a special subset of am335x_evm config,
created and owned by BeagleBoard.org community. Since it was not migrated to
use CONFIG_BLK in time for 2019.04 release.
(From meta-yocto rev: 26f38a6de56a2d3bb1ef9b06d6b49537192f9447)
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Acked-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Beautify the machine config files by making the names and descriptions
more uniform and verbose
(From meta-yocto rev: 159a8c9080af125c657558b4789f4aa8410e4fa2)
Signed-off-by: Jon Mason <jdmason@kudzu.us>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
it is possible to use the beagleboneblack with the 8250 serial
driver or with the deprecated omap serial driver.
Unfortunately serial console get different names (ttyS0 with
8250 driver and ttyO0 with omap driver)
So set SERIAL_CONSOLES to
SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyO0"
(intentionally with "?=" so it is overwriteable)
and activate
SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
with that on the first boot the correct value is picked up
automatically.
(From meta-yocto rev: ffd224382af6fe1f5eeae32d7b28cc975acdde05)
Signed-off-by: Heiko Schocher <hs@denx.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Asus EEEpc hardware hasn't been produced for a long time;
upstream repo is now gone.
(From meta-yocto rev: 76cd3a475ebce4ae26fc3aae0f2b43628926f7b0)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bump the kernel to v4.18 for all the boards in meta-yocto-bsp layer.
(From meta-yocto rev: 1e672581cc3fc695570f1ae9f951efbe4b05733a)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
SERIAL_CONSOLE was already deprecated in 2013, yet still some
machine configuration files were using it. This patch replaces
it with SERIAL_CONSOLES, which is the successor.
The default value in systemd-serialgetty.bb can also be safely
transitioned from SERIAL_CONSOLE to SERIAL_CONSOLES, as this
recipe already uses SERIAL_CONSOLES within do_install().
The documentation seems to be already up do date.
beaglebone-yocto.conf in the bsp-guide already uses
SERIAL_CONSOLES. The ref-manual redirects from SERIAL_CONSOLE
to SERIAL_CONSOLES.
[YOCTO #12653]
(From meta-yocto rev: a0c5332aefe75cf314e78284f578b17c51b8ab27)
Signed-off-by: Maciej Pijanowski <maciej.pijanowski@3mdeb.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now that kernel-modules are not included in x86-base.inc because of
changes done for YOCTO #12384, add them to RRECOMMENDS explicitly for
genericx86*.
(From meta-yocto rev: 0b78254b373c23f2c1a2bf7db0108a350266ab85)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* fix the issue with newer kernel-devicetree.bbclass as reported by RP in
http://lists.openembedded.org/pipermail/openembedded-core/2018-July/152594.html
with changes from
http://lists.openembedded.org/pipermail/openembedded-core/2018-July/152560.html
the bbclass no longer creates the dtb files prefixed with
KERNEL_IMAGETYPE_FOR_MAKE:
deploy/images/mpc8315e-rdb/uImage-mpc8315erdb.dtb
use the version less symlink:
-rw-r--r-- 2 bitbake bitbake 9.3K Jul 9 13:30 deploy/images/mpc8315e-rdb/mpc8315erdb--4.15.18+git0+45c256a5ca_0b32edc46d-r0.2-mpc8315e-rdb-20180709125726.dtb
lrwxrwxrwx 2 bitbake bitbake 84 Jul 9 13:30 deploy/images/mpc8315e-rdb/mpc8315erdb.dtb -> mpc8315erdb--4.15.18+git0+45c256a5ca_0b32edc46d-r0.2-mpc8315e-rdb-20180709125726.dtb
lrwxrwxrwx 2 bitbake bitbake 84 Jul 9 13:30 deploy/images/mpc8315e-rdb/mpc8315erdb-mpc8315e-rdb.dtb -> mpc8315erdb--4.15.18+git0+45c256a5ca_0b32edc46d-r0.2-mpc8315e-rdb-20180709125726.dtb
(From meta-yocto rev: 1f8b8d266a3e8dbe7c447d074446c9f27526991e)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently mpc8315e-rdb.conf comes after local.conf during parsing. We should
give local.conf a chance to overwrite the kernel provider assignment, like
other BSPs.
(From meta-yocto rev: c5c70afb0306d96ae63d7a67d658524ed6d91e88)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These spaces aren't needed and are confusing people. Remove them.
(From meta-yocto rev: 36d20206b73d2efbf72353030b786483eb8749b6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Also set the default kernel of these BSPs to v4.15.
(From meta-yocto rev: 4c35cdf84b24104c341b986dd3e04323aca894c4)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The beaglebone BSP provided in this layer is a reference implementation
usingonly mainline components available in core Yocto Project layers,
whereas Texas Instruments maintain a full-featured BSP in the meta-ti
layer.
Rename the reference machine to prevent namespace collisions with the
version maintained by the SoC vendor.
[YOCTO #12326]
(From meta-yocto rev: e32882938eca7f50548deab84dab78b4aef31b95)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As 4.4 is the lowest kernel version in oe-core, we can add the dtb for the
beaglebon green to the list of dtb's to generate.
(From meta-yocto rev: dc77383ca352431cba7cb779899220db4eaa0cba)
Signed-off-by: Anders Darander <anders@chargestorm.se>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bump to the latest stable kernel for 4.4, 4.9, 4.10 and 4.12. Also
set the default kernel to 4.12.
(From meta-yocto rev: 4e0ada1132db54a1723e3a603fa99b0b8ddf29eb)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The genericx86 and genericx86-64 machine confs do not need to set the
PREFERRED_PROVIDER_virtual/kernel as they will use the one set by the
distribution. If there needed to be a different version for one of these
machines in the future, we could add it in to the machine.conf.
(From meta-yocto rev: 89dd8159fc83f54d7fe234b619a28f5d97519156)
Signed-off-by: brian avery <brian.avery@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In order to match the other meta-yocto-bsp MACHINE definitions add wic.bmap
to the produced images.
(From meta-yocto rev: 43c3e1194bf789d16c3e9bd41b8aae0098362677)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This means mismatched layers are more clearly identified to the user in
cases where compatibility has not been tested.
(From meta-yocto rev: ca35ea46708e0514e4d5a20950880be0bf1d4147)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In machine configuration files, there is no need to use OVERRIDES that
match the precise machine being defined, so remove them for clarity
and consistency from these lines in those respective files:
PREFERRED_VERSION_linux-yocto_genericx86-64 ?= "4.10%"
PREFERRED_VERSION_linux-yocto_genericx86 ?= "4.10%"
UBOOT_MACHINE_mpc8315e-rdb = "MPC8315ERDB_config"
(From meta-yocto rev: 035d4e7763171068d2b4df0622b6cc0fc1cf4b32)
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
