Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / b28e983772ec07969cb23d799e8c292933845aed
commitb28e983772ec07969cb23d799e8c292933845aed[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Tue Apr 17 14:24:01 2018 +0930
committerAndrew Geissler <geissonator@yahoo.com>Wed Apr 18 12:35:37 2018 +0000
treebab0604f6b36c27408f9d73cb4e864c6d14ca927
parentd1cbe5fd64dffa1dc7a3ef3c5331615182c74b7d [diff]
kernel: Add Nuvoton NPCM (Poleg), ncsi and romulus fixes

Brendan Higgins (3):
      MAINTAINERS: Add entry for the Nuvoton NPCM architecture
      arm: npcm: add basic support for Nuvoton BMCs
      arm: dts: add Nuvoton NPCM750 device tree

Eddie James (1):
      aspeed: watchdog: Set bootstatus during probe

Joel Stanley (3):
      serial: 8250: Add Nuvoton NPCM UART
      dt-bindings: watchdog: Add Nuvoton NPCM description
      watchdog: Add Nuvoton NPCM watchdog driver

Lei YU (1):
      ARM: dts: aspeed: romulus: Add id-button gpio key

Samuel Mendoza-Jonas (1):
      net/ncsi: Refactor MAC, VLAN filters

Tali Perry (2):
      dt-binding: clk: npcm750: add binding
      clk: npcm7xx: add clock controller

Tomer Maimon (10):
      arm: dts: add watchdog device to NPCM750 device tree
      arm: dts: modify UART compatible name in NPCM750 device tree
      arm: dts: modify timer register size in NPCM750 device tree
      arm: dts: modify clock binding in NPCM750 device tree
      arm: dts: modify Makefile NPCM750 configuration name
      arm: dts: modify Nuvoton NPCM7xx device tree structure
      arm: npcm: modify configuration for the NPCM7xx BMC.
      dt-binding: timer: document NPCM7xx timer DT bindings
      clocksource/drivers/npcm: Add NPCM7xx timer driver
      arm: npcm: enable L2 cache in NPCM7xx architecture

Change-Id: Ia5743a14d780d85a61c2796786eed483d7e2f78c
Signed-off-by: Joel Stanley <joel@jms.id.au>
1 file changed
tree: bab0604f6b36c27408f9d73cb4e864c6d14ca927
  1. import-layers/
  2. meta-openbmc-bsp/
  3. meta-openbmc-machines/
  4. meta-phosphor/
  5. bitbake ⇨ import-layers/yocto-poky/bitbake
  6. documentation ⇨ import-layers/yocto-poky/documentation
  7. LICENSE ⇨ import-layers/yocto-poky/LICENSE
  8. meta ⇨ import-layers/yocto-poky/meta
  9. meta-poky ⇨ import-layers/yocto-poky/meta-poky
  10. meta-selftest ⇨ import-layers/yocto-poky/meta-selftest
  11. meta-skeleton ⇨ import-layers/yocto-poky/meta-skeleton
  12. meta-yocto-bsp ⇨ import-layers/yocto-poky/meta-yocto-bsp
  13. oe-init-build-env ⇨ import-layers/yocto-poky/oe-init-build-env
  14. oe-init-build-env-memres ⇨ import-layers/yocto-poky/oe-init-build-env-memres
  15. scripts ⇨ import-layers/yocto-poky/scripts
  16. .gitignore
  17. .gitreview
  18. .templateconf
  19. openbmc-env
  20. README.md
  21. setup
README.md

OpenBMC

Build Status

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.

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 23
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake
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 variable known as TEMPLATECONF to be set to a hardware target. OpenBMC has placed all known hardware targets in a standard directory structure meta-openbmc-machines/meta-[architecture]/meta-[company]/meta-[target]. You can see all of the known targets with find meta-openbmc-machines -type d -name conf. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet

MachineTEMPLATECONF
Palmettometa-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf
Zaiusmeta-openbmc-machines/meta-openpower/meta-ingrasys/meta-zaius/conf
Witherspoonmeta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/conf

As an example target Palmetto

export TEMPLATECONF=meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf

4) Build

. openbmc-env
bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

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.

Features of OpenBMC

Feature List

  • REST Management
  • IPMI
  • SSH based SOL
  • Power and Cooling Management
  • Event Logs
  • Zeroconf discoverable
  • Sensors
  • Inventory
  • LED Management
  • Host Watchdog
  • Simulation
  • Code Update Support for multiple BMC/BIOS images
  • POWER On Chip Controller (OCC) Support

Features In Progress

  • Full IPMI 2.0 Compliance with DCMI
  • Verified Boot
  • HTML5 Java Script Web User Interface
  • BMC RAS

Features Requested but need help

  • OpenCompute Redfish Compliance
  • OpenBMC performance monitoring
  • cgroup user management and policies
  • Remote KVM
  • Remote USB
  • OpenStack Ironic Integration
  • QEMU enhancements

Finding out more

Dive deeper in to OpenBMC by opening the docs repository.

Contact