openbmc/entity-manager/README.md

3 Entity manager is a design for managing physical system components, and mapping
14 likely does contain multiple sub-components, but the component itself as a whole
31 of a D-Bus interface definition.
40    platforms and components, such that components interoperate as much as
48    components at runtime. The most common of these, fru-device, is included in
49    the Entity-Manager repo, and scans all available I2C buses for IPMI FRU
51    **[peci-pcie](https://github.com/openbmc/peci-pcie):** A daemon that utilizes
53    **[smbios-mdr](https://github.com/openbmc/smbios-mdr):** A daemon that
73    records to D-Bus.
77    describe. One example of this is dbus-sensors, which contains a suite of
84 reactor when architectures are multi-tiered. An example of this might include a
98    PCIe Add-in-cards.
104 3. Entity manager shall provide data to D-Bus about a particular device such
108    minimal number of changes necessary when new components are detected or no
109    longer detected. Some examples of re-detection events might include host
121    and instead will rely on other D-Bus applications to publish interfaces that
131 entity-manager to produce a Redfish compliant REST API. **intel-ipmi-oem** An
137 1. **[Entity Manager DBus API](https://github.com/openbmc/entity-manager/blob/master/docs/entity_ma…
138 2. **[My First Sensor Example](https://github.com/openbmc/entity-manager/blob/master/docs/my_first_…
139 3. **[Configuration File Schema](https://github.com/openbmc/entity-manager/tree/master/schemas)**
140 4. **[EEPROM address size detection modes](https://github.com/openbmc/entity-manager/tree/master/do…