commit | bba5b1817e89bd63766e2bb91d406130f027fcaf | [log] [tgz] |
---|---|---|
author | Andrew Jeffery <andrew@aj.id.au> | Mon May 09 15:02:07 2016 +0930 |
committer | Andrew Jeffery <andrew@aj.id.au> | Mon May 09 15:10:34 2016 +0930 |
tree | 541a5f65bcdd1ecb93c2f434c549139c7389cfce | |
parent | a72974312446174f382ab424460f3b355fc2874c [diff] |
userguide: Generate userguide.tex to include \tightlist macro Allow xelatex to build userguide.pdf without errors. pandoc injects \tightlist macros into its output files which cause xelatex to choke. By processing the hand-rolled userguide.tex with pandoc the definition is injected and xelatex can build the PDF. 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, easily 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