Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / b66b4fc738bf55c39d8b46ef2db8cdf6e13c8f29
commitb66b4fc738bf55c39d8b46ef2db8cdf6e13c8f29[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Tue Aug 02 18:26:51 2022 +0930
committerJoel Stanley <joel@jms.id.au>Thu Aug 04 01:31:58 2022 +0000
tree8d6748576cfb342a8c32b7037af21d6fdc1ec6cc
parentdb7c651670d8b28144dd35c85c2fcc3d47456a14 [diff]
u-boot-aspeed: Rebase on SDK v00.04.11

This moves OpenBMC to the latest SDK from Aspeed.

Note that a series of fixes were sent to Aspeed on top of the SDK
release to ensure the OpenBMC configuration continued to work. These
changes have been merged by Aspeed but do not appear in a SDK tag at
this stage. Also sent to Aspeed were some of the changes from the
OpenBMC branch.

Changes from Aspeed's new SDK:

Billy Tsai (1):
      gpio: aspeed: Fix incorrect offset of read back register.

Chia-Wei Wang (3):
      Merge branch pull request #10 into aspeed-dev-v2019.04
      arm: aspeed: ast2600: Remove ASPEED_LOADERS
      configs: aspeed: Remove legacy defconfig

Chin-Ting Kuo (10):
      dts: aspeed: Create a device tree for DC-SCM solution
      dts: aspeed: Add ast2600-dcscm device tree
      spi-nor: Porting for S25HL series
      dts: aspeed: DC-SCM early bring up
      spi: aspeed: Fix bug when using 2Gb flash
      dts: aspeed: dc-scm: Add support for external mux
      spi_nor: Support s25hl without SFDP
      mtd: spi: Support Gigadevice device with 64KB sector size
      dts: aspeed: dc-scm: Extend bus-width to 4 for SPI1
      spi-nor: Add fast read command for S25HL series flash support

Dylan Hung (5):
      cmd/aspeed/nettest: apply addtional delay for RTL8211F
      dts: aspeed: enable mac1 for ast2600-dcscm
      cmd: aspeed: nettest: fix driving strength setting
      cmd: aspeed: support ctrl+c to break dramtest loop
      ram: aspeed: add AST2600 ODT configuration

Eddie James (2):
      ARM: dts: aspeed: tacoma: Add eMMC nodes and parameters
      ARM: dts: aspeed: rainier: Add eMMC nodes and parameters

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

Jammy Huang (11):
      pinctrl: ast2600: Add support for secure-i2c
      arm: dts: ast2600: Add definition for secure-i2c pinctrl
      misc: dp: Support re-driver
      misc: dp: Update dp-fw
      misc: dp: Refine code
      misc: dp: Update dp-fw
      misc: dp: Fix black screen occasionally
      misc: dp: Fix monitors black screen with 15m cable
      misc: dp: Fix black screen occasionally
      misc: dp: Improve compatibility
      misc: dp: Improve compatibility

Joel Stanley (5):
      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

Johnny Huang (4):
      cmd: aspeed: otp: fix otp status polling
      otp: update image checksum to SHA384
      otp: add 'verify' sub-command
      otp: add 'invalid' sub-command

Neal Liu (2):
      arm: aspeed: ast2600: select USB2.0 device mode as default
      arm: aspeed: ast2600: enable USB port B PHY clock

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

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

Tommy Huang (5):
      cmd: aspeed: DP CTS command utility
      cmd: aspeed: Update aspeed dptest default build config
      cmd: dptest: Arrange tab align
      cmd: aspeed: Fix the internal section compile fail
      i2c: ast_i2c: Remove SCL direct drive mode

ryan_chen (4):
      i2c:ast2600: add ast2600 new register mode driver
      pcie:aspeed : update reset sequnce.
      pcie:aspeed : fix two rc enable rc high config read timeout issue
      pcie:aspeed : update perst sequence

Change-Id: I2b79d15f7016913cae3f2b1d9cf6ee143136aaf2
Signed-off-by: Joel Stanley <joel@jms.id.au>
1 file changed
tree: 8d6748576cfb342a8c32b7037af21d6fdc1ec6cc
  1. .github/
  2. meta-amd/
  3. meta-ampere/
  4. meta-arm/
  5. meta-aspeed/
  6. meta-asrock/
  7. meta-bytedance/
  8. meta-evb/
  9. meta-facebook/
  10. meta-fii/
  11. meta-google/
  12. meta-hpe/
  13. meta-ibm/
  14. meta-ingrasys/
  15. meta-inspur/
  16. meta-intel-openbmc/
  17. meta-inventec/
  18. meta-nuvoton/
  19. meta-openembedded/
  20. meta-openpower/
  21. meta-phosphor/
  22. meta-qualcomm/
  23. meta-quanta/
  24. meta-raspberrypi/
  25. meta-security/
  26. meta-supermicro/
  27. meta-tyan/
  28. meta-wistron/
  29. meta-yadro/
  30. poky/
  31. bitbake ⇨ poky/bitbake/
  32. LICENSE ⇨ poky/LICENSE
  33. meta ⇨ poky/meta
  34. meta-poky ⇨ poky/meta-poky/
  35. meta-skeleton ⇨ poky/meta-skeleton
  36. oe-init-build-env ⇨ poky/oe-init-build-env
  37. scripts ⇨ poky/scripts/
  38. .eslintrc.json
  39. .gitignore
  40. .gitreview
  41. .templateconf
  42. openbmc-env
  43. OWNERS
  44. README.md
  45. 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

See the Yocto documentation for the latest requirements

Ubuntu

$ sudo apt install git python3-distutils gcc g++ make file wget \
    gawk diffstat bzip2 cpio chrpath zstd lz4 bzip2

Fedora

$ sudo dnf install git python3 gcc g++ gawk which bzip2 chrpath cpio
hostname file diffutils diffstat lz4 wget zstd rpcgen patch

2) Download the source

git clone https://github.com/openbmc/openbmc
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               mihawk                  swift
dl360poc                mori                    tatlin-archive-x86
e3c246d4i               mtjade                  tiogapass
ethanolx                nicole                  transformers
evb-ast2500             olympus-nuvoton         vegman-n110
evb-ast2600             on5263m5                vegman-rx20
evb-npcm750             p10bmc                  vegman-sx20
f0b                     palmetto                witherspoon
fp5280g2                quanta-q71l             witherspoon-tacoma
g220a                   romulus                 x11spi
gbs                     s2600wf                 yosemitev2
gsj                     s6q                     zaius
kudo                    s7106
lannister               s8036

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