From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Doug Maxey <dwm@maxeymade.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Christoph Hellwig <hch@infradead.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Albert CC Lee <albertcc@tw.ibm.com>
Subject: Re: PATAPI via libata promise 20275 (was: RFC: moving drivers to a new drivers/ata directory)
Date: Thu, 21 Oct 2004 20:53:34 +0200 [thread overview]
Message-ID: <58cb370e041021115367c80c55@mail.gmail.com> (raw)
In-Reply-To: <200410211704.i9LH4jMR008268@falcon30.maxeymade.com>
ATAPI is working just fine for me (ata_piix) in both PIO/DMA
and thanks to Jeff all my ATAPI work is now in -linus tree. :)
Just enable ATA_ENABLE_ATAPI in <linux/libata.h>.
On Thu, 21 Oct 2004 12:04:45 -0500, Doug Maxey <dwm@maxeymade.com> wrote:
> Continuing down a somewhat related path, what is the outlook for PATAPI
> via libata?
>
> There is a high level of interest to have hotplug controllers for ppc64, and
> the primary (exclusive at this point) application is to drive PATAPI optical.
>
> I know you have indicated that you have some WIP to get there. I would like
> to offer any help to reach that goal.
>
> Would you point me to any code available?
>
> ++doug
next prev parent reply other threads:[~2004-10-21 18:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 4:51 RFC: moving drivers to a new drivers/ata directory Jeff Garzik
2004-10-15 7:46 ` Christoph Hellwig
2004-10-15 17:22 ` Jeff Garzik
2004-10-20 15:34 ` Christoph Hellwig
2004-10-20 15:46 ` Jeff Garzik
2004-10-21 17:04 ` PATAPI via libata promise 20275 (was: RFC: moving drivers to a new drivers/ata directory) Doug Maxey
2004-10-21 17:10 ` PATAPI via libata promise 20275 Jeff Garzik
2004-10-21 18:53 ` Bartlomiej Zolnierkiewicz [this message]
2004-10-15 8:37 ` RFC: moving drivers to a new drivers/ata directory Douglas Gilbert
2004-10-15 15:00 ` Brian King
2004-10-15 17:20 ` Jeff Garzik
2004-10-15 18:32 ` Alan Cox
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=58cb370e041021115367c80c55@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=dwm@maxeymade.com \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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).