From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sl82c105 driver update
Date: 11 Jan 2003 23:44:15 +0100 [thread overview]
Message-ID: <1042325055.525.153.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <20030111223231.B21505@flint.arm.linux.org.uk>
On Sat, 2003-01-11 at 23:32, Russell King wrote:
> On Sat, Jan 11, 2003 at 05:33:19PM +0100, Benjamin Herrenschmidt wrote:
> > Enclosed is an update to the sl82c105 driver against 2.4.21-pre3, I'll
> > produce a 2.5 version once this is accepted by Alan.
>
> Its still broken - if it uses DMA, the ide core will call ide_dma_on,
> which will call config_for_dma(), which will call ide_config_drive_speed,
> which will then call ide_dma_on, etc.
>
> Sorry, I don't have a solution off hand for this. I just wish that
> the IDE core didn't change in these incompatible ways during a stable
> kernel release.
No this problem is not here, at least not in 2.4, I did test it ;)
ide_config_drive_speed will call ide_dma_host_on, not ide_dma_on.
Note that I think sl82c105 and ide-pmac are the only ones to redo the
DMA config on ide_dma_on. Most chipsets only do it on ide_dma_check, but
I chosed to do it in ide_dma_on too mostly because I found no way to
re-trigger ide_dma_check from hdparm (well, this might have changed
since, I have to dbl check).
Ben.
next prev parent reply other threads:[~2003-01-11 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 16:33 Benjamin Herrenschmidt
2003-01-11 19:46 ` Benjamin Herrenschmidt
2003-01-11 22:32 ` Russell King
2003-01-11 22:44 ` Benjamin Herrenschmidt [this message]
2003-01-11 22:48 ` Vojtech Pavlik
2003-01-11 23:12 ` Benjamin Herrenschmidt
2003-01-12 1:54 ` Kurt Garloff
2003-01-12 9:07 ` Vojtech Pavlik
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=1042325055.525.153.camel@zion.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®