From: Paul Mundt <lethal@linux-sh.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: B.Zolnierkiewicz@elka.pw.edu.pl, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, rmk@arm.linux.org.uk, gregkh@suse.de,
ysato@users.sourceforge.jp
Subject: Re: [PATCH] Generic platform device IDE driver
Date: Thu, 5 Oct 2006 05:05:01 +0900 [thread overview]
Message-ID: <20061004200501.GB6664@localhost.Internal.Linux-SH.ORG> (raw)
In-Reply-To: <1159962084.25772.14.camel@localhost.localdomain>
On Wed, Oct 04, 2006 at 12:41:24PM +0100, Alan Cox wrote:
> Ar Mer, 2006-10-04 am 16:45 +0900, ysgrifennodd Paul Mundt:
> > This is intended purely for the simple NO_DMA ide_generic case.. nothing
> > complicated.
> >
> > What do people think about this, is there a better way to do this?
>
> drivers/ide is going away over time.
That was the impression I got.
> I think the concept is nice and it's sort of reflected in the libata
> VLB drivers. I think it would be a very good way to get good platform
> drivers for libata for the embedded platforms.
>
Ok, I wasn't sure if libata was intended for anything outside of the
SATA case (especially non-PCI), but if that's the way to go, I'll look
at hacking something up under libata.
> Moving the existing drivers/ide stuff to a new drivers/ide variant is
> wasted work however.
>
That's what I figured, thanks for clearing it up.
next prev parent reply other threads:[~2006-10-04 12:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 7:45 [PATCH] Generic platform device IDE driver Paul Mundt
2006-10-04 11:30 ` girish
2006-10-04 20:02 ` Paul Mundt
2006-10-04 12:25 ` girish
2006-10-04 11:41 ` Alan Cox
2006-10-04 20:05 ` Paul Mundt [this message]
2006-10-04 14:38 ` Alan Cox
2006-10-05 9:16 ` Paul Mundt
2006-10-11 12:50 ` Matthias Fuchs
2006-10-12 6:13 ` Paul Mundt
2006-10-13 7:52 ` Russell King
2006-10-13 12:28 ` Paul Mundt
2006-10-13 12:46 ` 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=20061004200501.GB6664@localhost.Internal.Linux-SH.ORG \
--to=lethal@linux-sh.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=ysato@users.sourceforge.jp \
/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.