From: Jeff Garzik <jgarzik@pobox.com>
To: "Gaston, Jason D" <jason.d.gaston@intel.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch for Intel Tolapai
Date: Fri, 07 Sep 2007 18:39:15 -0400 [thread overview]
Message-ID: <46E1D313.2060302@pobox.com> (raw)
In-Reply-To: <39B20DF628532344BC7A2692CB6AEE0701B9A4CA@orsmsx420.amr.corp.intel.com>
Gaston, Jason D wrote:
>> -----Original Message-----
>> From: Gaston, Jason D
>> Sent: Friday, August 31, 2007 10:10 AM
>> To: 'Jeff Garzik'
>> Cc: linux-ide@vger.kernel.org; linux-kernel@vger.kernel.org
>> Subject: RE: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch
> for
>> Intel Tolapai
>>
>> This device has both AHCI and RAID modes that use the ahci driver.
> Only
>> the RAID mode DID's are being added as the PCI class code support will
>> cover the AHCI mode. Looking at the Generic, PCI class code support
>> section, it uses "board_ahci". I assumed that they should be the same
> as
>> the generic class code support is working on this platform.
>>
>> Thanks,
>>
>> Jason
>>
>>
>>> -----Original Message-----
>>> From: Jeff Garzik [mailto:jgarzik@pobox.com]
>>> Sent: Friday, August 31, 2007 12:47 AM
>>> To: Gaston, Jason D
>>> Cc: linux-ide@vger.kernel.org; linux-kernel@vger.kernel.org
>>> Subject: Re: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch
> for
>>> Intel Tolapai
>>>
>>> Jason Gaston wrote:
>>>> Resend trying to remove 8-bit characters in the email.
>>>>
>>>> This patch adds the Intel Tolapai RAID controller DID's for SATA
>> support.
>>>> Signed-off-by: Jason Gaston <jason.d.gaston@intel.com>
>>>>
>>>> --- linux-2.6.23-rc4/drivers/ata/ahci.c.orig 2007-08-27
>>> 18:32:35.000000000 -0700
>>>> +++ linux-2.6.23-rc4/drivers/ata/ahci.c 2007-08-28
>> 16:58:11.000000000 -
>>> 0700
>>>> @@ -411,6 +411,8 @@
>>>> { PCI_VDEVICE(INTEL, 0x292f), board_ahci_pi }, /* ICH9M */
>>>> { PCI_VDEVICE(INTEL, 0x294d), board_ahci_pi }, /* ICH9 */
>>>> { PCI_VDEVICE(INTEL, 0x294e), board_ahci_pi }, /* ICH9M */
>>>> + { PCI_VDEVICE(INTEL, 0x502a), board_ahci }, /* Tolapai */
>>>> + { PCI_VDEVICE(INTEL, 0x502b), board_ahci }, /* Tolapai */
>>> Why did you not use board_ahci_pi? Is the AHCI ports-implemented
>>> register unreliable on this platform?
>
> Jeff,
>
> Do I need to change this to board_ahci_pi or is it ok to leave it at
> board_ahci, which will be used by the AHCI class code devices?
You are the one who needs to answer this question ;-)
Most new Intel AHCI have a sane and reliable Ports-Implemented register
value even across reset, unlike earlier ones or some clones. For those,
we use board_ahci_pi.
If PI is not reliable across reset or if BIOS is absent (yes we care
about that case, when we do our own PCI resume for example), then you
should use board_ahci.
Jeff
next prev parent reply other threads:[~2007-09-07 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 4:27 [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch for Intel Tolapai Jason Gaston
2007-08-31 7:47 ` Jeff Garzik
2007-08-31 17:10 ` Gaston, Jason D
2007-09-06 17:27 ` Gaston, Jason D
2007-09-07 22:39 ` Jeff Garzik [this message]
2007-09-07 23:37 ` Gaston, Jason D
2007-09-07 23:57 ` Jeff Garzik
2007-09-08 5:51 ` Tejun Heo
2007-09-20 21:35 ` Jeff Garzik
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=46E1D313.2060302@pobox.com \
--to=jgarzik@pobox.com \
--cc=jason.d.gaston@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).