commit | c1f75fbc91c4b22959d65d56e25e9b19c1da214e | [log] [tgz] |
---|---|---|
author | Joel Stanley <joel@jms.id.au> | Mon May 06 16:46:05 2019 +0930 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Tue May 07 08:38:26 2019 -0400 |
tree | fa089d9503f0094be040baa8c2b54653589ebd61 | |
parent | 1917c1b958b144a86e395b6002213d19d394d9af [diff] |
pdbg: Bump to latest version Alistair Popple (4): Revert incorrect version of "libpdbg/p8chip.c: release special wakeups for P8" Revert incorrect version of "libpdbg: use MTMSRD opcode rather than MTMSR" Revert incorrect version of "libpdbg/p8chip.c: ram state setup sequence ..." Revert incorrect version of "libpdbg/p8chip.c: Emulate sreset using ramming..." Amitay Isaacs (9): adu: Convert __adu_{get, put}mem_blocksize to adu functions adu: Add read/write methods for adu target adu: Set default blocksize for adu adu: Add new api for memory read/write main: Use new api to read/write memory path: Match targets with dn name correctly tests: Add a test for dn name match path: Avoid a match for nested nodes of the same class tests: Fix the core address calculation Artem Senichev (1): api: Fix API interface for external usage Nicholas Piggin (11): libpdbg: Fix CHECK_ERR macro to evaluate once in error case libpdbg/p8chip.c: read status from correct target libpdbg/p8chip.c: Only write the SP_STOP bit once libpdbg/p8chip.c: release special wakeups for P8 libpdbg: use MTMSRD opcode rather than MTMSR libpdbg/p8chip.c: ram state setup sequence match workbook libpdbg/p8chip.c: Emulate sreset using ramming for active threads libpdbg/p8chip.c: release special wakeups for P8 libpdbg: use MTMSRD opcode rather than MTMSR libpdbg/p8chip.c: ram state setup sequence match workbook libpdbg/p8chip.c: Emulate sreset using ramming for active threads (From meta-openpower rev: 35f5adc0a390d2d398cdcb949b613eeb3d0d25d9) Change-Id: Ia36ba13d8ccf75994f844223bc65d7d8e5798b93 Signed-off-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.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 perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum sudo dnf groupinstall "C Development Tools and Libraries"
git clone git@github.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
Machine | TEMPLATECONF |
---|---|
Palmetto | meta-ibm/meta-palmetto/conf |
Zaius | meta-ingrasys/meta-zaius/conf |
Witherspoon | meta-ibm/meta-witherspoon/conf |
Romulus | meta-ibm/meta-romulus/conf |
As an example target Palmetto
export TEMPLATECONF=meta-ibm/meta-palmetto/conf
. 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.
Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.
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.
Feature List
Features In Progress
Features Requested but need help
Dive deeper into OpenBMC by opening the docs repository.