linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wayne Sherman <Wayne@SystemDesignWorks.com>
To: jgarzik@pobox.com
Cc: linux-ide@vger.kernel.org
Subject: AHCI support on Intel chipsets (confusion?)
Date: Sat, 02 Dec 2006 02:20:49 -0800	[thread overview]
Message-ID: <45715381.80206@SystemDesignWorks.com> (raw)

Jeff Garzik,

First of all, thank you for your work on the SATA implementation for 
Linux.  I am looking forward to using NCQ.  On that topic, I just 
purchased a motherboard thinking I could use SATA NCQ.  I partly based 
my decision on the kernel source code.  It seems to indicate the Intel 
ICH7 is AHCI compatible:

/linux-2.6.19/drivers/ata/ata_piix.c (lines  226-227):

   /* 82801GB/GR/GH (ICH7, identical to ICH6) */
   { 0x8086, 0x27c0, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich6_sata_ahci },

/linux-2.6.19/drivers/ata/ahci.c (starting at line 300):

static const struct pci_device_id ahci_pci_tbl[] = {
/* Intel */
...
   { PCI_VDEVICE(INTEL, 0x27c1), board_ahci }, /* ICH7 */

I am running Fedora Core 5 w/ kernel 2.6.18, but I didn't see any AHCI 
messages in the dmesg output that were described here:

   http://blog.kovyrin.net/2006/08/11/turn-on-ncq-on-ich-linux/

So I did some more searching and found this Intel page:

   http://www.intel.com/support/chipsets/imst/sb/CS-012304.htm

Where it says clearly:

"ICH8, ICH7 and ICH6-based chipsets, as well as ICH5 and ICH5R-based 
chipsets, do not use AHCI."

So, does the kernel source code incorrectly indicate some of these 
chipsets are AHCI compatible?

Thanks,

Wayne Sherman
System Design Works
Las Vegas


             reply	other threads:[~2006-12-02 10:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 10:20 Wayne Sherman [this message]
2006-12-02 10:32 ` AHCI support on Intel chipsets (confusion?) Leon Woestenberg
2006-12-02 10:48   ` Wayne Sherman
2006-12-02 10:53   ` Wayne Sherman
2006-12-03 13:34 ` Tejun Heo
2006-12-03 19:39   ` Wayne Sherman
2006-12-03 20:32     ` Leon Woestenberg

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=45715381.80206@SystemDesignWorks.com \
    --to=wayne@systemdesignworks.com \
    --cc=jgarzik@pobox.com \
    --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).