linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Intel 5000X ESB2 AHCI PCI Dev ID not recognized by ahci.c (0x2680)
@ 2006-09-18 19:37 Dave Maurer
  0 siblings, 0 replies; only message in thread
From: Dave Maurer @ 2006-09-18 19:37 UTC (permalink / raw)
  To: linux-ide

I have a Mac Pro which has an Intel 5000X chipset in it.  On boot, the PCI 
Device ID for the ESB2 SATA/AHCI controller is set to 0x2680.  The last three 
bits of the Dev ID are assigned by the fuse bits.  I can't find anywhere in 
the Intel docs for this chipset what the fuse bits mean, or why the bits are 
different across the chipsets that contain ESB2 chips.

Regardless, the ahci.c file only looks for the AHCI on ESB2 chips if the Dev 
ID is 0x2681, 0x2682, or 0x2683.  So, only the ata_piix.c driver picks up the 
0x2680 Dev ID and treats it as the SATA controller in ICH6.  The side effect 
is that only the first 4 SATA ports are detected and probed, and the last 2 
are ignored.

I added an entry in ahci.c to detect ESB2 on the 0x2680 ID, and all is well. I 
made this change to the 2.0 version of the ahci.c fle. Upon boot with the 
change, all SATA ports were detected and enabled correctly.

So I don't know if the simple patch would be just to add the ID to ahci.c, or 
if this would cause problems with other chipsets, (ICH6, ICH7, etc.)

FYI, here's the device list for the ESB2 SATA controller on the Mac Pros.  
This might be common across all 5000X chipsets, might not.

00:1f.1 0101: 8086:269e (rev 09)  -- Legacy IDE controller
00:1f.2 0101: 8086:2680 (rev 09)  -- SATA/AHCI controller


Thanks!
Dave Maurer


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2006-09-18 19:37 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-18 19:37 Intel 5000X ESB2 AHCI PCI Dev ID not recognized by ahci.c (0x2680) Dave Maurer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).