BMC/tmp/openbmc.git/meta-aspeed/conf, branch 2.9.0

meta-aspeed: update Yocto compat for gatesgarth

2020-11-05T21:49:55+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 dunsfell (previous). (From meta-aspeed rev: 3cc1749d59f84cb441fdcf5490cbbecac7227caf) Signed-off-by: Patrick Williams Change-Id: I732a58adeef210b4975560c0d9607da79524dfa1 Signed-off-by: Andrew Geissler

aspeed: enable 'hw-rng' MACHINE_FEATURE

2020-09-13T15:05:45+00:00

Change Iee340ffd294c4f40ba3360acd3f750d886865608 introduced a machine feature which communicates to recipes if a hw random number generator is present. Since the Aspeed chips have a supported RNG, enable this MACHINE_FEATURE. (From meta-aspeed rev: 57caacd62ae6037119be32c608be6ae4e548e639) Signed-off-by: Patrick Williams Change-Id: I275ca0fc1445c782ea6b10e3807e3b339fead53b Signed-off-by: Andrew Geissler

wic: Populate hostfw partition

2020-08-04T00:52:20+00:00

Populate the hostfw partition by specifying the directory to be used as source for the filesystem. This directory is populated by a bbappend to the hostfw recipe. (From meta-aspeed rev: 37f30af4e377a6bc2d3c47ca435798969321f566) Change-Id: Id64e0ac6a5082be2b3ad689a6b323da8eb094e69 Signed-off-by: Adriana Kobylak Signed-off-by: Andrew Geissler

u-boot-aspeed: Generate default env for eMMC

2020-07-17T20:22:05+00:00

Generate a default environment to boot an eMMC based on a txt file. Populate the generated environment image into the eMMC. (From meta-aspeed rev: fdc603c73b2dc8851ce2d1684e9c71a5ce51a5b8) Change-Id: I93944b183b7907202b02854e931593d62603ae77 Signed-off-by: Adriana Kobylak Signed-off-by: Andrew Geissler

aspeed: Build a wic image for the eMMC User Data Area

2020-07-15T15:46:49+00:00

The U-Boot SPL and U-Boot proper would be programmed to the Boot Area Hardware Partitions of the eMMC. The kernel and user space would go into the User Data Area. This commit creates an image that can be programmed into that User Data Area. Layout: --- - ----- -------- -------- ----- ------- ------ -------- ------- |GPT| | env | boot-a | boot-b | fs-a | fs-b | rwfs | hostfw |GPT-sec| --- - ----- -------- -------- ------ ------ ------ -------- ------- ^ 1MB 64MB 64MB 1GB 1GB 7GB 5GB | 0x5000 Primary GPT size (Beginning of image): 512B (Protective MBR) + 512B (Primary Header) + 16KB (Primary Table) First partition (u-boot-env) is 4K-aligned, which puts it at offset 0x5000 Secondary GPT size (End of image): 16KB (Secondary Table) + 512B (Secondary Header) Since the secondary GPT is expected to be at the end of the device, the initramfs can issue a "sgdisk -e /dev/mmcblk0" on first boot to move it to the end. The first partition holds the U-Boot environment. The following two partitions hold a filesystem with the fitImage file. Code update would reflash the full filesystem with the fitImage during an update. U-Boot can then be programmed to look for the kernel in partitions boot-a or boot-b. The remaining is a set of ext4 filesystems for user space, read-write, and host firmware. The size for the host firmware partition is configurable to be able to build an image of different size. The reason is that the tacoma system is has a User Data area just 1GB smaller than rainier. Design doc: https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/28443 Tested: Adding "WKS_HOSTFW_SIZE = "4G"" to the tacoma.conf file created a 14GB wic file: $ ls -lh *wic -rw-r--r-- 1 anoo 532919 15G Jul 14 08:18 obmc-phosphor-image-rainier.wic -rw-r--r-- 1 anoo 532919 14G Jul 14 08:36 obmc-phosphor-image-witherspoon-tacoma.wi $ wic ls obmc-phosphor-image-rainier.wic Num Start End Size Fstype ... 7 9798963200 15167672319 5368709120 ext4 $ wic ls obmc-phosphor-image-witherspoon-tacoma.wic Num Start End Size Fstype ... 7 9798963200 14093930495 4294967296 ext4 (From meta-aspeed rev: b8a647297e3f9fe724f8ee1736bb9da3806d788e) Change-Id: I18b8a15ac8eddb6abfbc7b70429ef45ffc170d9a Signed-off-by: Adriana Kobylak Signed-off-by: Andrew Geissler

dunfell: add support for new layer

2020-04-14T19:25:58+00:00

(From meta-aspeed rev: cc14885f5d983ff0e3f5ad65e17790e3359fa778) Signed-off-by: Andrew Geissler Change-Id: I9a507f1acaf3edad59ddf100f79fb3652788b3f5 Signed-off-by: Andrew Geissler

u-boot-sdk: Use OpenBMC fork

2020-03-17T14:03:07+00:00

This is a fork that is based on ASPEED's 2019.04 SDK fork. The goal is to move to a mainline based tree, but while that work is underway, this allows ast2600 support to move forward. This gains support for NC-SI, and uses kconfig for the default boot command allowing us to drop the patch to aspeed-common.h. Machines will need to indicate which device tree to use. If possible we should look to having a few common device trees, but for now they are machine specific. The AST2600 is configured to use the ast2600a1-evb device tree, which will also work on the a0 variant. (From meta-aspeed rev: 22ccf4648a776c458300c97a6d001a843b2b5c9b) Change-Id: Ib21dc9962761aac3f3148fe4908439b975545e1e Signed-off-by: Joel Stanley Signed-off-by: Andrew Geissler

Move ast2600 to use hard float call convention

2019-12-16T20:59:35+00:00

Before this change, the ast2600 binaries were built with the soft float call convention, which allows them to run on systems that don't have hard float FPUs. Internally, this changes yocto to build like this: CXX="arm-openbmc-linux-gnueabi-g++ \ -march=armv7-a -mfpu=vfpv4-d16 -mfloat-abi=hard ... CPP="arm-openbmc-linux-gnueabi-gcc \ -march=armv7-a -mfpu=vfpv4-d16 -mfloat-abi=hard ... Tested: Builds and boots on ast2600-EVB (From meta-aspeed rev: 53e322518fe6f471663746934e38bf5d8143a501) Change-Id: If8037c66301ca4a3588d10270fe8d2fc610bb195 Signed-off-by: Vernon Mauery Signed-off-by: Brad Bishop

aspeed: Add udev mtd rules to machine recommends

2019-10-15T11:11:59+00:00

These udev rules are useful outside of fw_printenv, which is how we currently include them, so bring them in with the common machine type. (From meta-aspeed rev: 1a7cc4767eb0393bb615ae67e4b388163aa5dc48) Signed-off-by: Joel Stanley Change-Id: I0779fc4c2efd0e18d7729cef4548238e56c39a47 Signed-off-by: Brad Bishop

meta-aspeed: g5: drop redundant tune include

2019-09-26T16:21:52+00:00

Anyone using OE-core after 95823b7eab is using the OE-core provided tune and not ours. Drop our redundant tune file. (From meta-aspeed rev: 5894fc514daad03f70ada285a6b37947e1fb116e) Change-Id: Ice99855d7655f926832943f6944279a0d21de5a7 Signed-off-by: Brad Bishop