| commit | aad6505c9a5e5980bb88808ebdd1fca98f63ecd8 | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@aj.id.au> | Wed Jun 15 11:44:11 2016 +1000 |
| committer | Andrew Jeffery <andrew@aj.id.au> | Wed Jun 15 11:49:55 2016 +1000 |
| tree | eb66051f584a45ddbb50b65ea0daabb8c0babd37 | |
| parent | b065d2c15a5cd0a2e3e320c176fc19e3b9aabd51 [diff] |
cheatsheet.md: Re-write QEMU invocation example The commandline provided had several issues: * The -dtb option was redundant as we boot with the cuImage, and caused some kernel configuration to be skipped which in turn ended in a kernel panic * -append argument was redundant with respect to the devicetree * The file paths used typically required the user to change up out of the build directory after bitbaking obmc-phosphor-image The patch addresses all of the above. Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
This repository contains documentation for OpenBMC as a whole. There may be component-specific documentation in the repository for each component.
These documents describe how to use OpenBMC, including using the programmatic interfaces to an OpenBMC system.
rest-api.md: Introduction to using the OpenBMC REST API
console.md: Using the host console
host-management.md: Performing host management tasks with OpenBMC
code-update.md: Updating OpenBMC and host platform firmware
These documents contain details on developing OpenBMC code itself
cheatsheet.md: Quick reference for some common development tasks
contributing.md: Guidelines for contributing to OpenBMC
dbus-interfaces.md: Reference for APIs exposed to dbus
kernel-development.md: Reference for common kernel development tasks
The OpenBMC project's aim is to create a highly extensible framework for BMC software and implement for data-center computer systems.
We have a few high-level objectives:
The OpenBMC framework must be extensible, easy to learn, and usable in a variety of programming languages.
Provide a REST API for external management, and allow for "pluggable" interfaces for other types of management interactions.
Provide a remote host console, accessible over the network
Persist network configuration settable from REST interface and host
Provide a robust solution for RTC management, exposed to the host.
Compatible with host firmware implementations for basic IPMI communication between host and BMC
Provide a flexible and hierarchical inventory tracking component
Maintain a sensor database and track thresholds