All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Andrew Morton <akpm@zip.com.au>
Cc: benh@kernel.crashing.org, Kristian <kristian.peters@korseby.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [CFT] Bus mastering support for IDE CDROM audio
Date: 28 Jan 2002 10:50:01 -0500	[thread overview]
Message-ID: <1012233006.951.2.camel@psuedomode> (raw)
In-Reply-To: <3C551F18.873EA52E@zip.com.au>
In-Reply-To: <3C550BD4.E9CBE6A@zip.com.au> <3C550BD4.E9CBE6A@zip.com.au> <20020128095136.1298@mailhost.mipsys.com>  <3C551F18.873EA52E@zip.com.au>

I've always been able to get it back to dma for packet by forcing the
drive to sleep mode and then letting the kernel wake it.   I guess I'll
try this 3rd version patch when I get back from class today and see if
that still works.   

hdparm -Y /dev/cdrom    

then go and set dma again with hdparm.   

Although this could just be fickleness of my cdrom.  


On Mon, 2002-01-28 at 04:51, Andrew Morton wrote:
> benh@kernel.crashing.org wrote:
> > 
> > >At no stage does a packet-mode DMA error turn off drive-level
> > >DMA.  This is because some devices seem to perform ordinary
> > >ATA DMA OK, but screw up packet DMA.
> > >
> > >The kernel internally retries the requests when it performs fallback,
> > >so userspace shouldn't see any disruption as the kernel works
> > >out what to do.
> > >
> > >Once the drive has fallen back to single-frame (or PIO mode) for
> > >packet reads, the only way to get it back to a higher level is
> > >a reboot.
> > 
> > Doesn that mean that a bad media (typically a scratched CDROM) will
> > cause the drive to revert to PIO until next reboot ?
> > 
> 
> Nope.  This error handling is specifically for busmastering
> errors, not for media errors.
> 
> I've tested media errors (whiteboard marker scribblings on the
> CD do this nicely).  DMA errors (bad return value from
> HWIF->dmaproc) I can only simulate.
> 
> 
> -



  reply	other threads:[~2002-01-28 15:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25  8:40 [CFT] Bus mastering support for IDE CDROM audio Andrew Morton
2002-01-25 19:21 ` Kevin P. Fleming
2002-01-27  2:13   ` Dan Chen
2002-01-27  3:16   ` Andrew Morton
2002-01-27  6:41     ` Andrew Morton
2002-01-27  9:11       ` Kristian
2002-01-27 10:19         ` Kristian
2002-01-27 19:54           ` Ed Sweetman
2002-01-28  8:29             ` Andrew Morton
2002-01-28  9:51               ` benh
2002-01-28  9:51                 ` Andrew Morton
2002-01-28 15:50                   ` Ed Sweetman [this message]
2002-01-28 17:13                     ` Kristian
2002-01-28 13:51               ` Kristian
2002-01-28 19:21       ` Kevin P. Fleming
2002-01-26  8:43 ` Dan Chen
2002-01-26 12:03 ` Kristian
2002-01-27 21:21 ` Robert Love
2002-01-27 21:25   ` Jens Axboe
2002-01-27 21:36     ` Andrew Morton
2002-01-27 21:40     ` Robert Love

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=1012233006.951.2.camel@psuedomode \
    --to=ed.sweetman@wmich.edu \
    --cc=akpm@zip.com.au \
    --cc=benh@kernel.crashing.org \
    --cc=kristian.peters@korseby.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.