The 5.2 recipes have been dropped from oe-core, so we drop the
5.2 bbappends to match.
(From meta-yocto rev: 1da347d7c9b50974648bf216b766bcb958159fa0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[
Author: Changbin Du <changbin.du@gmail.com>
Date: Tue Jan 28 23:29:38 2020 +0800
perf: Make perf able to build with latest libbfd
libbfd has changed the bfd_section_* macros to inline functions
bfd_section_<field> since 2019-09-18. See below two commits:
o http://www.sourceware.org/ml/gdb-cvs/2019-09/msg00064.html
o https://www.sourceware.org/ml/gdb-cvs/2019-09/msg00072.html
This fix make perf able to build with both old and new libbfd.
Signed-off-by: Changbin Du <changbin.du@gmail.com>
Acked-by: Jiri Olsa <jolsa@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: http://lore.kernel.org/lkml/20200128152938.31413-1-changbin.du@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]
(From meta-yocto rev: 207feb95be473359785e67df340e07942a376c54)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This avoids warnings due to kernel version mismatches
(From meta-yocto rev: 4d8122bca9e5a8788521537610411fe59b1ba8a6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the SRCREVs for the h/w references to v5.4.20, which includes
the binutils fix for perf.
(From meta-yocto rev: 9fcac872e5f2cc05409cb06640c0f625bea6e8ba)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
5.4 is the new LTS kernel, so we drop the 4.19 bbappens as the 4.19
kernel will be removed.
(From meta-yocto rev: 36e7756b89a2adb0df470e862a71fbfda98a8682)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.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>
If mtools isn't present on the underlying system this test would fail.
Ensure wic-tools is available in a similar way to other wic selftests
in OE-Core.
(From meta-yocto rev: 5d48d41a3f93ca0e7085ce3c0f646b1d0c8d52d1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
effort to remove live for x86 from default image
see https://bugzilla.yoctoproject.org/show_bug.cgi?id=11291
reduce dependency on hddimg, change the test to based on wic image.
(From meta-yocto rev: 8cce1493f625664c21c156a36d9c9fb6d4dd4b1f)
Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com>
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>
Updating the reference BSP SRCREVs and versions to 5.2.17 to match
the latest for qemu* and to pickup some reference board specific
patches.
(From meta-yocto rev: fcc920580380a2b57b5b8e1649b4ad94bd3d15b7)
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. 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>
Boot test for all these boards.
(From meta-yocto rev: 3407018bc9d4e4660bba1b1a153815df4640de7e)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Matching changes in OE-Core. drop OETestID.
(From meta-yocto rev: 58e50924e5fd0b3dae5ac3413c40f0f16a857b72)
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>
Boot test for all these boards.
(From meta-yocto rev: 135958cd17531fd5eeb5e1eff3e673c435def1b2)
Signed-off-by: Kevin Hao <kexin.hao@windriver.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>
Boot test for all the boards.
(From meta-yocto rev: 8abaf3bfbbb6c0dd51e35ef4c3f6e8455b9109d4)
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>
Although the hardware reference boards are not using the 5.x
kernel yet, we generate a baseline bbappend for future work.
(From meta-yocto rev: c3b875dcc01de567ba0320bcba5922000cfb2e2f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the commit ec6d61cbdd ("mesa: enable native and nativesdk
variants"), the gallium is enabled for the mesa. Since we use the
modesetting driver for the Xorg on the beagleboard and the glamor
acceleration method is enabled by the modesetting driver, the gallium
DRI driver will be used after this commit. But the gallium DRI driver
only support 32bpp and we choose to use 16bpp on beaglebone in commit
e7434c17b4 ("meta-yocto-bsp: workaround the X malfunction on
beaglebone"), the mismatch between them causes the malfunction of the
Xorg. I have hacked the kernel to enable the 32bpp for the beagllebone,
but it has the following issues:
1. The color is abnormal.
2. The Xorg hang occasionally.
3. The performance of using glamor acceleration based on gallium is
pretty bad.
So I choose to disable the glamor on this board.
(From meta-yocto rev: b7a995856c58b507a521a55dcf94bee75804e81c)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bump to the latest stable kernel for 4.18.
(From meta-yocto rev: 317dab2926a6f6a59f19fb3c4453a313af041b60)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
And bump the kernel version to v4.19.8.
(From meta-yocto rev: 19f5a52f102f61dadb55a19f4643ba7da5e678c8)
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
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>
Bump to the latest stable kernel for 4.14 and 4.18.
(From meta-yocto rev: f7d36129adfeb0d0d5fe26675e2668c49573a32d)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
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>
4.18 is replacing 4.12 as the latest kernel in the upcoming
release, so we drop this dangling bbappend.
(From meta-yocto rev: 6686fbad03d8de5d29d58aae149e253474336d5f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4.18 is replacing 4.15 as the latest kernel in the upcoming
release, so we drop this dangling bbappend.
(From meta-yocto rev: 14e89c34cc0cb9e74075cd5a86500426701b1c8d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
