Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 0ac3f966c9b593e5afe66c9c9046e65142274dc0
commit0ac3f966c9b593e5afe66c9c9046e65142274dc0[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Mon Apr 18 18:24:44 2022 +0930
committerPatrick Williams <patrick@stwcx.xyz>Mon Apr 18 17:51:01 2022 +0000
tree8f7e4dc9fa9d6e73fb0013ad5d040a18812228da
parent78477f674063ef2fe393cdba69144af6fe1b31a5 [diff]
u-boot-aspeed: Update to SDK v00.04.10

THe diff between the old commit and this one is below. This includes new
changes from the SDK, and the existing patches rebased on top of the new
SDK release.

Adriana Kobylak (1):
      configs: aspeed-common: Add redundant env for mmc

Chia-Wei Wang (1):
      configs: evb-ast2600-spl: Remove U-Boot MMC raw sector

Chin-Ting Kuo (5):
      spi_nor: aspeed: Update SPI driver
      spi: apseed: Update timing compensation calculation method
      dts: ast2600: Update decoded address size
      spi: aspeed: Fix resource size calculation method
      dts: aspeed: Sync the real scenario of AST2600 EVB

Dylan Hung (8):
      ram: aspeed: remove incorrect Vref information
      ram: aspeed: remove dead code and refine comment
      ram: aspeed: revise tRFI configuration
      ram: aspeed: fix incorrect printf
      ram: aspeed: revise coding style
      cmd: aspeed: nettest: add RTL8211F(D)-VD-CG support
      net: phy: realtek: Add RTL8211F-VD driver support
      clk: ast2600: fix ast2600_find_dly32_tap return value

Eddie James (5):
      gpio: Enable hogging support in SPL
      ast2600: Add GPIO controller and hog TPM reset pin
      ARM: dts: aspeed: tacoma: Add eMMC nodes and parameters
      ARM: dts: aspeed: rainier: Add eMMC nodes and parameters
      Add GPIO hogging support for AST2600 openbmc config

George Hung (1):
      ARM: dts: aspeed: add Quanta S6Q machine dts

Heiko Schocher (2):
      gpio: add gpio-hog support
      gpio: fixes for gpio-hog support

Jamin Lin (1):
      fix compiling warnings for AST2600 A1 SPL

Jammy Huang (1):
      misc: dp: Update fw

Jean-Jacques Hiblot (1):
      dm: Add a No-op uclass

Joel Stanley (15):
      Makefile: Conditionally add defaultenv_h to envtools target
      ast2600: spl: Fix build when accelerators are disabled
      ARM: dts: rainier: Enable ACRY and HACE
      ARM: dts: tacoma: Enable ACRY and HACE
      aspeed: Disable unused loaders, add STMICRO flash
      aspeed: Sort dts files in makefile
      as2600/scu: Fix printing of security info
      ast2600: spl: Implement board_boot_order
      configs: Add OpenBMC spl defconfig for AST2600 boards
      ast2600: Allow selection of SPL boot devices
      config: ast2600: Add config for SPL MMC boot with FIT signature verification
      ast2600: Add environment for booting from mmc
      ast2600/openbmc: Use emmc based configuration
      crypto: Restore old driver for Aspeed HACE
      ARM: dts: aspeed: Disable ACRY for rainier and tacoma

Neal Liu (3):
      crypto: aspeed: combine acry drivers into a file
      arm: dts: ast2600: add acry sram base
      crypto: aspeed: acry: add private allocated space for device

Peng Fan (1):
      tools: imx image: fix write warning

Potin Lai (1):
      ARM: dts: Aspeed: Add Bletchley dts

Troy Lee (2):
      ARM: aspeed: Disable ABR WDT when boot from UART with secure boot
      configs: aspeed: Increase SPL stack size

Zev Weiss (1):
      pinctrl: ast2400: add support for TXD3/RXD3 pins

ryan_chen (3):
      rename pcie driver for aspeed phy and pcie controller
      ast2600:bclk is come from epll. it will update in datasheet
      platform.S:ast2600: modify for only reset at AC on

Change-Id: I52b1be9474461e18dd26fd08472c2824485c1c09
Signed-off-by: Joel Stanley <joel@jms.id.au>
1 file changed
tree: 8f7e4dc9fa9d6e73fb0013ad5d040a18812228da
  1. .github/
  2. meta-amd/
  3. meta-ampere/
  4. meta-aspeed/
  5. meta-asrock/
  6. meta-bytedance/
  7. meta-evb/
  8. meta-facebook/
  9. meta-fii/
  10. meta-google/
  11. meta-hpe/
  12. meta-ibm/
  13. meta-ingrasys/
  14. meta-inspur/
  15. meta-intel-openbmc/
  16. meta-inventec/
  17. meta-nuvoton/
  18. meta-openembedded/
  19. meta-openpower/
  20. meta-phosphor/
  21. meta-quanta/
  22. meta-raspberrypi/
  23. meta-security/
  24. meta-supermicro/
  25. meta-tyan/
  26. meta-wistron/
  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. .eslintrc.json
  37. .gitignore
  38. .gitreview
  39. .templateconf
  40. openbmc-env
  41. OWNERS
  42. README.md
  43. setup
README.md

OpenBMC

Build Status

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 \
    zstd pigz
  • 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:

  • Roxanne Clarke, IBM
  • Nancy Yuen, Google
  • Sai Dasari, Facebook
  • Terry Duncan, Intel
  • Sagar Dharia, Microsoft
  • Samer El-Haj-Mahmoud, Arm

Contact