#
# Copyright (c) 2015, Oracle and/or its affiliates. All rights reserved.
#
#
#    ***WARNING***: CUSTOMERS SHOULD NOT MODIFY THIS FILE.
#
#    This file is named "/platform/i86pc/kernel/drv/rootnex.conf".
#
#    If you are a Solaris customer wanting to 'tune' "rootnex.conf", you
#    should be making changes to "/etc/driver/drv/rootnex.conf". Any changes
#    made to this file may be lost during the next Solaris upgrade.
#
#    In addition to the driver.conf(1M) properties defined in this file
#    below (possibly none), this file effectively serves as a trigger for
#    the Solaris kernel to import and process driver.conf(4) information
#    obtained from ILOM/BIOS via the BIOS ACPI_OEMS_SIG-ACPI_TOPO_SIG table
#    contents. From a customer perspective, this ACPI table driver.conf(4)
#    information only changes when ILOM/BIOS is updated.
#
#    The driver.conf(4) data obtained from this ACPI table is opaque to BIOS
#    (i.e. ASCII text in driver.conf(4) form, which BIOS does not
#    understand). A typical use-case for this ACPI table information is to
#    define 'compatible-derived' platform-specific/hardware-specific
#    driver.conf(4) properties. These property definitions are parsed by
#    the standard kernel driver.conf code, and then end up decorating
#    specific parts of the Solaris device tree. The device tree then gets
#    consumed by an fmd(1M) libtopo enumeration module, and the properties
#    end up being used to generate various FMA aspects of platform-specific
#    hardware.
#
#    For Oracle Solaris developers, this driver.conf(4) file can be used as
#    a temporary playground for the development of platform-specific
#    configuration information before that information is handed off to the
#    platform ILOM/BIOS team for integration into a new ILOM/BIOS release.
#    The intent is that these definitions end up in the ILOM/BIOS
#    ACPI_OEMS_SIG-ACPI_TOPO_SIG table, and only very rarely in the pkg
#    delivered version of this file.