public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Mark Nelson <mdnelson8@gmail.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
	linux-ide@vger.kernel.org,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [RFC][PATCH] ahci: Add support for Promise PDC42819
Date: Thu, 04 Sep 2008 09:43:22 -0400	[thread overview]
Message-ID: <48BFE5FA.9090006@garzik.org> (raw)
In-Reply-To: <65a6ef750809040459h3ffe3183nf0b5a35d15ab86e4@mail.gmail.com>

Mark Nelson wrote:
> On Thu, Sep 4, 2008 at 8:37 PM, Jeff Garzik <jeff@garzik.org> wrote:
>> Mark Nelson wrote:
>>> On Tue, Sep 2, 2008 at 10:08 PM, Mikael Pettersson <mikpe@it.uu.se> wrote:
>>>> Mark Nelson writes:
>>>>  > On Tue, Sep 2, 2008 at 9:19 PM, Jeff Garzik <jeff@garzik.org> wrote:
>>>>  > > Mark Nelson wrote:
>>>>  > >>
>>>>  > >> Add an appropriate entry for the Promise PDC42819 controller. It
>>>> has an
>>>>  > >> AHCI mode and seems to work 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.
>>>>  > >>
>>>>  > >> Signed-off-by: Mark Nelson <mdnelson8@gmail.com>
>>>>  > >> ---
>>>>  > >> Apparently this chip also supports SAS disks, will these work with
>>>> the
>>>>  > >> ahci driver (I've only tested with normal desktop SATA disks)?
>>>>  > >
>>>>  > > ahci is definitely SATA-only, so I wonder how they modified AHCI to
>>>> support
>>>>  > > SAS transport...
>>>>  >
>>>>  > That is a good question. From my understanding the controller is a SAS
>>>>  > controller that can drive SATA disks (as I guess all SAS controllers
>>>> can
>>>>  > do...). Could it be that the controller can be setup to act as an AHCI
>>>>  > SATA controller or if the right registers are poked a SAS controller?
>>>>
>>>> Based on how the sata_promise-supported chips work I'd guess that they
>>>> have dual programming interfaces with AHCI for JBOD SATA and a native
>>>> one (perhaps just additional control registers) for SAS and raid.
>>>>
>>> That's interesting; and makes sense. I'm guessing that we won't end up
>>> with an open source driver that can do SAS on these chips then... But
>>> for now at least we can use them as SATA controllers and if Promise
>>> wants to come to the table with specs or datasheets they can in the
>>> future. I'm just happy to be able to use my eSATA ports (and perhaps
>>> the possibility of getting my hard disk off the SB600, although I should
>>> benchmark both controllers before jumping to any conclusions).
>> FWIW, I'll poke my Promise contacts, but they have gone mostly silent in the
>> past year, so don't get your hopes up...
> 
> Thanks Jeff!
> 
> No need for hope - we have ahci now :)

Well, I still think this PCI ID addition leaves open the possibility 
that plugging in a SAS disk could hang the system or similar misbehavior.

	Jeff




  reply	other threads:[~2008-09-04 13:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <65a6ef750809020403i52228319u9e3197e4062941bc@mail.gmail.com>
2008-09-02 11:19 ` [RFC][PATCH] ahci: Add support for Promise PDC42819 Jeff Garzik
2008-09-02 11:53   ` Alan Cox
2008-09-02 12:01     ` Jeff Garzik
2008-09-02 13:57       ` Alan Cox
2008-09-02 19:22         ` Jeff Garzik
2008-09-02 22:18           ` Alan Cox
2008-09-02 22:30           ` Alan Cox
2008-09-02 11:55   ` Mark Nelson
2008-09-02 12:08     ` Mikael Pettersson
2008-09-02 12:21       ` Mark Nelson
2008-09-04 10:37         ` Jeff Garzik
2008-09-04 11:59           ` Mark Nelson
2008-09-04 13:43             ` Jeff Garzik [this message]
2008-09-04 14:27               ` Mikael Pettersson
2008-09-04 14:28               ` Alan Cox
2008-09-05  2:31                 ` Mark Nelson
2008-09-05  2:28               ` Mark Nelson
2008-10-16 11:18               ` 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=48BFE5FA.9090006@garzik.org \
    --to=jeff@garzik.org \
    --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