Skip to content
No description, website, or topics provided.
Python BitBake C Shell PHP Roff Other
Branch: intel
Clone or download
Latest commit cfbc9ea Oct 29, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update to internal 10-28-19 Oct 29, 2019
meta-arm packagegroups: Remove obmc-mgr-system Oct 8, 2018
meta-aspeed Merge branch 'master' of ssh://… Oct 28, 2019
meta-evb meta-evb: Remove references to EVBBASE Sep 14, 2019
meta-facebook meta-facebook: fb-ipmi-oem: Added description json Oct 15, 2019
meta-google google-ipmi-sys: srcrev bump 0c0bfd3a14..cc53c847f1 Oct 2, 2019
meta-ibm Merge branch 'master' of ssh://… Oct 28, 2019
meta-ingrasys meta-ingrasys: layer.conf: add zeus compatibility Sep 20, 2019
meta-inspur fp5280g2: Enable TFTP updates via Redfish Oct 9, 2019
meta-intel intel-ipmi-oem: srcrev bump ca99ef5912..262276f496 Oct 24, 2019
meta-inventec meta-inventec: Remove references to INVENTECBASE Sep 16, 2019
meta-lenovo meta-lenovo: hr855xg2: flash: update bbappend Jul 26, 2019
meta-mellanox meta-mellanox: msn: mlx-ipmid: rename as git Oct 19, 2018
meta-microsoft Initial git pull request for meta-olympus. Jul 8, 2019
meta-nuvoton meta-nuvoton: Add zeus compatibility Oct 16, 2019
meta-openbmc-mods Update to internal 10-28-19 Oct 29, 2019
meta-openembedded meta-openembedded: subtree update:1bfaa2e63a..64224b92e5 Oct 21, 2019
meta-openpower openpower-pnor-code-mgmt: srcrev bump b41a57d52c..85f2540759 Oct 23, 2019
meta-phosphor dbus-sensors: srcrev bump 432d1edf7a..4316218ab8 Oct 24, 2019
meta-portwell/meta-neptune [Subtree] Bring openbmc machines to top level Aug 23, 2018
meta-qualcomm meta-qualcomm: Remove references to QUALCOMMBASE Sep 18, 2019
meta-quanta meta-quanta: gsj: quanta-nvme_powerctrl: fix setting initial SSD[i] G… Oct 17, 2019
meta-raspberrypi meta-raspberrypi: subtree update:cee2557dc8..4776ecc532 Oct 23, 2019
meta-security meta-security: subtree update:c55721b15e..27ddb45554 Oct 21, 2019
meta-x86/conf meta-x86: Add Zeus compatibility Oct 18, 2019
meta-xilinx meta-xilinx: subtree update:68eacd5636..391c7054e8 Sep 9, 2019
poky Merge branch 'master' of ssh://… Oct 28, 2019
.gitignore Add .repo/ to .gitignore Dec 16, 2016
.gitreview git-review config for Aug 2, 2016
.templateconf Combine poky and meta-phosphor as subtrees. Sep 15, 2015
LICENSE [Subtree] Removing import-layers directory Aug 23, 2018
MAINTAINERS Add MAINTAINERS file May 30, 2018 Add Wolf Pass build info back into Oct 25, 2019
bitbake [Subtree] Removing import-layers directory Aug 23, 2018
meta [Subtree] Removing import-layers directory Aug 23, 2018
meta-poky [Subtree] Removing import-layers directory Aug 23, 2018
meta-skeleton openbmc: Add top-level link to poky/meta-skeleton Oct 30, 2018
oe-init-build-env [Subtree] Removing import-layers directory Aug 23, 2018
openbmc-env Environment helper utility. Sep 16, 2015
scripts [Subtree] Removing import-layers directory Aug 23, 2018
setup Make `setup` show available targets in columns Aug 20, 2019


Build status

Intel-BMC/openbmc is a BMC implementation for servers. The purpose is to provide early access to features and capabilities which have not yet been accepted or merged in the OpenBMC main project ( In due course, all of the capabilities here will be brought to the OpenBMC project.

Some answers to the main questions that tend to get asked:

Does this mean that Intel is no longer contributing to the Linux foundation project?

No. This repo is for components that are intended for the eventual release to the LF OpenBMC project. There are a number of reasons where things might be checked in here. For example: functionality that is still under discussion or in the LF OpenBMC project, features that have not gone through the level of testing or integration needed to be included in the OpenBMC project

Why does this repo exist at all?

Upstreaming changes to the linux kernel, uboot, systemd, yocto, and the various projects that OpenBMC pulls in requires a significant effort. While we aspire to that process being fast, painless, and with minimal rework, the reality is far from that, and features or functions that require changes across a number of repos require a coordinated effort, and a single source of function. As a general rule, this repository loosens the requirements of "form over function" and prefers to make some simplifying assumptions of BMC capabilities, chipsets, and required features.

Can I upstream/release the code from this repository?

It very much depends on the component. While in general the answer ends up being "yes", prior approval should be granted, as this repo contains future facing capabilities that may not have been announced yet. Please email to discuss. Appropriate licenses will be applied to the portions of this codebase that are approved for upstreaming.

Which platforms does this code work on?

While the code is easily portable across different type of IA platforms, currently we use Intel’s Wolf Pass (S2600WP) platform for development and most testing.

How to build for Wolf Pass

source oe-init-build-env
bitbake intel-platforms
You can’t perform that action at this time.