linux-aspeed: Move to Linux 5.8

This updates the OpenBMC kernel tree to a 5.8 base. It has beent two
weeks since the kernel was last updated, making it the quickest bump in
OpenBMC history.

There are 93 out of tree kernel patches carried in the OpenBMC tree.

The defconfigs were updated to fix selection of video device. An
upstream reorganisation of the V4L kconfig resulted in a large number of
extra drivers enabled when all we required was VIDEO_ASPEED.

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

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

Andrew Jeffery (13):
      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
      soc: aspeed: Miscellaneous control interfaces
      ARM: dts: aspeed: witherspoon: Update max31785 node
      ARM: dts: aspeed-g5: Expose VGA and SuperIO scratch registers
      pinctrl: aspeed: Improve debug output
      soc: aspeed: Fail probe of lpc-ctrl if reserved memory is not aligned
      misc: Add ASPEED KCS driver for MCTP purposes
      ARM: dts: witherspoon: Add KCS node for LPC MCTP
      pinctrl: aspeed: Describe the heartbeat function on ball Y23

Ben Tyner (1):
      ARM: dts: aspeed: witherspoon-128: Remove checkstop GPIO from gpio-keys definitions

Brad Bishop (4):
      ARM: dts: aspeed-g6: Expose SuperIO scratch registers
      soc: aspeed: lpc: Add G6 compatible strings
      ipmi: aspeed-g6: Add compatible strings
      reset: simple: Add AST2600 compatibility string

Cédric Le Goater (22):
      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
      mtd: spi-nor: aspeed: fix training of multiple CS on the AST2600
      mtd: spi-nor: aspeed: Disable zero size segments on the AST2600
      spi-nor: aspeed-smc: Detect 4b opcodes differently
      /dev/mem: add a devmem kernel parameter to activate the device

Eddie James (11):
      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
      i2c: fsi: Prevent adding adapters for ports without dts nodes
      dt-bindings: soc: Add Aspeed XDMA Engine
      soc: aspeed: Add XDMA Engine Driver
      soc: aspeed: xdma: Add user interface
      soc: aspeed: xdma: Add reset ioctl
      leds: pca955x: Add an IBM software implementation of the PCA9552 chip

Fran Hsu (3):
      ARM: dts: nuvoton: Add NPCM730 common device tree
      ARM: dts: nuvoton: Add Quanta GSJ BMC pinctrl
      ARM: dts: nuvoton: Add Quanta GSJ BMC

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

Jae Hyun Yoo (12):
      clk: ast2600: enable BCLK for PCI/PCIe bus always
      dt-bindings: Add PECI subsystem document
      Documentation: ioctl: Add ioctl numbers for PECI subsystem
      peci: Add support for PECI bus driver core
      dt-bindings: Add bindings document of Aspeed PECI adapter
      ARM: dts: aspeed: Add PECI node
      peci: Add Aspeed PECI adapter driver
      dt-bindings: mfd: Add Intel PECI client bindings document
      mfd: intel-peci-client: Add Intel PECI client driver
      Documentation: hwmon: Add documents for PECI hwmon drivers
      hwmon: Add PECI cputemp driver
      hwmon: Add PECI dimmtemp driver

Joel Stanley (10):
      ARM: dts: aspeed-g4: Expose SuperIO scratch registers
      ARM: dts: nuvoton: Fix warnings in NPCM7xx common device tree
      ARM: dts: nuvoton: Update EVB for new PECI layout
      ARM: dts: nuvoton: evb: Rework enabling of nodes
      soc: aspeed-lpc-ctrl: LPC to AHB mapping on ast2600
      ARM: dts: aspeed: ast2600evb: Add MAC0
      soc: aspeed-lpc-ctrl: Fix printf warning
      ARM: configs: aspeed: Update defconfigs
      ARM: config: aspeed-g5: Enable I2C GPIO mux driver
      ARM: config: aspeed: Fix selection of video device
      mtd: spi-nor: sfdp: Revert "default to addr_width of 3 for configurable widths"
      ARM: aspeed: g5: Do not set sirq polarity

Tomer Maimon (11):
      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: configs: add defconfig for Nuvoton NPCM7xx BMC
      ARM: dts: npcm7xx: Update device tree
      arm: dts: Add NPCM7xx RunBMC Olympus Quanta machine.
      dt-bindings: peci: add NPCM PECI documentation
      peci: npcm: add NPCM PECI driver

(From meta-aspeed rev: 3c9616235643263beea47ef5db5cecafa3349c2e)

Change-Id: I4616f47026e00e49bda0abb1fc586dd2faabee30
Signed-off-by: Joel Stanley <joel@jms.id.au>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
3 files changed
tree: c317abdb4b9a571e231a65a8ed0f34048efb282d
  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. .gitignore
  30. .gitreview
  31. .templateconf
  32. MAINTAINERS
  33. openbmc-env
  34. README.md
  35. 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 IRC 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 IRC.

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