BMC/tmp/openbmc.git/meta-evb, branch hardknott

treewide: Remove obsolete image-mklibs class

2021-07-08T22:06:34+00:00

This is apparently not actually working anymore and is removed in the next poky update. Change-Id: Ia1c6a258d124a4a30a14fc42e8e0bba95e64faeb Signed-off-by: William A. Kennington III Signed-off-by: Patrick Williams

meta-evb-nuvoton: add symlinks for machine-conf for setup

2021-04-12T18:51:03+00:00

The 'setup' script looks for machine config files being present to know that the meta-layer contains a valid machine for OpenBMC. The nuvoton EVBs are split between meta-nuvoton for the base support and meta-evb-nuvoton for "EVB on Phosphor" support. Add symlinks for the machine config files from meta-nuvoton into meta-evb-nuvoton so that setup recognizes them as valid machines, but using the phosphor layers. Signed-off-by: Patrick Williams Change-Id: I871432047979f8a7c3d1b836633a5dc74864b6fa

hardknott: yocto release

2021-04-06T13:22:18+00:00

Latest upstream yocto has moved on to the 3.3 hardknott release Signed-off-by: Andrew Geissler Change-Id: Ieae36798d66d21c2c642931f06407d3bb2acf163

openbmc: add meta-security layer

2021-03-22T13:59:05+00:00

This layer provides libseccomp. Signed-off-by: Anton D. Kachalov Change-Id: I84513d56f2ed75fab49043196b98ef8b858e394f

Remove phsophor-gpio-keys as a standalone feature

2021-03-01T04:53:39+00:00

The feature was implemented as an append to the kernel (BSP) layers in meta-phsophor. This created a three way dance between machine layers, BSP and meta-phosphor, when it should have been the kernel layer providing this feature and machines could then opt in. Fixing this means we could remove the KERNEL_DANGLING_FEATURES_WARN_ONLY workaround. As the feature is simply turning on a pair of kernel options without any other impact, we can implement it by adding the options to our defconfigs. In fact, aspeed and hpe kernel configurations enable the two kernel options: $ git grep CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_KEYBOARD_GPIO=y meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_KEYBOARD_GPIO=y $ git grep CONFIG_INPUT_EVDEV meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_INPUT_EVDEV=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_INPUT_EVDEV=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_INPUT_EVDEV=y meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_INPUT_EVDEV=y Other machines that wish to enable this feature should ensure it is added to their BSP's defconfig, or add it to their machine specific defconfig. Change-Id: I0726836319022f96c1d13d4a0cbd73708047302c Signed-off-by: Joel Stanley

meta-evb-aspeed: add symlinks for machine-conf for setup

2021-02-20T01:49:38+00:00

The 'setup' script looks for machine config files being present to know that the meta-layer contains a valid machine for OpenBMC. The aspeed EVBs are split between meta-aspeed for the base support and meta-evb-aspeed for "EVB on Phosphor" support. Add symlinks for the machine config files from meta-aspeed into meta-evb-aspeed so that setup recognizes them as valid machines, but using the phosphor layers. Signed-off-by: Patrick Williams Change-Id: I673756a3d837f61d7338b8fbb356c5234770ffca

meta-evb-ast2600: Add obmc-phosphor-bsp-common.inc

2021-01-13T17:14:54+00:00

Add obmc-phosphor-bsp-common.inc for building OpenBMC image. Tested build with: TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2600/conf . openbmc-env bitbake obmc-phosphor-image (From meta-evb rev: ddba410ebffe7bace588ff6d216c43608f4c5310) Signed-off-by: Troy Lee Change-Id: Ia005eb875f11fec8ffb3aadd5fff4b93a3028f3a Signed-off-by: Andrew Geissler

meta-evb-ast2600: Add an new convenience layer for OpenBMC AST2600 EVB

2021-01-12T22:28:53+00:00

This commit has been verified with AST2600A1 EVB with the image created by the following command: TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2600/conf . openbmc-env bitbake obmc-phosphor-image (From meta-evb rev: 9ec0661731103f703660aa65b5806a126a4f69fb) Signed-off-by: Troy Lee Change-Id: Ie928880ed77ea77cecb33a900092f6ffc5454fb8 Signed-off-by: Andrew Geissler

meta-evb: update Yocto compat for gatesgarth

2020-11-21T19:00:18+00:00

The next release of Yocto is soon and most of the upstream layers have switched support strings for it. Support layer compat for gatesgarth (current) and dunfell (previous). (From meta-evb rev: 4d356d1b1afe5b7050220a649b894b1309973495) Signed-off-by: Patrick Williams Change-Id: Ia4a5889b5cb26171b4578f7a29254c9ad0c527a0 Signed-off-by: Andrew Geissler

meta-evb-ast2500: Add obmc-bsp-common.inc

2020-07-20T22:09:44+00:00

Add obmc-bsp-common.inc so that evb-ast2500 build produces the OpenBMC image. Tested: Verify that the evb-ast2500 builds OK with below commands: TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env bitbake obmc-phosphor-image (From meta-evb rev: 55bf3f1528d5c90c08c7cfa42e3f1783b4d29d35) Signed-off-by: Lei YU Change-Id: I00b22e5fc9a99296028621abb29f40a44e99fc34 Signed-off-by: Andrew Geissler