Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / cddb4fb6b19b576f5b42bd65fbf32d489c01074f
commitcddb4fb6b19b576f5b42bd65fbf32d489c01074f[log] [tgz]
authorJoseph Liu <kwliu@nuvoton.com>Thu Jul 16 14:25:00 2020 +0800
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Tue Aug 11 07:44:25 2020 -0400
tree170e88197efd11d18553ba1df4f57df40f7bcd0b
parent73c58c41840567d5947eb2f8141f96d11839fa21 [diff]
u-boot-nuvoton: srcrev bump adb4ac1af3...6870e66f6b

This includes bug fixs, pinctrl driver and npcm730/gis/gbs dts.

Avi Fishman (6):
      board: nuvoton: poleg: fix dram size for 2GB would configure to 128MB
      npcm: clean warnings
      ARM: npcm7xx: add registers gcr
      configs: npcm7xx: add MEMTEST command
      npcm7xx: fix: L2 cache invalidate 16 ways
      configs: npcm7xx: add CONFIG_HUSH_PARSER command

Brian Ma (5):
      npcm7xx: runbmc: buv: add DTS for BUV board
      driver: emc: add fixed phy support
      arch: arm: dts: remove BUV unused emc/gmac
      dts: npcm7xx: add common and pincfg dtsi
      arch: npcm750: reset: workaround BUV get CORSR when PORST

Fran Hsu (3):
      Add 'CONFIG_SYS_MEM_TOP_HIDE' to Poleg minimal defconfig.
      Commit u-boot DTS files for the GIS project.
      u-boot: GIS system dts update.

George Hung (5):
      dts: npcm730 GBS: add dts/pinctrl support
      dts:npcm730 GBS: add the missing GPIs initial
      dts: npcm730 GBS: add event clear to GPIO59
      dts: npcm730 GBS: add event clear to some GPIs and init GPIO74
      dts: npcm730 GBS: fix the GPIO91 setting

Joseph Liu (20):
      npcm7xx: runbmc: set the graphic reset delay value
      arch: arm: dts: add nuvoton-npcm750-olympus dts file
      board: nuvoton: poleg: init board by machine name
      board: nuvoton: poleg: olympus: remove reset control
      arch: arm: cpu: npcm750: correct cpu info
      arch: arm: npcm750: add get reboot reason
      drivers: pinctrl: add npcm7xx pinctrl driver
      dts: add nuvoton-npcm7xx-pinctrl.dtsi
      dts: npcm750 olympus: add pinctrl support
      dts: npcm750 evb: add pinctrl support
      board: nuvoton: poleg: remove mfsel settings
      drivers: nuvoton: remove mfsel configs
      doc: nuvoton npcm7xx introduce pinctrl device tree binding
      driver: pinctrl: npcm7xx: add event clear support
      driver: pinctrl: npcm7xx: corrects input setting
      driver: pinctrl: npcm7xx: corrects persist state
      driver: pinctrl: npcm7xx: corrects polarity setting
      Revert "driver: pinctrl: npcm7xx: corrects persist state"
      configs: runbmc: add hush parser and mtest command
      cmd: standalone test: support at least one test

Kun Yi (3):
      nuvoton: poleg.h: Add kernel reboot on oops/panic to bootargs
      npcm7xx: defconfig: Branch and remove unneeded functions
      dts: Add DTS for NPCM730

Medad CChien (3):
      u-boot: Support MFG Test
      u-boot: Add config to enable saving log in header
      u-boot: mfg test: Remove saving mtest result

Stanley Chu (1):
      npcm7xx: allow to config SYS_MEM_TOP_HIDE by defconfig

(From meta-nuvoton rev: c254937c929f03da19cac9fba7dc9bed6ef2acd6)

Change-Id: I74afb9ab6d78e16b5b12fa27ef890f6b75629cc7
Signed-off-by: Joseph Liu <kwliu@nuvoton.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: 170e88197efd11d18553ba1df4f57df40f7bcd0b
  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 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