Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / 49e4f60aebffcc24a9e1258db392444e41877f99
commit49e4f60aebffcc24a9e1258db392444e41877f99[log] [tgz]
authorJohn Wang <wangzqbj@inspur.com>Thu Jun 27 11:32:53 2019 +0800
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Fri Jun 28 09:03:13 2019 -0400
treef2a10dd39e6dd7c87cf52fb589d992f4b8d7a914
parent0641c48da7b27177ae7260ac1f346d5f042de4b7 [diff]
fp5280g2: ipmi: Add dcmi config

Tested: Verified that temperature sensors are returned
        by `ipmitool dcmi get_temp_reading` command
	responses:
	Entity ID			Entity Instance	   Temp. Readings
	Inlet air temperature(40h)         		1		+27 C
	CPU temperature sensors(41h)       		1		+26 C
	CPU temperature sensors(41h)       		2		+26 C
	CPU temperature sensors(41h)       		3		+26 C
        ......
	CPU temperature sensors(41h)       		4		+26 C
	CPU temperature sensors(41h)       		5		+26 C
	Baseboard temperature sensors(42h) 		1		+29 C
	Baseboard temperature sensors(42h) 		2		+32 C

(From meta-inspur rev: 397f0495707790dd38f7c3f5a32a3c37d12556df)

Signed-off-by: John Wang <wangzqbj@inspur.com>
Change-Id: I59cc386c407a70cce81ea5b067ebe537524d0a9d
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: f2a10dd39e6dd7c87cf52fb589d992f4b8d7a914
  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-nuvoton/
  16. meta-openembedded/
  17. meta-openpower/
  18. meta-phosphor/
  19. meta-portwell/
  20. meta-qualcomm/
  21. meta-quanta/
  22. meta-raspberrypi/
  23. meta-security/
  24. meta-x86/
  25. meta-xilinx/
  26. meta-yadro/
  27. poky/
  28. bitbake ⇨ poky/bitbake/
  29. LICENSE ⇨ poky/LICENSE
  30. meta ⇨ poky/meta
  31. meta-poky ⇨ poky/meta-poky/
  32. meta-skeleton ⇨ poky/meta-skeleton
  33. oe-init-build-env ⇨ poky/oe-init-build-env
  34. scripts ⇨ poky/scripts/
  35. .gitignore
  36. .gitreview
  37. .templateconf
  38. MAINTAINERS
  39. openbmc-env
  40. README.md
  41. 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 variable known as TEMPLATECONF to be set to a hardware target. You can see all of the known targets with find meta-* -name local.conf.sample. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet

MachineTEMPLATECONF
Palmettometa-ibm/meta-palmetto/conf
Zaiusmeta-ingrasys/meta-zaius/conf
Witherspoonmeta-ibm/meta-witherspoon/conf
Romulusmeta-ibm/meta-romulus/conf

As an example target Palmetto

export TEMPLATECONF=meta-ibm/meta-palmetto/conf

4) Build

. openbmc-env
bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

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.

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

Features In Progress

  • OpenCompute Redfish Compliance
  • User management
  • Virtual media
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Contact