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>
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>
The second test is designed only to run after the first so we may as
well merge these together into one.
Also, use DEPLOY_DIR_IMAGE rather than constructing paths by hand. Drop
the misleading comment which was likely due to the original code reading
DEPLOY_DIR_IMAGE before setting MACHINE. Only read the variable once
which reduces bitbake -e calls.
Merge the setup/build functions into the main test as there is no other
use of them.
Also ensure the main second test pieces aren't masked out by a missing
file without showing test failures.
(From meta-yocto rev: 1b46e2c1acd2c0cd557740220bbc3ccb77dae127)
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>
Removing things straight from the live sstate directory is prone to issues
since other builds may be relying on the artefact presence.
Also, cleansstate is very slow on the huge sstate that the autobuilder has
on slow NFS drives. This may well be causing long buildtimes in oe-selftest
as the time taken to remove the artefact by be long.
(From meta-yocto rev: 1ed60bfb46569a8b8c29f24187390ba79686486a)
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>
Update the kernel for v4.14 and v4.15 to include a workaround of
the Ethernet malfunction on edgerouter board when building with gcc8.
(From meta-yocto rev: a503919e72fad9556ab0f51a78b92ef3e0075e97)
Signed-off-by: Kevin Hao <kexin.hao@windriver.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>
Bump to the latest stable kernel for 4.14 and 4.15 for edgerouter/beaglebone
to fix gcc8 build issues.
(From meta-yocto rev: c5e07b460cf9477181d2dcde8ea93daeeacc9a2e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bump to the latest stable kernel for 4.12, 4.14 and 4.15.
(From meta-yocto rev: eb025ae398c0042ddc7be75e4ebdeb1fb1344c03)
Signed-off-by: Kevin Hao <kexin.hao@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>
4.4/4.9/4.10 are gone from oe-core master, so we can drop our
bbappends.
4.12 will be removed in the future and 4.14/4.15 added, but all
default versions should be 4.12+ now.
(From meta-yocto rev: fd333864ce66ca32828b3d290ea8aae4f489de9b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bump to the latest stable kernel for 4.4, 4.9 and 4.12.
(From meta-yocto rev: 4e71a79346351f8026a65cfbd68ed0bc8f5eed5c)
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.4, 4.9 and 4.12.
(From meta-yocto rev: f77e7b8c816742fbf5790f11997746958c593f1e)
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>
The yocto-bsp script has been removed, thus there's no need for this test
for the script.
(From meta-yocto rev: 280130bb02b550e882eb203328689b1526fa462c)
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>
After commit edcf39820f the beaglebone
builds fail to mount the boot partition as it is specified in
/etc/fstab with the device node /dev/mmcblkp1. With systemd in
particular this is considered an error and the system drops into
emergency mode.
(From meta-yocto rev: 11dbb98836768b71945817881709c5437d6eec6b)
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Force items into packagegroup-core-tools-profile? I don't think so.
(From meta-yocto rev: df0f331832fad818604d8696700765fb4d3ba072)
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Ross Burton <ross.burton@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.
(From meta-yocto rev: 6909368e9b193c3fc79257982ec609307a5e1ba4)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- Includes fix for CVE-2017-1000251
- Upgrades to Linux 4.9.49
(From meta-yocto rev: b3c4140647104fc764e8f8ffef6bd4bcba9ef4a2)
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- Includes fix for CVE-2017-1000251
- Upgrades to Linux 4.12.12
(From meta-yocto rev: 027a8685481b53fb6b482cdb7f2058536156e789)
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- Includes fix for CVE-2017-1000251
- Upgrades to Linux 4.4.87
(From meta-yocto rev: a1a0b9ef0681ef43ce6648d25e389ddccb1bfe9c)
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The YP Compat v2 standard requres a more specific README structure. Bring
meta-yocto to the required standard and clean up some of the data in the
READMEs whilst in there.
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>
Bump to the latest stable kernel for 4.1, 4,4 and 4.9.
(From meta-yocto rev: 41128b3640e5733e62cb633f7a3ce704dff6a4f2)
Signed-off-by: Kevin Hao <kexin.hao@windriver.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>
Add Test case to verify if EFI bootloader for
systemd boot is correctly build inside of image.
[YOCTO #9903]
(From meta-yocto rev: ce060ee09d00d737007f4a0569e13bebbcde0b3f)
Signed-off-by: Jose Perez Carranza <jose.perez.carranza@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bump to the latest stable kernel for 4.4, 4,9 and 4.10.
(From meta-yocto rev: 294a7d2e1b8d7c54f6ec11804254e7028390c028)
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.1, 4.4, 4,9 and 4.10.
(From meta-yocto rev: acedc2be541a29e33c5d44692aab75432e4d56a3)
Signed-off-by: Kevin Hao <kexin.hao@windriver.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>
- systemd_boot.py: Use the new case class and change decorator for id
- __init__.py: Because isn't needed now
(From meta-yocto rev: 59b2135007d80b3b76ef1256bf5d5aa6076178bc)
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bump to the latest stable kernel for 4.4, 4,9 and 4.10.
(From meta-yocto rev: d45f5894d8f73425b47e3cacbe07d0d5cf36dcd2)
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.4, 4,9 and 4.10.
(From meta-yocto rev: ee6e8f2926a7e2bd02b6b7991ba30ea6e6c9f2f2)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After the change in kernel commit a291b6b3d287 ("ARM: dts:
am335x-boneblack: Add blue-and-red-wiring -property to LCDC node"),
the pixel format we support for 32bit bpp has been changed from
XRGB8888 to XBGR8888. But the fbdev created by modesetting driver use
the XRGB8888 format by default, this causes the X malfunction. There is
no easy way to adjust the pixel format of the fbdev created by the
modesetting driver. So we create a xorg.conf to use the 16bit bpp to
work around this issue.
[YOCTO #11267]
(From meta-yocto rev: 1ef8a9584298a8745a28c0c92fa3ecbf92ffe494)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We have 4.1 (LTSI), 4.4 (LTS), 4.9 (LTS/LTSI) and 4.10 available in
master. 4.8 is no longer required, so we drop the recipe to keep
the version selection under control.
(From meta-yocto rev: 8be1b026d1f56ef18d19fae90cbae45bd7dd97c7)
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>
Since the genericx86*.conf file directly set PREFERRED_VERSION remove it
from here to avoid confusion.
(From meta-yocto rev: 2383d50b084cafdf04f7bd15ea732cd98982625b)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bump to the latest stable kernel for 4.1, 4.4, 4,9 and 4.10. Also set
the default kernel to 4.10.
(From meta-yocto rev: fbb8276e16976b5188efe5a9ee9bdda1ff44d931)
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.1, 4.4, 4,8 and 4.9. Also set
the default kernel to 4.9.
(From meta-yocto rev: 5db023bddd808b01dd7d02c20b3188657c959168)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
