PCI-Based System

The banner output is as follows, indicating that it is a PCI-based system by showing "UPA/PCI" in banner

ok banner
Sun Ultra 60 UPA/PCI (UltraSPARC-II 296MHz), No Keyboard
OpenBoot 3.11, 256 MB memory installed, Serial #9241373.
Ethernet address 8:0:20:8d:3:1d, Host ID: 808d031d.

Note that the output of show-devs command shows some PCI- based nodes. Also, PCI-based systems use generic names for devices. On-board network is named "network", and internal disks are named "diskn", n representing the scsi target number for that disk.

Plug in PCI cards with their own FCodePROM may or may not be using generic names. For details on generic names, see Recommended Practices available on homepage for Open Firmware Working Group at: http://playground.sun.com/1275

ok show-devs
/SUNW,UltraSPARC-II@0,0
/counter-timer@1f,1c00
/pci@1f,2000
/pci@1f,4000
/virtual-memory
/memory@0,a0000000
/aliases
/options
/openprom
/chosen
/packages
/pci@1f,4000/scsi@3,1
/pci@1f,4000/scsi@3
/pci@1f,4000/network@1,1
/pci@1f,4000/ebus@1
/pci@1f,4000/scsi@3,1/tape
/pci@1f,4000/scsi@3,1/disk
/pci@1f,4000/scsi@3/tape
/pci@1f,4000/scsi@3/disk
/pci@1f,4000/ebus@1/SUNW,CS4231@14,200000
/pci@1f,4000/ebus@1/flashprom@10,0
/pci@1f,4000/ebus@1/eeprom@14,0
/pci@1f,4000/ebus@1/fdthree@14,3023f0
/pci@1f,4000/ebus@1/ecpp@14,3043bc
/pci@1f,4000/ebus@1/su@14,3062f8
/pci@1f,4000/ebus@1/su@14,3083f8
/pci@1f,4000/ebus@1/se@14,400000
/pci@1f,4000/ebus@1/sc@14,500000
/pci@1f,4000/ebus@1/SUNW,pll@14,504000
/pci@1f,4000/ebus@1/power@14,724000
/pci@1f,4000/ebus@1/auxio@14,726000
/openprom/client-services
/packages/sun-keyboard
/packages/SUNW,builtin-drivers
/packages/disk-label
/packages/obp-tftp
/packages/deblocker
/packages/terminal-emulator 

The following shows the output of the devalias command on the Sun Ultra 30UPA/PCI system:

ok devalias
screen                   /SUNW,ffb@1e,0
net                      /pci@1f,4000/network@1,1
disk                     /pci@1f,4000/scsi@3/disk@0,0
cdrom                    /pci@1f,4000/scsi@3/disk@6,0:f
tape                     /pci@1f,4000/scsi@3/tape@4,0
tape1                    /pci@1f,4000/scsi@3/tape@5,0
tape0                    /pci@1f,4000/scsi@3/tape@4,0
disk6                    /pci@1f,4000/scsi@3/disk@6,0
disk5                    /pci@1f,4000/scsi@3/disk@5,0
disk4                    /pci@1f,4000/scsi@3/disk@4,0
disk3                    /pci@1f,4000/scsi@3/disk@3,0
disk2                    /pci@1f,4000/scsi@3/disk@2,0
disk1                    /pci@1f,4000/scsi@3/disk@1,0
disk0                    /pci@1f,4000/scsi@3/disk@0,0
scsi                     /pci@1f,4000/scsi@3
floppy                   /pci@1f,4000/ebus@1/fdthree
ttyb                     /pci@1f,4000/ebus@1/se:b
ttya                     /pci@1f,4000/ebus@1/se:a
keyboard!                /pci@1f,4000/ebus@1/su@14,3083f8:forcemode
keyboard                 /pci@1f,4000/ebus@1/su@14,3083f8
mouse                    /pci@1f,4000/ebus@1/su@14,3062f8
name                     aliases

When you look at properties for the device node of a PCI device, you will see few properties that are unique to PCI devices and few properties has a different format than that of a SBus device. For example, the output of .properties for a PCI device is:

ok cd /pci@1f,4000/scsi@3
ok .properties
assigned-addresses       81001810 00000000 00000400 00000000 00000100 
                         82001814 00000000 00010000 00000000 00000100 
                         82001818 00000000 00011000 00000000 00001000 
device_type              scsi-2
clock-frequency          02625a00 
reg                      00001800 00000000 00000000 00000000 00000000 
                         01001810 00000000 00000000 00000000 00000100 
                         02001814 00000000 00000000 00000000 00000100 
                         02001818 00000000 00000000 00000000 00001000 
model                    Symbios,53C875
compatible               glm
name                     scsi
devsel-speed             00000001 
class-code               00010000 
interrupts               00000001 
max-latency              00000040 
min-grant                00000011 
revision-id              00000014 
device-id                0000000f 
vendor-id                00001000