ISA: Industry Standard Architecture
The meaning of this property is as defined in Open Firmware core document [1], as modified by the Generic Names Recommended Practice[7]. The value for nodes described by this specification shall be "8042".
The meaning of this property is as defined in the Open Firmware core document [1]. The value for nodes described by this specification shall be "8042".
The meaning of this property is as defined in Open Firmware, as modified by the Generic Names Recommended Practice [7]. As described in those documents, the entries are a list of device names with which this device is compatible, starting with the name of the device itself and progressing through successively less precise and possibly less functional compatible devices.
The value of this property shall include "chrp,8042"
Additional entries may be supplied, at their appropriate position in the list, to describe devices with which this device is compatible.
The meaning of this property is as defined in the Open Firmware core document [1]. It describes the device's register set. The values which shall be assigned to this property are explained in the ISA/EISA/ISA-PnP binding[3] and the I/O Device Reference[5].
The meaning of this property is as defined in the Interrupt Mapping Recommended Practice [6]. The values assigned to this property are explained in the ISA/EISA/ISA-PnP binding[3] and the I/O Device Reference[5]. This device may have up to two interrupts assigned to it. The components of the array shall correspond with the interrupts assigned to the children of this node such that a child's reg property when used as an index into the array shall yield the appropriate interrupt value for that child.
prop-encoded-array: Integer constant 1, encoded as with encode-int.
The value of "#address-cells" for this node shall be 1.
prop-encoded-array: Integer constant 0, encoded as with encode-int.
The value of "#size-cells" for this node shall be 0 because the children of this node do not consume any physical address space.
The meaning of this property is as defined in Open Firmware core document [1], as modified by the Generic Names Recommended Practice. The value for nodes described by this specification shall be "keyboard" for an ISA keyboard device node, and "mouse" for an ISA mouse device node.
The meaning of this property is as defined in the Open Firmware core document [1]. The value for nodes described by this specification shall be "keyboard" for an ISA keyboard device node, or "mouse" for an ISA mouse device node.
The meaning of this property is as defined in Open Firmware, as modified by the Generic Names Recommended Practice. As described in those documents, the entries are a list of device names with which this device is compatible, starting with the name of the device itself and progressing through successively less precise and possibly less functional compatible devices.
The value of this property shall be "pnpPNP,303" for an ISA keyboard device node.
The value of this property shall be "pnpPNP,f03" for an ISA mouse device node.
Additional entries may be supplied, at their appropriate position in the list, to describe devices with which this device is compatible.
prop-encoded-array: An integer, encoded with encode-int.
The value of this property shall be 0 for a keyboard node and 1 for a mouse node.
For devices which are selected as Open Firmware's "console input device" or "console output device" device, the device shall be initialized appropriately for the device to which it is attached.
Refer to [5] for more information on the state of this device when the client is started.
For devices selected as Open Firmware's "console input device" or "console output device" device, the state should be unmodified from the initial state on client start-up.
Note: If the device is in a different state when the client calls Open Firmware, unpredictable behavior may result if Open Firmware accepts input or generates output. Clients changing the device state should either restore the original state before calling Open Firmware or should avoid using Open Firmware features requiring user interaction. Changing the device state is likely to render Open Firmware unusable for debugging purposes.