|author||Andrew Jeffery <firstname.lastname@example.org>||Wed Aug 04 13:35:31 2021 +0930|
|committer||Patrick Williams <email@example.com>||Fri Aug 13 09:55:12 2021 +0000|
meta-aspeed: socsec: Bump to v0.2.1 Andrew Jeffery (10): resocsec: Style cleanup via autopep8 resocsec: Use env(1) for shebang resocsec: Consistently use single-quotes for strings resocsec: Make signing helper options mutually exclusive resocsec: Add a helper for frobbing the RSA algorithm slug resocsec: Attempt at ergonomic Chain-of-Trust options resocsec: Rename secure-bootloader to secure-bootstrap-image resocsec: Add secure-chained-images subcommand resocsec: Add verify-secure-image subcommand setup: Install resocsec Johnny Huang (43): Merge branch 'develop' into resocsec Merge pull request #7 from amboar/resocsec resocsec: fix typo socsec: add support for ast2605 socsec: remove hexdump module dependcy schema: update otp schema otptool: fix making strap region otptool: fix schema typo readme: add descripton of verify strap: fix "VGA class code" info otptool: fix schema key otptool: fix OTPCFG0 description for 2600A1 socsec: move hexdump to global otptool: add 'print' function for otptool socsec: fix public key exponent otp_info: fix config typo otptool: add AST2600A3 support socsec: add rsa pss padding for AST1030A1 socsec: fix cot public key exponent socsec: Add new test item socsec: Add 2600A3 test item Merge branch 'develop' socsec: add mode2v2aes2 pub and priv test socsec: add ecdsa mode for AST1030A1 socsec: Add ecdsa test item otp_info: remove ast1030 from otp_info otp_info: update schema socsec: update revision id otptool: update schema for manifest id config socsec: fix revision id range. socsec: fix f-strings giving SyntaxError socsec: deprecate the CoT sing function otptool: fix bitarray AttributeError readme: update readme and fix typo otp_info: update otp info tool: add info2sample tool otp_info: Add AST2600A3 otp config otp_info: update and add OTPSTRAP Reserved info otptool: fix otptool print otptool: make image also generate OTPCFG1 tool: add script to generate otp config schema setup: update version number Merge branch 'develop' Change-Id: Ie78aa2c0ddb18d823e1055a67c76967aa9762285 Signed-off-by: Andrew Jeffery <firstname.lastname@example.org>
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.
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
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"
git clone email@example.com:openbmc/openbmc.git cd openbmc
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: centriq2400-rep f0b fp5280g2 gsj hr630 hr855xg2 lanyang mihawk msn neptune nicole olympus olympus-nuvoton on5263m5 p10bmc palmetto qemuarm quanta-q71l romulus s2600wf stardragon4800-rep2 swift tiogapass vesnin witherspoon witherspoon-tacoma yosemitev2 zaius
Once you know the target (e.g. romulus), source the
setup script as follows:
. setup romulus
For evb-ast2500, please use the below command to specify the machine config, because the machine in
meta-aspeed layer is in a BSP layer and does not build the openbmc image.
TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env
Additional details can be found in the docs repository.
The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here
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.
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.
Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.
First, please do a search on the internet. There's a good chance your question has already been asked.
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 In Progress
Features Requested but need help
Dive deeper into OpenBMC by opening the docs repository.
The Technical Steering Committee (TSC) guides the project. Members are: