|
Revision tags: titanic_53.0, titanic_51.4, titanic_52.1, titanic_51.3, titanic_52.0, titanic_50.16, titanic_51.2, titanic_50.15, titanic_51.1, titanic_51.0, titanic_50.14, titanic_50.13, titanic_50.12, titanic_50.11, titanic_50.10, titanic_50.9, titanic_50.8, titanic_50.7, titanic_50.6, titanic_50.5, titanic_50.4, titanic_50.3, titanic_50.2, titanic_50.1, titanic_50.0 |
|
| #
06e46062 |
| 13-Dec-2005 |
jbeloro <none@none> |
PSARC 2005/662 SIS Compliance for Locator Indicators
PSARC 2005/697 Tamale Data Protocol Extensions for Large Data Transfers
PSARC 2005/698 Seattle/Boston Chassis Serial Number
PSARC 2005/728 Boston/
PSARC 2005/662 SIS Compliance for Locator Indicators
PSARC 2005/697 Tamale Data Protocol Extensions for Large Data Transfers
PSARC 2005/698 Seattle/Boston Chassis Serial Number
PSARC 2005/728 Boston/Seattle PICL
6313684 PICL support for Seattle
6328752 PICL support for Boston
6332630 Chassis serial number support for Seattle/Boston
6333508 Solaris needs to support ALOM's disk-on-chip device
6344008 The fruadm command on Boston & Seattle fails to write to any of the system's fruid proms
6347431 picl envmon doesn't fully support blinking/flashing LED states
6347537 locator(1m) is not SIS-compliant
6360332 Seattle platmod is missing the 'plat_add_mem_unum_label' function
6360506 locator -n fails to activate the system locator on Boston
show more ...
|
| #
7c478bd9 |
| 14-Jun-2005 |
stevel@tonic-gate <none@none> |
OpenSolaris Launch
|