From: Martin Dalecki <dalecki@evision-ventures.com>
To: Ken Brownfield <brownfld@irridia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] ServerWorks autodma behavior
Date: Tue, 26 Feb 2002 12:12:46 +0100 [thread overview]
Message-ID: <3C7B6DAE.1090809@evision-ventures.com> (raw)
In-Reply-To: <20020226032629.A930@asooo.flowerfire.com>
Ken Brownfield wrote:
> There wasn't a specific MAINTAINER for this stuff, other than perhaps
> Andre Hedrick by proxy, so I decided it might be best to post this
> directly.
>
> I have a lot of ServerWorks OSB4 IDE hardware, which has the annoyingly
> suboptimal behavior of corrupting filesystems when DMA is active.
> Unfortunately, serverworks.c (in recent 2.4, at least) does not honor
> the CONFIG_IDEDMA_AUTO config option -- it turns dma on only unless
> "ide=nodma" is set on the kernel command line.
>
> Personally, I think the correct behavior is for the subdrivers to honor
> this config value. However, only VIA behaves in this way, and PIIX only
> because of its funky CONFIG_PIIX_TUNING config. This obviates having to
> modify lilo.conf (or similar) on all machines, and having to remember
> to do so, etc etc.
>
> The alternative is that, somewhat unintuitively, the correct behavior is
> for the subdrivers to make their own non-CONFIGurable decisions on DMA.
> In this case, VIA and PIIX should be corrected, I would think.
>
> 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 ;-).
next prev parent reply other threads:[~2002-02-26 11:13 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 [this message]
2002-02-27 1:01 ` Ken Brownfield
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=3C7B6DAE.1090809@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=brownfld@irridia.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