commit	8cd6dedc193cd2b7b13c3abfd04b1772c253e335	[log] [tgz]
author	Andrew Geissler <openbmcbump-github@yahoo.com>	Thu May 28 20:02:03 2020 +0000
committer	Andrew Geissler <geissonator@yahoo.com>	Tue Jun 02 17:43:36 2020 -0500
tree	a3da0036abfd4f002f9ca0846a075ad730c7fc4d
parent	b26dd2183d1f68562630d2d66eab977043ec0d9c [diff]

libmctp: srcrev bump 34b9b3d82b..ba6727e6d6

Andrew Jeffery (53):
      Add MAINTAINERS file
      bindings: Fix spaced-indentation
      serial: Fix unused result warning for write()
      mctp-demux-daemon: Fix erroneous call to memset()
      astlpc: Remove unused rc variable
      serial: Fix control reaching end of non-void function
      log: Allow disabling of stdio
      Add gitignore
      astlpc: Make sure fileio capability builds if we've requested it
      astlpc: Fix KCS read error mesage
      astlpc: Fix kcs_read() status check in mctp_astlpc_kcs_send()
      libmctp: Clarify BTU-related symbols
      mctp-demux-daemon: Explicitly disable verbose before option parsing
      configure: Add code coverage magic
      astlpc: mctp_astlpc_init_ops: constify ops struct
      tests: Add test_astlpc
      tests: Add test_serial
      core: Add packetisation debug statements
      astlpc: Add packet transmission debugging statements
      astlpc: Fix dummy byte IRQ trigger ordering
      test_serial: Fix assert triggered in core.c
      mctp-demux.service: Set a default binding to be overridden
      cmake: Avoid artifacts called liblibmctp*
      cmake: Register test executables with the build system
      cmake: Add new tests to test suite
      mctp-demux-daemon: Resolve uninitialised variable warning
      test_serial: Resolve control reaching end of non-void function
      alloc: Resolve control reaching the end of a non-void function
      test_bridge: Resolve control reaching the end of a non-void function
      test-utils: Resolve control reaching the end of a non-void function
      test-utils: Avoid undefined behaviour on indirect call
      core: Fix realloc() memory leak in packet reassembly
      libmctp: Add mctp_destroy()
      test-utils: Add mctp_binding_test_destroy()
      test_seq: Clean up after each test case
      test_eid: Clean up after test case
      astlpc: Add mctp_astlpc_destroy()
      test_astlpc: Clean up after test case
      serial: Add mctp_serial_destroy()
      test_serial: Clean up after test case
      bootstrap: Add a 'dev' mode
      mctp-demux-daemon: Silence warnings on remote close
      configure: Disable portability to cater to code-coverage
      bootstrap: Cleanup FLAGS definition
      bootstrap: Error on implicit function definitions
      astlpc: Use mctp_pr* inside libmctp
      astlpc: Conditionally include endian.h
      astlpc: Avoid requiring off_t
      configure: Expose optional features via AC_ARG_WITH()
      libmctp: Add .clang-format config
      clang-format: Disable AlignConsecutiveMacros
      libmctp: Add code formatting script
      test_astlpc: Do debug logging before asserts

Iwona Winiarska (1):
      MAINTAINERS: Add Iwona Winiarska as a reviewer

James Feist (1):
      CmakeLists.txt: Add missing flag

Jeremy Kerr (1):
      serial,astlpc: only include unistd.h if we're using file IO

Przemyslaw Czarnowski (1):
      Extract container_of definition out of individual bindings

Sumanth Bhat (1):
      Add Sumanth and Richard to reviewers

Wiktor Gołgowski (1):
      core: Support transport control commands

Xiaochao Ma (1):
      Add MCTP service file

(From meta-phosphor rev: b89f4aea500c1aa5aafb2a23a9cb8d732c1b6bf1)

Change-Id: I8522dfa3138678e56465472d3dd601ea1364590e
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>

meta-phosphor/recipes-phosphor/mctp/mctp_git.bb[diff]

1 file changed

tree: a3da0036abfd4f002f9ca0846a075ad730c7fc4d

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

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

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