commit	33812da79001c5dcdb2cc9d15e9786d8e42afddc	[log] [tgz]
author	Joel Stanley <joel@jms.id.au>	Fri Mar 18 14:15:16 2022 +1030
committer	Joel Stanley <joel@jms.id.au>	Fri Mar 18 14:16:02 2022 +1030
tree	3ce075ca8710cdc209fd1cec655879ebb0e76850
parent	24f6d997ed5271f8e6506b6ece197a248c2307ad [diff]

linux-aspeed: MCTP core and drivers

Backport of the MCTP core and drivers from mainline provided by Jeremy
and Matt.

Eugene Syromiatnikov (1):
      mctp: handle the struct sockaddr_mctp_ext padding field

Gagan Kumar (1):
      mctp: Remove only static neighbour on RTM_DELNEIGH

Jeremy Kerr (29):
      mctp: Allow local delivery to the null EID
      mctp: locking, lifetime and validity changes for sk_keys
      mctp: Add refcounts to mctp_dev
      mctp: Implement a timeout for tags
      mctp: Add tracepoints for tag/key handling
      mctp: Do inits as a subsys_initcall
      doc/mctp: Add a little detail about kernel internals
      mctp: Add initial test structure and fragmentation test
      mctp: Add test utils
      mctp: Add packet rx tests
      mctp: Add route input to socket tests
      mctp: Add input reassembly tests
      mctp: Implement extended addressing
      mctp: Return new key from mctp_alloc_local_tag
      mctp: Add flow extension to skb
      mctp: Pass flow data & flow release events to drivers
      mctp/test: Update refcount checking in route fragment tests
      mctp: Add MCTP-over-serial transport binding
      mctp: serial: cancel tx work on ldisc close
      mctp: serial: enforce fixed MTU
      mctp: serial: remove unnecessary ldisc data check
      mctp: test: fix skb free in test device tx
      mctp: tests: Rename FL_T macro to FL_TO
      mctp: tests: Add key state tests
      mctp: Add helper for address match checking
      mctp: Allow keys matching any local address
      mctp: replace mctp_address_ok with more fine-grained helpers
      mctp: add address validity checking for packet receive
      mctp: serial: Cancel pending work from ndo_uninit handler

Joel Stanley (1):
      ARM: configs: aspeed_g5: Enable MCTP stack

Matt Johnston (15):
      mctp: Allow MCTP on tun devices
      mctp: Set route MTU via netlink
      mctp: Warn if pointer is set for a wrong dev type
      mctp: Avoid leak of mctp_sk_key
      mctp: emit RTM_NEWADDR and RTM_DELADDR
      mctp: test: zero out sockaddr
      mctp: Add SIOCMCTP{ALLOC,DROP}TAG ioctls for tag control
      mctp: make __mctp_dev_get() take a refcount hold
      mctp: Fix incorrect netdev unref for extended addr
      mctp: Fix warnings reported by clang-analyzer
      mctp: Avoid warning if unregister notifies twice
      dt-bindings: net: New binding mctp-i2c-controller
      mctp i2c: MCTP I2C binding driver
      mctp i2c: Fix potential use-after-free
      mctp i2c: Fix hard head TX bounds length check

Tom Rix (1):
      mctp: fix use after free

Xu Wang (1):
      mctp: Remove redundant if statements

Yang Yingliang (1):
      mctp: remove unnecessary check before calling kfree_skb()

Change-Id: I99c4bd0eb9725116052d112f731864add8e2117b
Signed-off-by: Joel Stanley <joel@jms.id.au>

meta-aspeed/recipes-kernel/linux/linux-aspeed_git.bb[diff]

1 file changed

tree: 3ce075ca8710cdc209fd1cec655879ebb0e76850

README.md

OpenBMC

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:

Brad Bishop (chair), IBM
Nancy Yuen, Google
Sai Dasari, Facebook
Terry Duncan, Intel
Sagar Dharia, Microsoft
Samer El-Haj-Mahmoud, Arm

Contact

Mail: openbmc@lists.ozlabs.org https://lists.ozlabs.org/listinfo/openbmc
Discord: https://discord.gg/69Km47zH98