From: "Mark Nelson" <mdnelson8@gmail.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: Driver for Promise PDC42819 SATA/SAS controller
Date: Mon, 1 Sep 2008 22:04:23 +1000 [thread overview]
Message-ID: <65a6ef750809010504q6c4e112cse9163733366bfca0@mail.gmail.com> (raw)
In-Reply-To: <18619.54275.742794.192883@harpo.it.uu.se>
On Mon, Sep 1, 2008 at 9:37 PM, Mikael Pettersson <mikpe@it.uu.se> wrote:
> Mark Nelson writes:
> > On Sat, Aug 23, 2008 at 9:59 PM, Mikael Pettersson <mikpe@it.uu.se> wrote:
> > > Mark Nelson writes:
> > > > > > Forgive my ignorance, but does the fact that the T3 controller can also
> > > > > > use SAS disks mean we should be looking for a SCSI driver?
> > > > >
> > > > > Promise lists only this one partial-source driver for the tx4650,
> > > > > and it /is/ a Linux scsi driver.
> > > > >
> > > >
> > > > Oh sorry, I meant to ask should we be looking at an in-kernel
> > > > (or fully open source driver) that is a SCSI driver that we could make
> > > > work with the T3? So maybe my question is actually: does the
> > > > fact that this controller supports SAS disks mean that the
> > > > driver for it should be a scsi driver (rather than an ATA driver)?
> > >
> > > The candidate Linux drivers would be ata/sata_promise, ata/sata_sx4,
> > > block/sx8, and scsi/stex. You tried sata_promise, and from looking
> > > at the PCI IDs I doubt the others are likely to drive the T3.
> > >
> > > If you can find an open-source T3 driver in some other operating
> > > system, like OpenSolaris, Darwin, or some *BSD, then that would be
> > > great.
> > >
> >
> > Okay, so after trying all of the above drivers you suggested (as
> > well as a few other SAS drivers I found) I figured I'd try AHCI.
> >
> > And it actually works!
> >
> > After making the following simple change:
> >
> > --- linux/drivers/ata/ahci.c_orig 2008-09-01 18:42:26.000000000 +1000
> > +++ linux/drivers/ata/ahci.c 2008-09-01 19:41:29.000000000 +1000
> > @@ -542,6 +542,9 @@ static const struct pci_device_id ahci_p
> > { PCI_VDEVICE(MARVELL, 0x6145), board_ahci_mv }, /* 6145 */
> > { PCI_VDEVICE(MARVELL, 0x6121), board_ahci_mv }, /* 6121 */
> >
> > + /* Promise */
> > + { PCI_VDEVICE(PROMISE, 0x3f20), board_ahci }, /* T3 */
> > +
> > /* 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 },
>
> Nice detective work. At least now the chip is usable.
>
> /Mikael
>
Thanks! It still might need a bit of tweaking and input from
the ahci guys but I'm really happy now that I can use those
extra ports.
Mark
prev parent reply other threads:[~2008-09-01 12:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 1:46 Driver for Promise PDC42819 SATA/SAS controller Mark Nelson
2008-08-15 11:10 ` Mikael Pettersson
2008-08-21 12:57 ` Mark Nelson
2008-08-21 13:27 ` Mikael Pettersson
2008-08-22 0:10 ` Mark Nelson
2008-08-22 16:43 ` Mikael Pettersson
2008-08-22 20:57 ` Jeff Garzik
2008-08-22 22:01 ` Mikael Pettersson
2008-08-23 9:23 ` Mark Nelson
2008-08-23 10:19 ` Mikael Pettersson
2008-08-23 10:40 ` Mark Nelson
2008-08-23 11:59 ` Mikael Pettersson
2008-09-01 11:10 ` Mark Nelson
2008-09-01 11:37 ` Mikael Pettersson
2008-09-01 12:04 ` Mark Nelson [this message]
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=65a6ef750809010504q6c4e112cse9163733366bfca0@mail.gmail.com \
--to=mdnelson8@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--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).