Message-ID: <4402106D.60605@rtr.ca>
Date: Sun, 26 Feb 2006 15:32:45 -0500
From: Mark Lord <lkml@rtr.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0
MIME-Version: 1.0
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: hda: irq timeout: status=0xd0 DMA question
References: <5KtPb-2oP-9@gated-at.bofh.it> <5Kxzs-7M7-19@gated-at.bofh.it> <5KxJa-7XQ-31@gated-at.bofh.it> <5KxT2-8a6-15@gated-at.bofh.it> <5KyFa-RL-1@gated-at.bofh.it> <4401F6BA.5010607@shaw.ca>
In-Reply-To: <4401F6BA.5010607@shaw.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1094
Lines: 24

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/