linux/poky.git/meta-yocto-bsp/conf/machine, branch dunfell-23.0.23

meta-yocto-bsp: Bump to the v5.4 kernel for the non-x86 boards

2020-02-14T13:08:37+00:00

Build and boot test for the beaglebone and edgerouter. (From meta-yocto rev: db4247b8c95ec997fa90226a49df36d7366c469f) Signed-off-by: Kevin Hao Signed-off-by: Richard Purdie

conf/machine: Remove mpc8315e-rdb machine

2020-02-02T10:38:55+00:00

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

genericx86: wic wks do not hardcode loader

2019-12-15T09:08:43+00:00

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 Signed-off-by: Richard Purdie

meta-yocto-bsp: Bump to the v5.2 kernel

2019-09-06T07:25:29+00:00

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 Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

beaglebone: use the default of 256M rather than 512M

2019-08-29T13:05:12+00:00

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 Signed-off-by: Richard Purdie

genericx86-64.conf/genericx86.conf: add QB_SYSTEM_NAME

2019-08-07T15:08:56+00:00

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 Signed-off-by: Richard Purdie

yocto-bsp: runqemu runs beaglebone-yocto

2019-07-19T15:21:16+00:00

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 Signed-off-by: Richard Purdie

beaglebone-yocto: Add missing wic image u-boot deploy dependency

2019-06-01T10:27:42+00:00

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

beaglebone-yocto: Update u-boot config to match u-boot 19.04

2019-04-12T13:05:38+00:00

[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 Acked-by: Denys Dmytriyenko Signed-off-by: Richard Purdie

meta-yocto-bsp: clean up machine config files

2019-04-01T13:58:45+00:00

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 Signed-off-by: Richard Purdie