linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Maurer <dcmaurer1@cox.net>
To: linux-ide@vger.kernel.org
Subject: Intel 5000X ESB2 AHCI PCI Dev ID not recognized by ahci.c (0x2680)
Date: Mon, 18 Sep 2006 12:37:35 -0700	[thread overview]
Message-ID: <200609181237.35209.dcmaurer1@cox.net> (raw)

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


                 reply	other threads:[~2006-09-18 19:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200609181237.35209.dcmaurer1@cox.net \
    --to=dcmaurer1@cox.net \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).