|author||Brad Bishop <firstname.lastname@example.org>||Thu Sep 12 13:41:52 2019 -0400|
|committer||Brad Bishop <email@example.com>||Thu Sep 19 16:23:29 2019 +0000|
meta-aspeed: g6: Adjust fit address 5b6780e981 changed the u-boot+env size and thus the same fit image address (512KiB) can be used on g6 as on the other aspeed SoCs. Refresh the initial u-boot patch rather than a new one because the original has not yet been accepted upstream. (From meta-aspeed rev: 6aa4aaf66f96acaf84a6c434ddfb3e142c087bf4) Change-Id: I5bcd6468f1578f7f820e3eeeec23d5b3756dca60 Signed-off-by: Brad Bishop <firstname.lastname@example.org>
The OpenBMC project can be described as a Linux distribution for embedded devices that have a BMC; typically, but not limited to, things like servers, top of rack switches or RAID appliances. The OpenBMC stack uses technologies such as Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your server platform.
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake \ rpcgen perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum sudo dnf groupinstall "C Development Tools and Libraries"
git clone email@example.com:openbmc/openbmc.git cd openbmc
Any build requires an environment variable known as
TEMPLATECONF to be set to a hardware target. You can see all of the known targets with
find meta-* -name local.conf.sample. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet
As an example target Palmetto
. openbmc-env bitbake obmc-phosphor-image
Additional details can be found in the docs repository.
Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile
make check directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.
Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.
Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.
Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.
Features In Progress
Features Requested but need help
Dive deeper into OpenBMC by opening the docs repository.