From a1adb0777e370103ab9f3e7f8788f74975c69897 Mon Sep 17 00:00:00 2001 From: David Cobbley Date: Tue, 21 Nov 2017 15:58:13 -0800 Subject: Get Device ID - JSON 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 --- docs/configuration.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 docs/configuration.md (limited to 'docs') diff --git a/docs/configuration.md b/docs/configuration.md new file mode 100644 index 0000000..61caaf1 --- /dev/null +++ b/docs/configuration.md @@ -0,0 +1,24 @@ +#Device ID Configuration# + +There is a default dev_id.json file provided by +meta-phosphor/common/recipes-phosphor/ipmi/phosphor-ipmi-host.bb + +Any target can override the default json file by providing a +phosphor-ipmi-host.bbappend with an ODM or platform customizable configuration. + +For a specific example, see: +[Witherspoon](https://github.com/openbmc/openbmc/blob/master/ +meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/ +recipes-phosphor/ipmi/phosphor-ipmi-host.bbappend) + +The JSON format for get_device_id: + + {"id": 0, "revision": 0, "addn_dev_support": 0, + "manuf_id": 0, "prod_id": 0, "aux": 0} + + +Each value in this JSON object should be an integer. The file is placed in +/usr/share/ipmi-providers/ by Yocto, and will be parsed upon the first call to +get_device_id. The data is then cached for future use. If you change the data +at runtime, simply restart the service to see the new data fetched by a call to +get_device_id. -- cgit v1.2.1