SiI3114 PCI to Serial ATA Controller
Data Sheet
Silicon Image, Inc.
Table 33. Data FIS
Byte 2
Dword
Byte 3
Byte 1
Byte 0
0
Data FIS Header
1
Sector Data Byte 3
Sector Data Byte 2
Sector Data Byte 1
Sector Data Byte 0
2
Sector Data Byte 7
-
Sector Data Byte 6
-
Sector Data Byte 5
-
Sector Data Byte 4
-
3
...
126
127
128
129
130
Sector Data Byte 507
Sector Data Byte 511
Don't care
Sector Data Byte 506
Sector Data Byte 510
Vendor Specific Byte 1
Vendor Specific Byte 3
-
Sector Data Byte 505
Sector Data Byte 509
Don't care
Sector Data Byte 504
Sector Data Byte 508
Vendor Specific Byte 0
Vendor Specific Byte 2
-
Don't care
Don't care
-
-
...
Last (n is even)
Last (n is odd)
Don't care
Don't care
Vendor Specific Byte n-1
Don't care
Don't care
Don't care
Vendor Specific Byte n-2
Vendor Specific Byte n-1
Note: (The Number of Vendor Specific Bytes is "n" as determined by the Transfer Count in the PIO Setup FIS)
Vendor Specific Command Support
The SiI3114 supports most vendor specific commands that utilize existing protocols.
Silicon Image's Vendor Specific Commands
Silicon Image defines several vendor specific commands (all of which use Expanded Features in 48-bit LBA
addressing) to support vendor specific and reserved commands:
• VS Unlock Vendor Specific: Unlock the host or device to support vendor specific commands.
• VS Unlock Reserved: Unlock the host or device to support reserved commands.
• VS Unlock Individual: Unlock the host or device to support individual vendor specific and reserved
commands.
• VS Lock: Lock the host or device to abort all vendor specific and reserved commands.
• VS Set General Protocol: Determine the General Protocol Code to be used for all subsequent vendor
specific commands (if unlocked via a VS Unlock Vendor Specific command) and reserved commands (if
unlocked via a VS Unlock Reserved command).
• VS Set Command Protocol: Select protocols for individual vendor specific and reserved commands (if
unlocked via a VS Unlock Individual command). A Command Protocol Table shall be maintained.
Potential Conflicts with other Vendor Specific Commands
The commands chosen use Subcommand (Features) code F1h under the SMART command (B0h). While this
code is not expected to be used by device manufacturers, there is always the possibility that it is used. If such
conflict happens, the device manufacturers shall reassign a new code to the conflicting command in order to use
this scheme.
Other Expanded Features Codes
The commands above do not use all Expanded Features Codes. However, all other Expanded Features Codes
under Command Code B0h and Subcommand (Features) Code F1h are reserved as Silicon Image Vendor
Specific commands.
© 2007 Silicon Image, Inc.
93
SiI-DS-0103-D
SILICONIMAGE [ Silicon image ]
