Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 661122dbec1d82991925c5a0f45f7970816ce390
commit661122dbec1d82991925c5a0f45f7970816ce390[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Thu Aug 22 15:42:07 2019 +0930
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Thu Aug 22 12:13:56 2019 -0400
tree5c1405dec21e2b00a4ab568fc64ffd59def06b96
parent760eaab591b415723d2caac4f44f0541397c14b3 [diff]
linux-aspeed: eMMC and ast2600 support

Andrew Jeffery (13):
      dt-bindings: mmc: Document Aspeed SD controller
      mmc: Add support for the ASPEED SD controller
      ARM: dts: aspeed: Describe SD controllers
      pinctrl: aspeed-g5: Delay acquisition of regmaps
      pinctrl: aspeed: Rename pin declaration macros
      pinctrl: aspeed: Add PIN_DECL_3() helper
      pinctrl: aspeed: Add multiple pin group support for functions
      pinctrl: aspeed: Add SIG_DESC_CLEAR() helper
      pinctrl: aspeed: Add AST2600 pinmux support
      pinctrl: aspeed-g6: Fix I2C14 function name typo
      pinctrl: aspeed-g6: Fix mislabeled PWM groups and functions
      pinctrl: aspeed-g6: Add EMMC pin group
      ARM: dts: aspeed: Add AST2600 pinmux nodes

Joel Stanley (12):
      ARM: dts: aspeed: swift: Add eMMC device
      dt-bindings: watchdog: Add ast2600 compatible
      clk: aspeed: Move structures to header
      clk: Add support for AST2600 SoC
      ARM: aspeed: Select timer in each SoC
      ARM: aspeed: Add ASPEED AST2600 architecture
      ARM: aspeed: Enable SMP boot
      ARM: dts: aspeed: Add AST2600 and EVB
      ARM: configs: aspeed_g5: Enable AST2600
      fsi: Add ast2600 master driver
      ARM: dts: aspeed-g6: Describe FSI masters
      ARM: dts: aspeed: ast2600evb: Enable FSI master

Ryan Chen (1):
      watchdog: aspeed: Add support for AST2600

YueHaibing (1):
      pinctrl: aspeed: Make aspeed_pinmux_ips static

(From meta-aspeed rev: 40df7ebc32ddecc28126c3726c79b25fe1b0feb2)

Change-Id: I005c90c8106f3857e45ada4ac93456b3665b20b3
Signed-off-by: Joel Stanley <joel@jms.id.au>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: 5c1405dec21e2b00a4ab568fc64ffd59def06b96
  1. .github/
  2. meta-arm/
  3. meta-aspeed/
  4. meta-evb/
  5. meta-facebook/
  6. meta-google/
  7. meta-hxt/
  8. meta-ibm/
  9. meta-ingrasys/
  10. meta-inspur/
  11. meta-intel/
  12. meta-inventec/
  13. meta-lenovo/
  14. meta-mellanox/
  15. meta-microsoft/
  16. meta-nuvoton/
  17. meta-openembedded/
  18. meta-openpower/
  19. meta-phosphor/
  20. meta-portwell/
  21. meta-qualcomm/
  22. meta-quanta/
  23. meta-raspberrypi/
  24. meta-security/
  25. meta-x86/
  26. meta-xilinx/
  27. meta-yadro/
  28. poky/
  29. bitbake ⇨ poky/bitbake/
  30. LICENSE ⇨ poky/LICENSE
  31. meta ⇨ poky/meta
  32. meta-poky ⇨ poky/meta-poky/
  33. meta-skeleton ⇨ poky/meta-skeleton
  34. oe-init-build-env ⇨ poky/oe-init-build-env
  35. scripts ⇨ poky/scripts/
  36. .gitignore
  37. .gitreview
  38. .templateconf
  39. MAINTAINERS
  40. openbmc-env
  41. README.md
  42. 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 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 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

MachineTEMPLATECONF
Palmettometa-ibm/meta-palmetto/conf
Zaiusmeta-ingrasys/meta-zaius/conf
Witherspoonmeta-ibm/meta-witherspoon/conf
Romulusmeta-ibm/meta-romulus/conf

As an example target Palmetto

export TEMPLATECONF=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

  • 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

Features In Progress

  • OpenCompute Redfish Compliance
  • User management
  • Virtual media
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Contact