|author||Joseph Liu <email@example.com>||Mon Nov 11 18:58:52 2019 +0800|
|committer||Andrew Geissler <firstname.lastname@example.org>||Fri Apr 17 12:34:47 2020 -0500|
meta-nuvoton: linux: enable hash api for systemd Kernel crypto/hash API CONFIG_CRYPTO_HMAC CONFIG_CRYPTO_SHA256 CONFIG_CRYPTO_USER_API_HASH The requirement can be found at https://github.com/systemd/systemd/blob/master/README This API is necessary for the UUID feature that you can find the implementation in the bmcweb. https://github.com/openbmc/bmcweb/blob/master/redfish-core/include/utils/systemd_utils.hpp (From meta-nuvoton rev: 0409fb71e479cef29777fee90f4285fd34f69eb6) Signed-off-by: Joseph Liu <email@example.com> Change-Id: I85bc34196571e04bdcdc0c12707930fdfc16530e Signed-off-by: Andrew Geissler <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 Romulus
. openbmc-env bitbake obmc-phosphor-image
Additional details can be found in the docs repository.
The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here
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.
First, please do a search on the internet. There's a good chance your question has already been asked.
For technical discussions, please see contact info below for IRC and mailing list information. Please don't file an issue to ask a question. You'll get faster results by using the mailing list or IRC.
Features In Progress
Features Requested but need help
Dive deeper into OpenBMC by opening the docs repository.
The Technical Steering Committee (TSC) guides the project. Members are: