linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Wayne Sherman <Wayne@SystemDesignWorks.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: AHCI support on Intel chipsets (confusion?)
Date: Sun, 03 Dec 2006 22:34:51 +0900	[thread overview]
Message-ID: <4572D27B.3000909@gmail.com> (raw)
In-Reply-To: <45715381.80206@SystemDesignWorks.com>

Wayne Sherman wrote:
> So, does the kernel source code incorrectly indicate some of these
> chipsets are AHCI compatible?

Not really.  If the controller has PCI ID of 0x27c1, it's an ahci
controller.  Care to post full dmesg and the result of 'lspci -nn'?

-- 
tejun

  parent reply	other threads:[~2006-12-03 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 10:20 AHCI support on Intel chipsets (confusion?) Wayne Sherman
2006-12-02 10:32 ` Leon Woestenberg
2006-12-02 10:48   ` Wayne Sherman
2006-12-02 10:53   ` Wayne Sherman
2006-12-03 13:34 ` Tejun Heo [this message]
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=4572D27B.3000909@gmail.com \
    --to=htejun@gmail.com \
    --cc=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).