.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SIL_DEV_CONFIG" "9" "09 October 2005" "" ""

.SH NAME
sil_dev_config \- Apply device/host-specific errata fixups
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void sil_dev_config  (struct ata_port * \fIap\fB, struct ata_device * \fIdev\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIap\fB\fR
Port containing device to be examined
.TP
\fB\fIdev\fB\fR
Device to be examined
.SH "DESCRIPTION"
.PP
After the IDENTIFY [PACKET] DEVICE step is complete, and a
device is known to be present, this function is called.
We apply two errata fixups which are specific to Silicon Image,
a Seagate and a Maxtor fixup.
.PP
For certain Seagate devices, we must limit the maximum sectors
to under 8K.
.PP
For certain Maxtor devices, we must not program the drive
beyond udma5.
.PP
Both fixups are unfairly pessimistic.  As soon as I get more
information on these errata, I will create a more exhaustive
list, and apply the fixups to only the specific
devices/hosts/firmwares that need it.
.PP
20040111 - Seagate drives affected by the Mod15Write bug are blacklisted
The Maxtor quirk is in the blacklist, but I'm keeping the original
pessimistic fix for the following reasons...
- There seems to be less info on it, only one device gleaned off the
Windows driver, maybe only one is affected.  More info would be greatly
appreciated.
- But then again UDMA5 is hardly anything to complain about