From: Jeff Garzik <jgarzik@pobox.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Robert Hancock <hancockrwd@gmail.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: Wed, 13 Jan 2010 12:08:42 -0500 [thread overview]
Message-ID: <4B4DFE1A.4000606@pobox.com> (raw)
In-Reply-To: <m3my0i6nou.fsf@intrepid.localdomain>
On 01/13/2010 10:15 AM, Krzysztof Halasa wrote:
> Jeff Garzik<jgarzik@pobox.com> writes:
>
>> Well, two lines of thinking here:
>>
>> * some of lines of Intel chips do not separate AHCI into a separate
>> PCI ID rather legacy IDE interface. When an AHCI interface exists and
>> AHCI/IDE share the same PCI ID, we default to using AHCI. Thus, some
>> of those PCI ID matches in ahci.c's PCI table may not get caught by
>> the generic PCI class match at the end of the table.
>>
>> * the cost carrying redundant PCI IDs seems low, harmless, and
>> potentially helpful.
>
> Also people may use things like this:
>
> diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
> index a3241a1..0616bbb 100644
> --- a/drivers/ata/ahci.c
> +++ b/drivers/ata/ahci.c
> @@ -561,9 +561,11 @@ static const struct pci_device_id ahci_pci_tbl[] = {
> { PCI_VDEVICE(INTEL, 0x3b2c), board_ahci }, /* PCH RAID */
> { PCI_VDEVICE(INTEL, 0x3b2f), board_ahci }, /* PCH AHCI */
>
> +#ifdef DOESNT_WORK_FOR_ME
> /* JMicron 360/1/3/5/6, match class to avoid IDE function */
> { PCI_VENDOR_ID_JMICRON, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,
> PCI_CLASS_STORAGE_SATA_AHCI, 0xffffff, board_ahci_ign_iferr },
> +#endif
>
> /* ATI */
> { PCI_VDEVICE(ATI, 0x4380), board_ahci_sb600 }, /* ATI SB600 */
> @@ -667,9 +669,11 @@ static const struct pci_device_id ahci_pci_tbl[] = {
> /* Promise */
> { PCI_VDEVICE(PROMISE, 0x3f20), board_ahci }, /* PDC42819 */
>
> +#ifdef DOESNT_WORK_FOR_ME
> /* Generic, PCI class code for AHCI */
> { PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,
> PCI_CLASS_STORAGE_SATA_AHCI, 0xffffff, board_ahci },
> +#endif
>
I'm not sure I understand your point. Are there ahci problems with the
generic entries, that remain unresolved?
Jeff
next prev parent reply other threads:[~2010-01-13 17:08 UTC|newest]
Thread overview: 34+ 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-14 0:03 ` Robert Hancock
2010-01-13 15:15 ` Krzysztof Halasa
2010-01-13 17:08 ` Jeff Garzik [this message]
2010-01-13 18:18 ` Krzysztof Halasa
2010-01-13 23:57 ` Robert Hancock
2010-01-13 23:57 ` Robert Hancock
2010-01-14 14:40 ` Krzysztof Halasa
2010-01-15 0:15 ` Robert Hancock
2010-01-15 0:15 ` Robert Hancock
2010-01-15 21:43 ` Krzysztof Halasa
2010-01-16 1:32 ` Robert Hancock
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:11 ` Robert Hancock
2010-01-14 0:42 ` 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-15 0:15 ` Robert Hancock
2010-01-16 3:02 ` Henrique de Moraes Holschuh
2010-01-16 4:57 ` Robert Hancock
2010-01-16 4:57 ` Robert Hancock
2010-01-20 3:21 ` Tejun Heo
2010-01-14 15:40 ` Krzysztof Halasa
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
2010-09-10 23:38 ` 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=4B4DFE1A.4000606@pobox.com \
--to=jgarzik@pobox.com \
--cc=hancockrwd@gmail.com \
--cc=khc@pm.waw.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.