bitbake: subtree update:c251833d20..d369bfd8e5
Adrian Freihofer (7):
tests/cooker: add a shared bitbake-subprocess test base class
tests/cooker: add a bitbake -b bbappend test
command: fix setConfig coercing bool config values to truthy strings
cooker: add a buildFile mode that runs a single task
tinfoil: add a prepared task runner
tests/cooker: add TinfoilTests for run_prepared_task
fetch2/wget: remove orphaned NamedTemporaryFile in _fetch_index
Alejandro Mery (1):
data: Return a list from exported_vars()
Antonin Godard (3):
doc: bitbake-user-manual-metadata.rst: fix append example
doc: bitbake-user-manual-environment-setup: use pip to install bitbake-setup
default-registry: use core/yocto/monitor-disk-space fragment by default
Chris Laplante (18):
fetch2: get rid of unused FetchMethod.urls property
fetch2/wget: cache SSL context instead of recreating every time
pyproject.toml: remove broken [build-system] section
pyproject.toml: specify min Python version for project
runqueue: Fix pending_hash_index not including taskname
data_smart: use Pattern.search instead of findall, to match comment
runqueue: fix init of RunQueueScheduler.prio_map; add test for 'basic' scheduler
runqueue: use set 'discard' method instead of 'in' followed by 'remove'
build: localize import of bb.progress
__init__.py: add missing import bb.event
cookerdata: cleanup imports
runqueue: fix bad check in process_possible_migrations
runqueue: remove unused attributes/variables
runqueue: remove unused RunQueueExecute.sorted_setscene_tids; declare setscene_tids_generator in __init__
runqueue: remove long-unused RunQueueData get_user_idstring/get_short_user_idstring
runqueue: remove RunQueueExecute.build_stamps2 which is never read
runqueue: clean up dumpsigs polling
runqueue: report memory pressure limit correctly
Francisco Pedraza (1):
asyncrpc: Close the client event loop when the client is collected
Fredrik Svensson (svsvenss) (2):
fetch2/wget: reuse cached HTTPS connections
tests/fetch: report OpenSSL certificate generation errors
Joshua Watt (12):
hashserv: server: Fix formatting
AGENTS.md: Add file
asyncrpc: Add Task Group
asyncrpc: serv: Use Task Group
asyncrpc: serv: Cancel all clients on server stop
hashserv: tests: Improve test logging
hashserv: client: Add asynchronous streaming API
hashserv: server: Add queued streaming API
hashserv: server: Use streaming and queue API for upstream unihash queries
hashserv: server: Use streaming and queue API for upstream exist queries
hashserv: tests: Add more upstream tests
hashserv: tests: Add test for upstream pipelining
Matt Madison (1):
parse/ast: improve error handling for invalid task dependencies
Michal Sieron (1):
hashserv: server: Fix upstream get-unihash miss truncating stream
Peter Kjellerstedt (1):
fetch2/git: Clarify error about missing LFS support
Philip Lorenz (1):
fetch2: Raise on git lfs fetch failures
Quentin Schulz (4):
doc: bitbake-user-manual-metadata: fix missing whitespace around '=' operator
doc/bitbake-user-manual-environment-setup: fix reference to non-existing term
doc/bitbake-user-manual-ref-variables: fix reference to non-existing entry in variable glossary
doc/bitbake-user-manual-environment-setup: cross-reference DL_DIR
Richard Purdie (18):
tests/setup: Drop win32 platform reference
fetch/wget: Handle long filenames correctly
data: Fix expandKeys recursion issue
fetch/__init__: Clean up minor mirror code duplication
fetch2: Drop unneeded checksum check
fetch2: Drop ESTALE error handling
utils: Allow lockfile/unlockfile to take empty names
utils: Add lockfile_to_exclusive
fetch2: Switch to shared locking for read accesses
utils: Fix lockfile_to_exclusive to avoid deadlock
bin/toaster: Remove accidentally added version string
toaster/tests: Add and use wait_until_element_visible()
toaster/orm/lsupdates: Improve error handling
cooker: Clean up collect_bbfiles handling
toaster: Rename wait_until_element_clickable -> wait_until_finder_clickable
toaster/layerdetails: Add id labels to textareas to make tests more robust
tests/selenium_helpers_base: Add wait_until_element_clickable
toaster/tests/layerdetails: Update tests to use labels and scrolling function
Rouven Rastetter (1):
fetch2/wget: checkstatus: Do not try again on 404 status code
Sebastian Muxel (1):
fetch2/gcp: treat GatewayTimeout as fetch failure
Thomas Perrot (2):
fetch/{npm,npmsw}: re-enable fetchers now that checksums come from SRC_URI
tests/fetch: restore and extend npm/npmsw test coverage
Trevor Woerner (1):
doc: continue the eventmask example onto its second line
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I3046ee4d5f55ca3314c19ab5c345a0b8c3311af4
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.
See the Yocto documentation for the latest requirements
sudo apt install git gcc g++ make file wget \ gawk diffstat bzip2 cpio chrpath zstd lz4 bzip2
sudo dnf install git python3 gcc g++ gawk which bzip2 chrpath cpio \ hostname file diffutils diffstat lz4 wget zstd rpcgen patch
git clone https://github.com/openbmc/openbmc 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: ...
A more complete list of supported machines can be found under meta-phosphor/docs.
Once you know the target (e.g. romulus), source the setup script as follows:
. setup romulus
bitbake obmc-phosphor-image
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.
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.
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 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.
This is a common question, particularly regarding boards from popular COTS (commercial off-the-shelf) vendors such as Supermicro and ASRock. You can see the list of supported boards by running . setup (with no further arguments) in the root of the OpenBMC source tree. Most of the platforms supported by OpenBMC are specialized servers operated by companies running large datacenters, but some more generic COTS servers are supported to varying degrees.
If your motherboard is not listed in the output of . setup it is not currently supported. Porting OpenBMC to a new platform is a non-trivial undertaking, ideally done with the assistance of schematics and other documentation from the manufacturer (it is not completely infeasible to take on a porting effort without documentation via reverse engineering, but it is considerably more difficult, and probably involves a greater risk of hardware damage).
However, even if your motherboard is among those listed in the output of . setup, there are two significant caveats to bear in mind. First, not all ports are equally mature -- some platforms are better supported than others, and functionality on some “supported” boards may be fairly limited. Second, support for a motherboard is not the same as support for a complete system -- in particular, fan control is critically dependent on not just the motherboard but also the fans connected to it and the chassis that the board and fans are housed in, both of which can vary dramatically between systems using the same board model. So while you may be able to compile and install an OpenBMC build on your system and get some basic functionality, rough edges (such as your cooling fans running continuously at full throttle) are likely.
See also “Supported Machines”.
Dive deeper into OpenBMC by opening the docs repository.
The Technical Oversight Forum (TOF) guides the technical direction of the project. Members are voted on by community members based on the membership and voting guidelines.