From: Jeff Garzik <jgarzik@pobox.com>
To: Doug Maxey <dwm@maxeymade.com>
Cc: 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
Date: Thu, 21 Oct 2004 13:10:39 -0400 [thread overview]
Message-ID: <4177ED8F.7060809@pobox.com> (raw)
In-Reply-To: <200410211704.i9LH4jMR008268@falcon30.maxeymade.com>
Doug Maxey 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?
You should be following linux-ide, and pay attention to any posting like
http://marc.theaimsgroup.com/?t=109782787200002&r=1&w=2&n=4
The latest ATAPI code is currently in the latest -BK snapshot of
upstream, but new development occurs in "libata-dev" queue as described
in the above email link.
Jeff
next prev parent reply other threads:[~2004-10-21 17:10 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 ` Jeff Garzik [this message]
2004-10-21 18:53 ` Bartlomiej Zolnierkiewicz
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=4177ED8F.7060809@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=dwm@maxeymade.com \
--cc=hch@infradead.org \
--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 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.