From: Krzysztof Halasa <khc@pm.waw.pl>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Seth Heasley <seth.heasley@intel.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.32.3] ahci: AHCI and RAID mode SATA patch for Intel Cougar Point DeviceIDs
Date: Thu, 14 Jan 2010 16:40:36 +0100 [thread overview]
Message-ID: <m3eilsitjf.fsf@intrepid.localdomain> (raw)
In-Reply-To: <51f3faa71001131611y343ad225n1acc73900fd49894@mail.gmail.com> (Robert Hancock's message of "Wed, 13 Jan 2010 18:11:43 -0600")
Robert Hancock <hancockrwd@gmail.com> writes:
> Well, ata_piix does have a couple of entries that are listed in ahci
> as well, for ICH6 device IDs 0x2652 and 0x2653. For 0x2653 ata_piix
> checks the class code to make sure it's IDE, but for the 0x2652 entry,
> and in both cases in ahci, the class code isn't checked. Deleting the
> specific entries from ahci for those controllers would seemingly
> actually improve the situation, since then ahci wouldn't try and
> attach to those devices when they indicate IDE class. ata_piix should
> also should be checking for IDE class on 0x2652 as well.
Interestingly the ICH6* datasheet says:
2651 is plain ICH6 (not RAID/AHCI capable)
2652 is ICH6R
2553 is ICH6-M
The subclass code is:
for plain ICH6: 01 (IDE controller)
for ICH6R: 04 (RAID controller)
for ICH6-M: 01 (IDE) or 06 (SATA=AHCI)
I think later chips change their subclass depending on
IDE/AHCI/RAID BIOS setting, wasn't it the ICH6R case as well?
Not checking the subclass for ICH6-M in ahci driver may be a bug,
unless ahci can handle the chip in BIOS-set IDE mode. Not checking
ICH6R code (or checking only for RAID) seems right, though.
--
Krzysztof Halasa
next prev parent reply other threads:[~2010-01-14 15:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 1:00 [PATCH 2.6.32.3] ahci: AHCI and RAID mode SATA patch for Intel Cougar Point DeviceIDs Seth Heasley
2010-01-13 4:40 ` Robert Hancock
2010-01-13 11:11 ` Jeff Garzik
2010-01-13 14:59 ` David Milburn
2010-01-13 15:43 ` Heasley, Seth
2010-01-14 0:03 ` Robert Hancock
2010-01-13 15:15 ` Krzysztof Halasa
2010-01-13 17:08 ` Jeff Garzik
2010-01-13 18:18 ` Krzysztof Halasa
2010-01-13 23:57 ` Robert Hancock
2010-01-14 14:40 ` Krzysztof Halasa
2010-01-15 0:15 ` Robert Hancock
2010-01-15 21:43 ` Krzysztof Halasa
2010-01-16 1:32 ` Robert Hancock
2010-01-16 18:02 ` Krzysztof Halasa
2010-01-14 0:11 ` Robert Hancock
2010-01-14 0:42 ` Robert Hancock
2010-01-14 20:11 ` Henrique de Moraes Holschuh
2010-01-15 0:15 ` Robert Hancock
2010-01-16 3:02 ` Henrique de Moraes Holschuh
2010-01-16 4:57 ` Robert Hancock
2010-01-20 3:21 ` Tejun Heo
2010-01-14 15:40 ` Krzysztof Halasa [this message]
2010-01-20 19:28 ` Jeff Garzik
2010-09-09 16:44 ` [PATCH 2.6.35.4] ahci: AHCI and RAID mode SATA patch for Intel Patsburg DeviceIDs Seth Heasley
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=m3eilsitjf.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=hancockrwd@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.heasley@intel.com \
/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).