From: Ken Brownfield <brownfld@irridia.com>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] ServerWorks autodma behavior
Date: Tue, 26 Feb 2002 19:01:49 -0600 [thread overview]
Message-ID: <20020226190149.B16048@asooo.flowerfire.com> (raw)
In-Reply-To: <20020226032629.A930@asooo.flowerfire.com> <3C7B6DAE.1090809@evision-ventures.com>
In-Reply-To: <3C7B6DAE.1090809@evision-ventures.com>; from dalecki@evision-ventures.com on Tue, Feb 26, 2002 at 12:12:46PM +0100
On Tue, Feb 26, 2002 at 12:12:46PM +0100, Martin Dalecki wrote:
| Ken Brownfield wrote:
[...]
| > In any case, I've appended the patch I'm using to be able to turn off
| > auto-DMA at config-time rather than run-time for ServerWorks. One
| > alternative is to shed this code altogether, since ide-pci.c seems to
| > set a rational default.
|
| I think (not 100% becouse not re-checked against the code),
| you could just have removed the lines
|
| if (!noautodma)
| hwif->autodma = 1;
|
| and all should be well ;-).
Yes, and that's what I found as well. That was my first patch until I
noticed the AUTO check in the VIA driver around this same code.
That being said, which of these solutions is worthy of going into the
kernel (if any) and should that decision be applied to the other IDE
drivers?
I feel like I'm okay with my own little patchbase, but this seems like a
useful type of change to make for everyone and all drivers in 2.4 (and
2.5 if it's even still applicable). And it's just dirt simple enough
for me to do it. ;)
Thanks,
--
Ken.
brownfld@irridia.com
next prev parent reply other threads:[~2002-02-27 1:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 9:26 [PATCH][RFC] ServerWorks autodma behavior Ken Brownfield
2002-02-26 9:52 ` Alan Cox
2002-02-26 9:37 ` Andre Hedrick
2002-02-26 10:27 ` Ken Brownfield
2002-02-26 10:50 ` Andre Hedrick
2002-02-26 19:14 ` Gunther Mayer
2002-02-26 10:19 ` Ken Brownfield
2002-02-26 11:12 ` Martin Dalecki
2002-02-27 1:01 ` Ken Brownfield [this message]
2002-02-27 10:21 ` Martin Dalecki
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=20020226190149.B16048@asooo.flowerfire.com \
--to=brownfld@irridia.com \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@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