commit | 724af737c7b4cb40c10bb22e79427cfc534d1d86 | [log] [tgz] |
---|---|---|
author | Andrew Geissler <openbmcbump-github@yahoo.com> | Fri Jun 12 04:51:35 2020 +0000 |
committer | Andrew Geissler <geissonator@yahoo.com> | Fri Jun 12 07:59:09 2020 -0500 |
tree | 8510b2c5a3569949b3295d38e788dfc1d614e8bb | |
parent | ad314aae9f250e21177185e33e3a3330fbb50335 [diff] |
libmctp: srcrev bump df5f6b9593..5303d9c594 Andrew Jeffery (23): test_astlpc: Fix OBF flag behaviour in emulated KCS status byte test_astlpc: Instantiate a binding for each endpoint test_astlpc: Extract single test case to dedicated function test_astlpc: Add astlpc_test_simple_init test_astlpc: Add network_{init,destroy}() helpers test_astlpc: Introduce astlpc_assert_tx_packet() test_astlpc: Assert message expectations in rx_message() test_astlpc: Clean up debugging in KCS callbacks test_astlpc: Test simple message from BMC to host test_astlpc: Improve readability of test output test_astlpc: Add test for a simple message from host to BMC test_astlpc: Add test initialising the device before the bus owner astlpc: Consolidate direct vs indirect LPC access astlpc: Handle loss of bmc-ready state astlpc: Remove redundant KCS register name enumeration astlpc: Introduce KCS accessors test_astlpc: Add astlpc_test_poll_not_ready() test_astlpc: Add astlpc_test_undefined_command() astlpc: Remove redundant lpc_map_base member from context struct astlpc: Implement version negotiation astlpc: Introduce MTU negotiation astlpc: Make MTU configurable at binding instantiation astlpc: Bump protocol support to v2 (From meta-phosphor rev: 370620b594eb367f90de56a0c0b72b2048c4c6f8) Change-Id: I796b2bd35be8af547b07a951915f14e2fe452d30 Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.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 set up according to your hardware target. There is a special script in the root of this repository that can be used to configure the environment as needed. The script is called setup
and takes the name of your hardware target as an argument.
The script needs to be sourced while in the top directory of the OpenBMC repository clone, and, if run without arguments, will display the list of supported hardware targets, see the following example:
$ . setup Target machine must be specified. Use one of: centriq2400-rep nicole stardragon4800-rep2 f0b olympus swift fp5280g2 olympus-nuvoton tiogapass gsj on5263m5 vesnin hr630 palmetto witherspoon hr855xg2 qemuarm witherspoon-128 lanyang quanta-q71l witherspoon-tacoma mihawk rainier yosemitev2 msn romulus zaius neptune s2600wf
Once you know the target (e.g. romulus), source the setup
script as follows:
. setup romulus
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.
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.
First, please do a search on the internet. There's a good chance your question has already been asked.
For general questions, please use the openbmc tag on Stack Overflow. Please review the discussion on Stack Overflow licensing before posting any code.
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.
Feature List
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: