From: Jeff Garzik <jgarzik@pobox.com>
To: andersen@codepoet.org
Cc: Joe Blow <joeblow341@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Promise 20378 + 2.6.0-test10 + libata patch 1
Date: Mon, 22 Mar 2004 21:04:15 -0500 [thread overview]
Message-ID: <405F9B1F.4000403@pobox.com> (raw)
In-Reply-To: <20031202052015.GA28551@codepoet.org>
Erik Andersen wrote:
> On Mon Dec 01, 2003 at 10:04:42PM -0500, Jeff Garzik wrote:
>
>>Joe Blow wrote:
>>
>>>>From: Jeff Garzik <jgarzik@pobox.com>
>>>>
>>>>Nope, libata Promise driver only supports Serial ATA.
>>>
>>>
>>>Bummer. Will it ever support PATA?
>>
>>No plans.
>
>
> What exactly is needed to get got SATA and PATA support
> comparable to the driver provided by promise? Would it be
> possible to adapt the existing promise PATA IDE driver to drive
> the PATA port, while the libata Promise driver handles the SATA
> ports. Or would a new driver be needed?
>
> How would the two drivers share the same PCI device?
It looks like libata pretty much needs to do PATA, in this case and a
couple others. Promise sent me a couple 2037x test cards with a PATA
port on them, so just now need the time... :)
Getting PATA disks working should be very, very easy. Getting ATAPI
devices working requires some libata core hacking, though the ATAPI code
is mostly there already.
Jeff
next prev parent reply other threads:[~2004-03-23 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 2:52 Promise 20378 + 2.6.0-test10 + libata patch 1 Joe Blow
2003-12-02 3:04 ` Jeff Garzik
2003-12-02 5:20 ` Erik Andersen
2004-03-23 2:04 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-03 3:10 Joe Blow
2003-12-03 3:43 ` Erik Andersen
2003-12-02 3:24 Joe Blow
2003-12-02 5:29 ` Paul Misner
2003-11-30 21:11 Joe Blow
2003-12-01 3:22 ` 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=405F9B1F.4000403@pobox.com \
--to=jgarzik@pobox.com \
--cc=andersen@codepoet.org \
--cc=joeblow341@hotmail.com \
--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 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.