Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 71f614cf20acf4eafc2236e6bac9e81e7890ffd6
commit71f614cf20acf4eafc2236e6bac9e81e7890ffd6[log] [tgz]
authorAndrew Geissler <openbmcbump-github@yahoo.com>Mon Oct 31 19:02:02 2022 -0500
committerPatrick Williams <patrick@stwcx.xyz>Fri Nov 04 01:41:12 2022 +0000
treee65f645a8d3e7c23b3b90456b15c5f5557b01abe
parent2390b1b6299fb1e57e6d9a94c287ce1c0b322376 [diff]
phosphor-networkd: srcrev bump f7dce2e866..6bf7a7d631

Ali El-Haj-Mahmoud (1):
      Treat link-local addresses as static when link local autoconfig is disabled.

Asmitha Karunanithi (2):
      Set static & dhcp sent ntp server ip on ethernet obj
      Move dbus method call into try-catch block

William A. Kennington III (26):
      netlink: Improve error output
      util: Don't directly include config_parser.hpp
      util: Fix mac truncation
      util: Refactor isValidPrefix to reduce address family re-use
      util: Remove unused toMask
      util: Refactor addrFromBuf
      util: isValidIP should be noexcept
      util: Refactor IP toString
      util: Add non-family isValidIP
      ethernet_interface: Simplify hwaddr string
      network_manager: Cleanup VLAN creation
      network_manager: Cleanup map type
      network_manager: Inline trivial functions
      network_manager: Allow direct access to interfaces
      ethernet_interface: Use string_umaps where sensible
      build: Cleanup subprojects and gitignore
      treewide: Clean up string parameters
      ipaddress: Remove obsolete gateway parameter
      ethernet_interface: Refactor object hashing
      ethernet_interface: Remove unused resolvconf file
      ethernet_interface: Always try ethtool as we handle unsupported
      ethernet_interface: Add error logging for ethtool queries
      ethernet_interface: Refactor ethtool querying
      test/ethernet_interface: Improve syscall test coverage
      treewide: Remove redundant inline
      vlan_interface: Remove interface name usage

Change-Id: Ia9f3c8312333902c554cb8bed4e7e71faada0e3a
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
1 file changed
tree: e65f645a8d3e7c23b3b90456b15c5f5557b01abe
  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. .templateconf ⇨ poky/.templateconf
  32. bitbake ⇨ poky/bitbake/
  33. LICENSE ⇨ poky/LICENSE
  34. meta ⇨ poky/meta
  35. meta-poky ⇨ poky/meta-poky/
  36. meta-skeleton ⇨ poky/meta-skeleton
  37. oe-init-build-env ⇨ poky/oe-init-build-env
  38. scripts ⇨ poky/scripts/
  39. .eslintrc.json
  40. .gitignore
  41. .gitreview
  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               mori                    s8036
dl360poc                mtjade                  swift
e3c246d4i               mtmitchell              tatlin-archive-x86
ethanolx                nicole                  tiogapass
evb-ast2500             olympus-nuvoton         transformers
evb-ast2600             on5263m5                vegman-n110
evb-npcm750             p10bmc                  vegman-rx20
f0b                     palmetto                vegman-sx20
fp5280g2                qcom-dc-scm-v1          witherspoon
g220a                   quanta-q71l             witherspoon-tacoma
gbs                     romed8hm3               x11spi
greatlakes              romulus                 yosemitev2
gsj                     s2600wf                 zaius
kudo                    s6q
lannister               s7106

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