|author||Brad Bishop <email@example.com>||Thu Nov 08 13:51:11 2018 -0500|
|committer||Brad Bishop <firstname.lastname@example.org>||Mon Nov 19 23:02:52 2018 -0500|
Revert "Cherry-pick systemd mangle-escape patch" This reverts commit 8ef5fd21107625d7480346318cb858759e61ee66. The pull request referenced in the original commit was never merged into systemd. Support for properly using /sys/devices paths as template instances has been added to systemd in the meantime. It probably didn't/doesn't make sense to use device tree paths when launching applications via udev+system (applications to use /sys/devices paths instead). Given all these reasons, drop these two systemd patches. (From meta-phosphor rev: ee22593ddc009cda7aad28bf1311f1a26047fc97) Change-Id: Ic10e0abc8c112e7e6bd62bc346857cf4194dbe50 Signed-off-by: Brad Bishop <email@example.com>
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 sudo dnf groupinstall "C Development Tools and Libraries"
git clone firstname.lastname@example.org: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 in to OpenBMC by opening the docs repository.