| commit | d83b524fcf1bf3a0fa2851591e0abf845fbdeaa3 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Nov 05 08:50:44 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 10 18:11:44 2021 +0000 |
| tree | d4ca392ee69e6c8195e2906f916536f8a02a24f4 | |
| parent | e26b18755304b74f817b79103ac2cce4dc277580 [diff] |
meta-phosphor: remove obmc-system-mgmt from qemu It was reported that after 5a5f33c729e6b5869362172b63595422eb84a418 the qemu images are not buildable. Treat qemu systems like an 'evb' so that the obmc-system-mgmt package is not included. Make a minor change to how evb is specified so that it is treated as a MACHINEOVERRIDE that can be leveraged in multiple recipes. Tested by ensuring that `evb-ast2600` still successfully resolves all package dependencies (with `bitbake -p`). Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Iff4573aa3d4aac30a6681ed75741a6e351bda982
- meta-phosphor/classes/obmc-phosphor-image.bbclass[diff]
- meta-phosphor/conf/machine/include/obmc-evb-common.inc[diff]
- .github/
- meta-amd/
- meta-ampere/
- meta-aspeed/
- meta-asrock/
- meta-bytedance/
- meta-evb/
- meta-facebook/
- meta-fii/
- meta-google/
- meta-hpe/
- meta-ibm/
- meta-ingrasys/
- meta-inspur/
- meta-intel-openbmc/
- meta-inventec/
- meta-nuvoton/
- meta-openembedded/
- meta-openpower/
- meta-phosphor/
- meta-quanta/
- meta-raspberrypi/
- meta-security/
- meta-supermicro/
- meta-wistron/
- meta-x86/
- meta-yadro/
- poky/
- bitbake ⇨ poky/bitbake/
- LICENSE ⇨ poky/LICENSE
- meta ⇨ poky/meta
- meta-poky ⇨ poky/meta-poky/
- meta-skeleton ⇨ poky/meta-skeleton
- oe-init-build-env ⇨ poky/oe-init-build-env
- scripts ⇨ poky/scripts/
- .eslintrc.json
- .gitignore
- .gitreview
- .templateconf
- MAINTAINERS
- openbmc-env
- OWNERS
- README.md
- setup
OpenBMC
OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your platform.
Setting up your OpenBMC project
1) Prerequisite
- Ubuntu 14.04
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
- Fedora 28
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"
2) Download the source
git clone git@github.com:openbmc/openbmc.git cd openbmc
3) Target your hardware
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 <machine> [build_dir] Target machine must be specified. Use one of: bletchley gsj romulus dl360poc kudo s2600wf e3c246d4i mihawk swift ethanolx mtjade tiogapass evb-ast2500 nicole transformers evb-ast2600 olympus-nuvoton witherspoon evb-npcm750 on5263m5 witherspoon-tacoma f0b p10bmc x11spi fp5280g2 palmetto yosemitev2 g220a qemuarm zaius gbs quanta-q71l
Once you know the target (e.g. romulus), source the setup script as follows:
. setup romulus
4) Build
bitbake obmc-phosphor-image
Additional details can be found in the docs repository.
OpenBMC Development
The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here
Build Validation and Testing
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.
Submitting Patches
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.
Bug Reporting
Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.
Questions
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 Discord 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 Discord.
Features of OpenBMC
Feature List
- Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog
- Full IPMI 2.0 Compliance with DCMI
- Code Update Support for multiple BMC/BIOS images
- Web-based user interface
- REST interfaces
- D-Bus based interfaces
- SSH based SOL
- Remote KVM
- Hardware Simulation
- Automated Testing
- User management
- Virtual media
Features In Progress
- OpenCompute Redfish Compliance
- Verified Boot
Features Requested but need help
- OpenBMC performance monitoring
Finding out more
Dive deeper into OpenBMC by opening the docs repository.
Technical Steering Committee
The Technical Steering Committee (TSC) guides the project. Members are:
- Brad Bishop (chair), IBM
- Nancy Yuen, Google
- Sai Dasari, Facebook
- James Mihm, Intel
- Sagar Dharia, Microsoft
- Samer El-Haj-Mahmoud, Arm