commit	ce4c8a920589566faceffcec5e95810474ce972a	[log] [tgz]
author	Andrew Geissler <openbmcbump-github@yahoo.com>	Tue Nov 20 04:00:24 2018 +0000
committer	Brad Bishop <bradleyb@fuzziesquirrel.com>	Tue Nov 20 21:58:09 2018 -0500
tree	0bdf3da839fb1e145875e7497988f46a27bb046f
parent	7bc57b8c79d534d46c618f59bf903b8325c74fe1 [diff]

phosphor-ipmi-flash: srcrev bump 4306f68bf4..09114c1c48

Patrick Venture (57):
      Enable firmware transport mechanisms
      firmware: implement canHandleBlob
      rename: Rename firmware to blobid where appropriate
      gitignore: Add test-driver
      test: Add first unit-test to verify factory
      main: handle error checking with handler creation
      firmware: add active blob ids
      firmware: implement stat command
      test: fixup unit-test naming
      tests: Add unit-tests for canHandleBlob
      firmware: start implementing open
      add image_handler interface for open
      firmware: add handler for static layout
      firmware: add write method
      add data handler interface
      firmware: move enum into class
      set up data handler mechanism
      firmware: invert conditions to reduce depth
      tests: add unit-tests for opening
      build: cleanup makefile whitespace
      firmware: add active to canhandle blob list
      firmware: start notion of a session
      s/::bt/::ipmi/g to be more correct
      firmware: set up hash handler
      firmware: add a session lookup map
      firmware: tie implementation of session into write
      tests: cleanup test code
      firmware: add read/write configuration methods
      firmware: add global state for the process
      firmware: prevent writing or opening during verification
      style: s/FirmwareUpdateFlags/UpdateFlags/g
      pci: continued implementation in P2A bridge handler
      data handler: add open method
      data handler: add close method
      pci: add region parameter to constructor
      static: add temporary filename for staging update
      session: add per session state information
      session: start tracking open state
      firmware: add verification response enum
      firmware: cleanup - cleaned up some documentation
      firmware: return failure on attempt to open active files
      bugfix: active blob id added on open failure
      firmware: tie in call to data handler's open
      firmware: enable fileOpen state
      session: start tracking active path for session
      firmware: start implementing close method
      add createHandler method per phosphor-ipmi-blobs change
      add lpc mapping interface and stubs
      lpc_handler: drop-in call to mapWindow on writeMeta
      lpc_handler: add note to copyFrom stub
      firmware: start implementing deleteBlob
      static_handler: implement basic version
      lpc_handler also requires a BMC address for mapping
      hash handler: implement file hash handler
      static handler: transition to generic file handler
      lpc: add missing headers
      build: add lpc source files

(From meta-phosphor rev: d6cb25029962e91ee4cdba9b795a96b4f3ce6e06)

Change-Id: I40796a7ae5496c6cdd19b66093ab83f6edb5572e
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>

meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-flash_git.bb[diff]

1 file changed

tree: 0bdf3da839fb1e145875e7497988f46a27bb046f

README.md

OpenBMC

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
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

Machine	TEMPLATECONF
Palmetto	`meta-ibm/meta-palmetto/conf`
Zaius	`meta-ingrasys/meta-zaius/conf`
Witherspoon	`meta-ibm/meta-witherspoon/conf`
Romulus	`meta-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

REST Management
IPMI
SSH based SOL
Power and Cooling Management
Event Logs
Zeroconf discoverable
Sensors
Inventory
LED Management
Host Watchdog
Simulation
Code Update Support for multiple BMC/BIOS images
POWER On Chip Controller (OCC) Support

Features In Progress

Full IPMI 2.0 Compliance with DCMI
Verified Boot
HTML5 Java Script Web User Interface
BMC RAS

Features Requested but need help

OpenCompute Redfish Compliance
OpenBMC performance monitoring
cgroup user management and policies
Remote KVM
Remote USB
OpenStack Ironic Integration
QEMU enhancements

Finding out more

Dive deeper in to OpenBMC by opening the docs repository.

Contact

Mail: openbmc@lists.ozlabs.org https://lists.ozlabs.org/listinfo/openbmc
IRC: #openbmc on freenode.net
Riot: #openbmc:matrix.org