path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* Correct the formatting of the network commands documentTom Joseph2018-07-241-6/+6
| | | | | | | The ipmitool commands are placed in the code block. Change-Id: I787dff9d6acd77ceaa1c6251b4287c2367212cad Signed-off-by: Tom Joseph <>
* Docs: Add IPMI command cheatsheetRatan Gupta2018-07-171-0/+36
| | | | | | | Adding the network configuration commands Change-Id: I0542e1266d3bf71c813c3d449bb2838f0dc887cf Signed-off-by: Ratan Gupta <>
* Grammar and spelling fixesGunnar Mills2018-04-181-1/+1
| | | | | | | | | | Spelling errors found using A tool to fix common misspellings. This tool is licensed under GNU General Public License, version 2. Some additional grammar and capitalization errors were fixed as well. Change-Id: I700db4e6d7ba52b02374c9c3e84be0af8bd91859 Signed-off-by: Gunnar Mills <>
* Get Device ID - JSONDavid Cobbley2018-01-041-0/+24
| | | | | | | | | | | | | | This reads in all the get device ID parameters via a JSON file in the rootfs. Using a file in the rootfs will give much more flexibility to consumers of openbmc. Each ODM can simply bbappend their dev_id.json with their own specific get device ID info in. Now you can compile in the required info at build time, or modify during run time if needed. It also does not require any additional compilers/scripts to generate a yaml file. Change-Id: I44dfda54fa1762f88973ad709bf7a50bf32e492d Signed-off-by: David Cobbley <>
* Document OpenBMC OEM Extension NumberingPeter Hanson2017-11-301-0/+172
| | | | | | | | Includes table of OpenBMC OEM Extension command codes, and describes message layout of I2C extension. Change-Id: Idafce7959348fca1e072c0bad09b58bf6c6931ab Signed-off-by: Peter Hanson <>
* Implement Network Settings OverrideRatan Gupta2016-09-021-0/+74
We want to implement the network settings override functionality. This is an OEM boot parameter selector, using parameter ID 0x61. The first byte of the parameter data is the same as parameter ID 5 (ie, the valid flag in the top bit). Persistency doesn't matter here, as petitboot will not clear out this setting. The rest of the parameter data is a host network settings description. For other BMC firmware, the BMC just treats this as opaque (the BMC will just return the same data (including that data1 byte), in response to a Get System Boot Option). For OpenBMC, we may want the BMC to know how to construct that data; the spec for that is at: Closes openbmc/openbmc#267 Change-Id: I2af8776718deda97acf90d10504783085ccf7323 Signed-off-by: Ratan Gupta <>
OpenPOWER on IntegriCloud