This automatic case seems minor binding to remove two drivers that only
existed on the original Sun Ultra-1 platform, and so are no longer useful
in the context of Solaris.Next/OpenSolaris.
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2010 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
EOF esp and dma
1.2. Name of Document Author/Supplier:
Author: Garrett D'Amore
1.3 Date of This Document:
15 January, 2010
4. Technical Description
EOF of esp and dma drivers
----------------------------
The esp driver was used to support legacy sbus SCSI adapters
found on many sun4m systems. The only sun4u system that I've
been able to determine it was found on was the Sun Ultra 1, although
it seems to have been on some *very* old sbus adapers.. (The
Sun Ultra 2 shipped with the "fas" driver which was capable of
20 MB/sec.) The "esp" hardware is ancient Emulex esp100, esp100A,
esp236, fas101, and fas236, supporting only 10 MB/sec SCSI-2. While
perhaps considered advanced for their day, they are very far past
their peak. They also were not capable of doing bus mastering
on their own, but relied on an external part to perform this function
for them.
Note that the Sun Ultra-1 systems that shipped with this on the
motherboard have long since been EOF'd. The Ultra-2 did *not* use
this part, but instead used a "newer" part supported by the "fas"
driver.
We'd like to remove the "esp" driver from the next minor release of
Solaris.
At the same time, the "dma" driver is used to support a dma gate array
for this device. There are no other devices which rely on this driver.
We'd like to eliminate the "dma" driver from the next minor release of Solaris
as well, since it will have no use once the "esp" driver is removed.
(Note that the "dma" driver appears to be the sole consumer of the
ddi_dev_affinity() Consolidation Private interface, and we would like
to remove that interface, and remove the underpinning DDI_CTLOPS_AFFINITY
support from the nexus drivers, but we will undertake that as a separate
effort in a future case to follow this one.)
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
ON
6.5. ARC review type: Automatic
6.6. ARC Exposure: open
