| commit | d4f5ef794a73c450bd7e5232e3cef975054501de | [log] [tgz] |
|---|---|---|
| author | Lei YU <mine260309@gmail.com> | Thu Aug 10 15:56:45 2017 +0800 |
| committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Mon Oct 16 09:23:32 2017 -0400 |
| tree | db15d97a27770bb4875fb415cbe9a07a60e3cae7 | |
| parent | dce347440e4307aa8ff237d67caee33246103708 [diff] |
sensor-architecture.md: Fix broken links Several links are broken because they were in different lines. Replace all inline-style links with reference-style ones and fix the broken links. Change-Id: Ia3266ebb83f275a3e25affac4ed88283892a1a5b Signed-off-by: Lei YU <mine260309@gmail.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
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 D-Bus
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