Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / f3823ad3d166dc19c373e67ab871d5480bcaf4da
commitf3823ad3d166dc19c373e67ab871d5480bcaf4da[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Mon Nov 30 15:31:36 2020 +1030
committerJoel Stanley <joel@jms.id.au>Thu Feb 11 00:06:17 2021 +0000
treef4d7d165e38d043618881e10ebbe0503e6358299
parent0d84c227694b49723552cd5e57e9168c61121d82 [diff]
linux-openbmc: Move to Linux 5.10

This moves the OpenBMC kernel to a v5.10 base for both Aspeed and
Nuvoton. There are 125 patches in the tree, with 80 of those patches not
yet queued for merging in v5.11.

Notably the PECI patchset has been dropped as the author, Intel, has
elected to develop it out of tree instead of submitting it for mainline
inclusion.

The remaining out of tree patches:

Alexander Amelkin (1):
      mtd: spi-nor: fix options for mx66l51235f

Andrew Geissler (1):
      ARM: dts: tacoma: Add KCS node for LPC MCTP

Andrew Jeffery (9):
      dt-bindings: hwmon: pmbus: Add Maxim MAX31785 documentation
      pmbus (max31785): Add support for devicetree configuration
      pmbus (core): Use driver callbacks in pmbus_get_fan_rate()
      pmbus (core): One-shot retries for failure to set page
      pmbus (max31785): Wrap all I2C accessors in one-shot failure handlers
      ARM: dts: aspeed: witherspoon: Update max31785 node
      misc: Add ASPEED KCS driver for MCTP purposes
      ARM: dts: witherspoon: Add KCS node for LPC MCTP
      ARM: dts: aspeed: rainier: Don't shout addresses

Brad Bishop (3):
      ipmi: aspeed-g6: Add compatible strings
      reset: simple: Add AST2600 compatibility string
      eeprom: at25: Split reads into chunks and cap write size

Cédric Le Goater (19):
      mtd: spi-nor: aspeed: use command mode for reads
      mtd: spi-nor: aspeed: add support for SPI dual IO read mode
      mtd: spi-nor: aspeed: link controller with the ahb clock
      mtd: spi-nor: aspeed: optimize read mode
      mtd: spi-nor: aspeed: limit the maximum SPI frequency
      mtd: spi-nor: aspeed: introduce a aspeed_smc_default_read() helper
      mtd: spi-nor: aspeed: clarify 4BYTE address mode mask
      mtd: spi-nor: aspeed: use memcpy_fromio() to capture the optimization buffer
      mtd: spi-nor: aspeed: add support for the 4B opcodes
      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
      /dev/mem: add a devmem kernel parameter to activate the device

Dan Carpenter (1):
      soc: aspeed: xdma: Return -EFAULT if copy_from_user() fails

Eddie James (9):
      ARM: dts: rainier: Add KCS node for LPC MCTP
      ARM: dts: aspeed: Add witherspoon-128 machine
      dt-bindings: fsi: Add P10 OCC device documentation
      fsi: occ: Add support for P10
      hwmon: (occ) Add new temperature sensor type
      dt-bindings: input: Add documentation for IBM Operation Panel
      input: misc: Add IBM Operation Panel driver
      ARM: dts: aspeed: rainier: Mark FSI SPI controllers as restricted
      ARM: dts: aspeed: Add Everest BMC machine

Fran Hsu (2):
      ARM: dts: nuvoton: npcm730: Add UDC device
      ARM: dts: nuvoton: gsj: Add non-mainline nodes

George Hung (2):
      dt-binding: edac: add NPCM ECC documentation
      edac: npcm: Add Nuvoton NPCM7xx EDAC driver

George Liu (2):
      ARM: dts: aspeed: inspur-fp5280g2: Add GPIO line names
      ARM: dts: aspeed: inspur-fp5280g2: Add ipsps1 driver

Jae Hyun Yoo (1):
      clk: ast2600: enable BCLK for PCI/PCIe bus always

Joel Stanley (4):
      ARM: dts: aspeed: ast2600evb: Add MAC0
      drm/aspeed: Add sysfs for output settings
      net: ftgmac100: Ensure tx descriptor updates are visible
      ARM: configs: aspeed: Update defconfigs

Quan Nguyen (1):
      ARM: dts: aspeed: Add device tree for Ampere's Mt. Jade BMC

Ryan Sie (1):
      ARM: dts: aspeed: Add Supermicro x11spi BMC machine

Tomer Maimon (21):
      dt-binding: bmc: Add NPCM7xx LPC BPC documentation
      misc: npcm7xx-lpc-bpc: add NPCM7xx BIOS post code driver
      dt-binding: bmc: add npcm7xx pci mailbox document
      misc: mbox: add npcm7xx pci mailbox driver
      dt-binding: net: document NPCM7xx EMC DT bindings
      net: npcm: add NPCM7xx Ethernet MAC controller
      ARM: dts: npcm7xx: Add out of tree nodes
      ARM: dts: olympus: Add non-mainline nodes
      ARM: dts: npcm750: Add fuse regmap support node
      ARM: dts: npcm7xx: Link fuse syscon to adc and wdt
      clk: npcm7xx: add read only flag to divider clocks
      iio: adc: Add calibration support to npcm ADC
      watchdog: npcm: Add DT restart priority and reset type support
      pinctrl: npcm7xx: Add HGPIO pin support to NPCM7xx pinctrl driver
      pinctrl: pinconf: add pin persist configuration
      pinctrl: npcm7xx: Add pin persist configuration support
      spi: npcm-pspi: Add full duplex support
      dt-binding: bmc: add NPCM7XX JTAG master documentation
      misc: Add NPCM7xx JTAG master driver
      watchdog: npcm: Modify get reset status function
      ARM: configs: add defconfig for Nuvoton NPCM7xx BMC

Troy Lee (3):
      dt-bindings: edac: aspeed-sdram-edac: Add ast2400/ast2600 support
      ARM: dts: aspeed: Add AST2600 edac into common devicetree
      edac: Supporting AST2400 and AST2600 edac driver

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

centriq2400-rep         nicole                     stardragon4800-rep2
f0b                     olympus                    swift
fp5280g2                olympus-nuvoton            tiogapass
gsj                     on5263m5                   vesnin
hr630                   palmetto                   witherspoon
hr855xg2                qemuarm                    witherspoon-128
lanyang                 quanta-q71l                witherspoon-tacoma
mihawk                  rainier                    yosemitev2
msn                     romulus                    zaius
neptune                 s2600wf

Once you know the target (e.g. romulus), source the setup script as follows:

. setup romulus build

For evb-ast2500, please use the below command to specify the machine config, because the machine in meta-aspeed layer is in a BSP layer and does not build the openbmc image.

TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env

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:

  • Brad Bishop (chair), IBM
  • Nancy Yuen, Google
  • Sai Dasari, Facebook
  • James Mihm, Intel
  • Sagar Dharia, Microsoft
  • Supreeth Venkatesh, Arm

Contact