Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / 37e94cf4f0b7ab50617e75f45f0be9022fe1f257
commit37e94cf4f0b7ab50617e75f45f0be9022fe1f257[log] [tgz]
authorAndrew Geissler <openbmcbump-github@yahoo.com>Wed Apr 13 22:10:15 2022 +0000
committerAndrew Geissler <andrew@geissonator.com>Thu Apr 14 18:54:24 2022 +0000
tree6d96fdb64db204775ec9249545bde0bb87202cf0
parent9ee03306eaed0f1789744ee66881f216fba1f65f [diff]
entity-manager: srcrev bump e35d0acb7e..86022017ea

Andrew Jeffery (29):
      EntityManager: Rename findJsonFiles() to loadConfigurations()
      EntityManager: Rename DBusProbeObjectT to MapperGetSubTreeResponse
      EntityManager: Rename BasicVariantType to DBusValueVariant
      EntityManager: Remove dead ManagedObjectType definition
      EntityManager: Make MapperGetSubTreeResponse type comprehensible
      PerformScan: All interfaces on a path is an object
      PerformScan: Remove redundant early-return
      PerformScan: Extract processDbusObjects()
      PerformScan: Eliminate interfaceConnections
      PerformScan: Introduce DBusInterfaceInstance
      PerformScan: Clean up timer declarations using auto
      PerformScan: Make registerCallback() static
      PerformScan: Clean up whitespace in registerCallback()
      PerformScan: Eliminate else-after-return in getRecordName()
      PerformScan: Unwrap comments in getRecordName()
      PerformScan: Only hash if we're not debugging in getRecordName()
      PerformScan: Eliminate duplicate type check in run()
      Utils: Continue early in templateCharReplace() to avoid indentation
      Utils: Destructure interface properties in templateCharReplace()
      Utils: `templateChar + propName` is `templateName`
      Utils: Declare mathChars and nextItemIdx where they're used
      Utils: Break out expression parsing and evaluation
      Utils: Extract expression evaluation loop to Expression.cpp
      Utils: std::stoul() converts numbers in base 10 too
      Utils: Simplify 'replaced' loop exit in templateCharReplace()
      Expression: evaluate adjusts the end iterator to the end
      Utils: Drop redundant iteration guard
      Utils: Use consistent style in expression reconstruction
      Utils: Move result definition to where it's used

Jae Hyun Yoo (1):
      Add 24C04, 24C08, 24C16, 24C32, 24C128 and 24C256 EEPROMs

Change-Id: Ib1765849e99873b297e887d2d41f61a9248e5b54
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
1 file changed
tree: 6d96fdb64db204775ec9249545bde0bb87202cf0
  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