From: Bill Davidsen <davidsen@tmr.com>
To: Alan Chandler <alan@chandlerfamily.org.uk>
Cc: Jens Axboe <axboe@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: ide-cd problem
Date: Mon, 29 Nov 2004 12:29:36 -0500 [thread overview]
Message-ID: <41AB5C80.10605@tmr.com> (raw)
In-Reply-To: <200411262339.01306.alan@chandlerfamily.org.uk>
Alan Chandler wrote:
> On Tuesday 23 November 2004 21:49, Alan Chandler wrote:
>
>
>>Before, I thought my hardware was a little out of spec - now I think there
>>is something else at play here.
>>
>
>
> Firstly, I think there might be another race condition like the one Alan Cox
> found. I attach a patch below with the fix for that (against 2.6.10-rc2, an
> including Alan's patch) I'm not 100% sure its necessary, but it seems fix a
> variation I have been seeing.
>
> With it in place, and apart from the ongoing issue - see below, I have managed
> to remove the delay in drive_is_ready() altogether without any ill effects.
>
> [my reading of the ATA spec is that 400ns is needed after reading the status
> reg before IRQ is removed, I had wondered whether it would be better to
> record the time here and then check whether we had used up the 400ns just
> before returning from the interrupt state]
The method is sound, I did some industrial control in a previous job and
used a back-to-back timer in a similar way. Just before starting an
operation I checked to see that it wasn't too soon and did a delay if so.
Depending on the path through the code, it may be easier to get right by
just putting in the delay.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2004-11-29 20:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 18:42 ide-cd problem Alan Chandler
2004-11-20 19:47 ` Jens Axboe
2004-11-21 0:53 ` Alan Chandler
2004-11-21 8:56 ` Jens Axboe
2004-11-21 10:25 ` Alan Chandler
2004-11-21 16:13 ` Alan Chandler
2004-11-22 7:52 ` Alan Chandler
2004-11-22 8:01 ` Jens Axboe
2004-11-22 10:30 ` Alan Chandler
2004-11-22 10:51 ` Jens Axboe
2004-11-22 11:29 ` Alan Chandler
2004-11-22 11:31 ` Jens Axboe
2004-11-22 12:53 ` Alan Chandler
2004-11-22 13:02 ` Jens Axboe
2004-11-22 19:19 ` Alan Chandler
2004-11-22 23:48 ` Alan Chandler
2004-11-23 7:13 ` Alan Chandler
2004-11-23 14:51 ` Jens Axboe
2004-11-23 21:49 ` Alan Chandler
2004-11-26 23:39 ` Alan Chandler
2004-11-29 17:29 ` Bill Davidsen [this message]
2004-11-30 8:59 ` Alan Chandler
2004-12-10 21:32 ` ide-cd problem revisited - more brainpower needed Alan Chandler
2004-12-10 23:14 ` Alan Cox
2004-12-12 0:17 ` Alan Chandler
2004-12-12 11:39 ` Alan Cox
2004-12-12 13:34 ` Alan Chandler
2004-12-14 0:20 ` Alan Chandler
2004-12-16 15:56 ` Bill Davidsen
2004-12-17 23:59 ` Alan Chandler
2004-11-24 23:19 ` ide-cd problem Alan Cox
2004-11-25 15:29 ` Jens Axboe
2004-11-25 16:25 ` Alan Cox
2004-11-25 18:12 ` Jens Axboe
2004-11-25 18:45 ` Alan Chandler
2004-11-23 18:34 ` Jeff Garzik
2004-11-23 19:13 ` Jens Axboe
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=41AB5C80.10605@tmr.com \
--to=davidsen@tmr.com \
--cc=alan@chandlerfamily.org.uk \
--cc=axboe@suse.de \
--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