| commit | d665475d14ee0d9ea388a77007f1667df372f85a | [log] [tgz] |
|---|---|---|
| author | Gunnar Mills <gmills@us.ibm.com> | Wed Jul 25 16:15:53 2018 -0500 |
| committer | Gunnar Mills <gmills@us.ibm.com> | Thu Jul 26 13:19:43 2018 -0500 |
| tree | ed53de36f3a94773c89189fee0da8306fdf77025 | |
| parent | 1a8a43836ea99d4607abacc8a7efdc9dd4142b32 [diff] |
Code Update: Fix image filenames "image-initramfs" is no longer built. It was removed here: https://github.com/openbmc/skeleton/commit/62d11c3e0d98e9a3f8908ec934698f90a55435fb Also correct several image filenames and updated some wording. After building a palmetto: ls -l image-* lrwxrwxrwx 2 gmills gmills 54 Jul 26 13:08 image-bmc -> obmc-phosphor-image-palmetto-20180726180322.static.mtd lrwxrwxrwx 2 gmills gmills 45 Jul 26 13:08 image-kernel -> fitImage-obmc-phosphor-initramfs-palmetto.bin lrwxrwxrwx 2 gmills gmills 40 Jul 26 13:08 image-rofs -> obmc-phosphor-image-palmetto.squashfs-xz lrwxrwxrwx 2 gmills gmills 10 Jul 26 13:08 image-rwfs -> rwfs.jffs2 lrwxrwxrwx 2 gmills gmills 10 Jul 26 13:08 image-u-boot -> u-boot.bin Change-Id: Ic7a9530509bd415c4edb0de70e009745a3268432 Signed-off-by: Gunnar Mills <gmills@us.ibm.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: 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
kernel-development.md: Reference for common kernel development tasks
REST-cheatsheet.md: Quick reference for some common curl commands usage.
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