From: Jeff Garzik <jeff@garzik.org>
To: Mark Nelson <mdnelson8@gmail.com>
Cc: linux-ide@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
mikpe@it.uu.se, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] ahci: Add support for Promise PDC42819
Date: Mon, 27 Oct 2008 23:57:32 -0400 [thread overview]
Message-ID: <49068DAC.605@garzik.org> (raw)
In-Reply-To: <65a6ef750810222008o139600e3o8d7c7cf50a4e4ea0@mail.gmail.com>
Mark Nelson wrote:
> Add an appropriate entry for the Promise PDC42819 controller. It has an
> AHCI mode and so far works correctly with board_ahci.
>
> This chip is found on Promise's FastTrak TX2650 (2 port) and TX4650 (4 port)
> software-based RAID cards (for which there is a binary driver, t3sas) and
> can be found on some motherboards, for example the MSI K9A2 Platinum,
> which calls the chip a Promise T3 controller.
>
> Although this controller also supports SAS devices, its default bootup mode
> is AHCI and the binary driver has to do some magic to get the chip into the
> appropriate mode to drive SAS disks.
>
> Seeing as no documentation is provided by Promise, adding this entry to the
> ahci driver allows the controller to be useful to people as a SATA
> controller (with no ill effects on the system if a SAS disk is connected -
> probing of the port just times out with "link online but device
> misclassified"), without having to resort to using the binary driver. Users
> who require SAS or the proprietary software raid can get this functionality
> using the binary driver.
>
> Signed-off-by: Mark Nelson <mdnelson8@gmail.com>
> ---
> drivers/ata/ahci.c | 3 +++
> 1 file changed, 3 insertions(+)
applied
next prev parent reply other threads:[~2008-10-28 3:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 3:08 [PATCH] ahci: Add support for Promise PDC42819 Mark Nelson
2008-10-28 3:57 ` Jeff Garzik [this message]
2008-10-28 5:55 ` Mark Nelson
2008-10-28 6:02 ` Mark Nelson
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=49068DAC.605@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mdnelson8@gmail.com \
--cc=mikpe@it.uu.se \
/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).