public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcin Dalecki <dalecki@evision.ag>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IDE udma_status = 0x76 and 2.5.30...
Date: Mon, 05 Aug 2002 16:21:06 +0200	[thread overview]
Message-ID: <3D4E89D2.7020408@evision.ag> (raw)
In-Reply-To: 1264DE104D6@vcnet.vc.cvut.cz

Uz.ytkownik Petr Vandrovec napisa?:

> PDC20265 works correctly without setting stop-bit in last descriptor
> for reads, as IDE drive signals no more data, and we stop udma engine
> manually in such case. But for writes PDC20265 prefetches beyond last 
> pointer, finds garbage here (probably descriptor crossing 64KB, or
> odd length or ...), and aborts whole transfer in the middle (about 
> 4 bytes before end of real write, when it tries to prefetch beginning 
> of next sector).

What about inserting a trap pointer there? One which would allow to 
determine "overflows" fast? However I don't see a way to trigger 
something as convenient as a simple page fault here.


  reply	other threads:[~2002-08-05 14:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 14:07 [PATCH] IDE udma_status = 0x76 and 2.5.30 Petr Vandrovec
2002-08-05 14:21 ` Marcin Dalecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-05 20:31 Petr Vandrovec
2002-08-05 21:10 ` Andre Hedrick
2002-08-05 21:19   ` Andre Hedrick
2002-08-05 10:18 Petr Vandrovec
2002-08-05 10:28 ` Marcin Dalecki
2002-08-04 22:25 Petr Vandrovec
2002-08-05  9:33 ` Marcin Dalecki
2002-08-05 20:08 ` Andre Hedrick
2002-08-05 21:42   ` Alan Cox

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=3D4E89D2.7020408@evision.ag \
    --to=dalecki@evision.ag \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    /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