From: Mark Lord <lkml@rtr.ca>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: hda: irq timeout: status=0xd0 DMA question
Date: Sun, 26 Feb 2006 15:32:45 -0500 [thread overview]
Message-ID: <4402106D.60605@rtr.ca> (raw)
In-Reply-To: <4401F6BA.5010607@shaw.ca>
Robert Hancock wrote:
> Henrik Persson wrote:
>> Does happen once or twice a year.. Probably something funky with the
>> cabling or some power-related issues.
>>
>> Anyway, I would be happy if the IDE driver would "just not do that". :)
>
> I can see the reasoning where the device just doesn't function properly
> with DMA at all (like on some Compact Flash-to-IDE adapters where the
> card claims to support DMA but the DMA lines aren't wired through in the
> adapter properly). In that case not disabling DMA would render it
> useless. The IDE layer could keep track of whether DMA was previously
> working on that device however, and not disable DMA on reset if it had
> previously been working.
Definitely. Where these things get sticky is in defining "DMA was working".
And keeping track of it separately for reads and writes.
cheers
next prev parent reply other threads:[~2006-02-26 20:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5KtPb-2oP-9@gated-at.bofh.it>
[not found] ` <5Kxzs-7M7-19@gated-at.bofh.it>
[not found] ` <5KxJa-7XQ-31@gated-at.bofh.it>
[not found] ` <5KxT2-8a6-15@gated-at.bofh.it>
[not found] ` <5KyFa-RL-1@gated-at.bofh.it>
2006-02-26 18:43 ` hda: irq timeout: status=0xd0 DMA question Robert Hancock
2006-02-26 18:49 ` Jesper Juhl
2006-02-26 20:32 ` Mark Lord [this message]
2006-02-26 13:08 Nick Warne
2006-02-26 14:09 ` Mark Lord
2006-02-26 14:15 ` Jesper Juhl
2006-02-26 17:01 ` Nick Warne
2006-02-26 17:07 ` Mark Lord
2006-02-26 17:17 ` Jesper Juhl
2006-02-26 17:20 ` Nick Warne
2006-02-26 17:35 ` Jesper Juhl
2006-02-26 18:10 ` Henrik Persson
2006-02-26 21:10 ` Nick Warne
2006-02-27 13:32 ` Mark Lord
2006-02-27 18:32 ` Nick Warne
2006-03-02 10:32 ` Nick Warne
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=4402106D.60605@rtr.ca \
--to=lkml@rtr.ca \
--cc=hancockr@shaw.ca \
--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