display or modify contents of the
eeprom provides an interface for
displaying and changing the contents of the OpenPROM. Without any arguments,
eeprom will list all of the known fields and their
corresponding values. When given the name of a specific field,
eeprom will display that value or set it if the
field name is followed by ‘=’ and a value. Only the superuser
may modify the contents of the OpenPROM.
The options are as follows:
- Commands are taken from stdin and displayed on stdout.
- Use device instead of the default /dev/openprom.
- Display the tree derived from the OpenPROM and exit.
- Be verbose when setting a value.
FIELDS AND VALUES
Since the OpenPROM is designed such that the field names are arbitrary, explaining them here is dubious. Below are field names and values that one is likely to see. NOTE: this list may be incomplete or incorrect due to differences between revisions of the OpenPROM.
- If true, the old EEPROM-style interface will be used while in the monitor, rather than the OpenPROM-style interface.
- A 32-bit integer specifying the number of megabytes of memory to test upon power-up.
- A 64bitx64bit bitmap in Sun Iconedit format. To set the bitmap, give the pathname of the file containing the image. NOTE: this property is not yet supported.
- If true, enables the use of the bitmap stored in oem-logo rather than the default Sun logo.
- A string to use at power-up, rather than the default Sun banner.
- If true, enables the use of the banner stored in oem-banner rather than the default Sun banner.
- A string of five comma separated fields in the format “9600,8,n,1,-”. The first field is the baud rate. The second field is the number of data bits. The third field is the parity; acceptable values for parity are “n” (none), “e” (even), “o” (odd), “m” (mark), and “s” (space). The fourth field is the number of stop bits. The fifth field is the “handshake” field; acceptable values are “-” (none), “h” (RTS/CTS), and “s” (XON/XOFF).
- If true, the system will ignore RTS/DTR.
- If true, the system will ignore carrier detect.
- Similar to ttya-mode, but for ttyb.
- Similar to ttya-rts-dtr-off, but for ttyb.
- Similar to ttya-ignore-cd, but for ttyb.
- Four digits in the format “0123” specifying which order to probe the SBus at power-up. It is unlikely that this value should ever be changed.
- An 8-bit integer specifying the number of columns on the console.
- An 8-bit integer specifying the number of rows on the console.
- Space separated list of device aliases or device paths to boot from, in the given order.
- File to boot. The empty string lets the second-stage boot program ofwboot choose the default.
- If true, the system will boot automatically at power-up.
- If true, the system will reboot upon reset. Otherwise, the system will fall into the monitor.
- One of the strings “keyboard”, “ttya”, or “ttyb” specifying the default console input device.
- One of the strings “screen”, “ttya”, or “ttyb” specifying the default console output device.
- If true, the keys click annoyingly.
- Comma separated list of arguments for booting over RARP or BOOTP/DHCP and TFTP.
- A string in the format “31204567” describing the translation of physical to logical target.
- Similar to sd-targets, but for tapes. The default translation is “45670123”.
- The SCSI ID of the on-board SCSI controller.
- A 7-character string describing a date, such as “25May95”.
- Similar to hardware-revision, describing when the CPU was last updated.
- If true, the system will boot and run in diagnostic mode.
- When set to false, all Ethernet devices will use the same system default MAC address. When true, Ethernet devices which have a unique MAC address will use it rather than the system default MAC address. This option only really affects FCode-based Ethernet devices. On Sparc64, all on-board devices, as well as plug-in hme(4) boards, will respect this setting; other hardware will not.
- the OpenPROM device
The fields and their values are not necessarily well defined on systems with an OpenPROM. Your mileage may vary.
There are a few fields known to exist in some revisions of the OpenPROM that are not yet supported. Most notable are those relating to password protection of the OpenPROM.
The date parser isn't very intelligent.