Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 6314859cbf35ed85a9e26f11b15ac7097cb2e9ef
commit6314859cbf35ed85a9e26f11b15ac7097cb2e9ef[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Thu Sep 26 23:03:39 2019 +0930
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Thu Sep 26 12:21:52 2019 -0400
tree29cb14bd2e315dfb246b887a746bc63f61b6ecd4
parent95ccc7320c91fbc34c8edb5bf9c22092fdbf06a3 [diff]
linux-aspeed: AST2600: spi-nor, NCSI clock, Rainier

Andrew Jeffery (6):
      dt-bindings: clock: Add AST2500 RMII RCLK definitions
      dt-bindings: clock: Add AST2600 RMII RCLK gate definitions
      clk: aspeed: Add RMII RCLK gates for both AST2500 MACs
      clk: ast2600: Add RMII RCLK gates for all four MACs
      net: ftgmac100: Ungate RCLK for RMII on ASPEED MACs
      ARM: dts: aspeed: Add RCLK to MAC clocks for RMII interfaces

Brad Bishop (9):
      soc: aspeed: lpc: Add G6 compatible strings
      ipmi: aspeed-g6: Add compatible strings
      reset: simple: Add AST2600 compatibility string
      ARM: dts: aspeed-g6: Add lpc devices
      ARM: dts: aspeed-g6: Expose SuperIO scratch registers
      ARM: dts: Add 128MiB OpenBMC flash layout
      ARM: dts: aspeed: Add Rainier system
      ARM: dts: aspeed: rainier: Add mac devices
      ARM: dts: aspeed: rainier: Add i2c devices

Cédric Le Goater (12):
      mtd: spi-nor: Add support for w25q512jv
      mtd: spi-nor: aspeed: Introduce a field for the AHB physical address
      mtd: spi-nor: aspeed: Introduce segment operations
      mtd: spi-nor: aspeed: add initial support for ast2600
      mtd: spi-nor: aspeed: Check for disabled segments on the AST2600
      mtd: spi-nor: aspeed: Introduce training operations per platform
      mtd: spi-nor: aspeed: Introduce a HCLK mask for training
      mtd: spi-nor: aspeed: check upper freq limit when doing training
      mtd: spi-nor: aspeed: add support for AST2600 training
      ARM: dts: aspeed-g6: Add FMC and SPI devices
      ARM: dts: aspeed: rainier: Enable FMC and SPI devices
      ARM: dts: ast2600-evb: Enable FMC and SPI devices

Joel Stanley (3):
      ARM: dts: aspeed: tacoma: Enable FMC and SPI devices
      ARM: dts: aspeed: ast2600evb: Use custom flash layout
      ARM: dts: aspeed: tacoma: Disable CS1 as it is broken

(From meta-aspeed rev: 6f2dd84f3f30c9777ce956d5ad56de7d04bb227c)

Change-Id: I774fa833665c5d84cf58df5cd7315cadaf56754b
Signed-off-by: Joel Stanley <joel@jms.id.au>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: 29cb14bd2e315dfb246b887a746bc63f61b6ecd4
  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