From: Christoph Hellwig <hch@lst.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 11/16] PATA driver for Celleb
Date: Fri, 17 Nov 2006 07:48:08 +0100 [thread overview]
Message-ID: <20061117064808.GA15013@lst.de> (raw)
In-Reply-To: <1163634900.5940.290.camel@localhost.localdomain>
On Thu, Nov 16, 2006 at 10:55:00AM +1100, Benjamin Herrenschmidt wrote:
> > This needs to go to linux-ide for review. But IIRC new PATA drivers
> > should use libata these days, not the old ide layer.
>
> While I agree, there are still issues with libata vs. devices that needs
> special IOps. libata allows you to override writing/reading taskfiles,
> but there are cases, specifically in the EH/bus reset code, where it
> still assumes the standard taskfile byte access format for a few things
> and while it's possible to "override" these, that means re-implementing
> a lot of logic in the driver.
>
> I need to sort that out with Jeff one of these days as there is a
> similar problem with the mpc52xx IDE driver.
>
> In the meantime, I reckon it's ok to have a drivers/ide driver for
> 2.6.20
I don't know. And I think we can't make the judgement here, we should
leave it to the IDE maintainers to a proper review and make this
decision, that's why this patch needs to go to linux-ide ASAP.
next prev parent reply other threads:[~2006-11-17 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 9:49 [PATCH 11/16] PATA driver for Celleb Ishizaki Kou
2006-11-15 18:44 ` Christoph Hellwig
2006-11-15 23:55 ` Benjamin Herrenschmidt
2006-11-16 9:42 ` Akira Iguchi
2006-11-17 6:48 ` Christoph Hellwig [this message]
[not found] <200611160939.kAG9dqre027595@toshiba.co.jp>
2006-11-16 11:32 ` Benjamin Herrenschmidt
2006-11-21 7:22 ` Akira Iguchi
[not found] ` <200611210719.kAL7JsGH025487@toshiba.co.jp>
2006-11-21 7:29 ` Benjamin Herrenschmidt
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=20061117064808.GA15013@lst.de \
--to=hch@lst.de \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).