All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@codemonkey.org.uk>
Subject: Re: how to use "ATAPI:" protocol for IDE CD/RWs??
Date: Mon, 21 Jul 2003 16:49:31 +0200	[thread overview]
Message-ID: <20030721144930.GG12516@suse.de> (raw)
In-Reply-To: <20030720222854.GI26422@fs.tum.de>

On Mon, Jul 21 2003, Adrian Bunk wrote:
> On Sun, Jul 20, 2003 at 12:26:53PM +0200, Rudo Thomas wrote:
> > >   are there known problems with trying to access IDE CD/RWs directly
> > > through the IDE drivers, rather than using SCSI emulation?  i've tried
> > > testing cdrecord using the "dev=ATAPI:x,y,z" option, and am having
> > > no luck.
> > 
> > Take a look at
> > http://www.codemonkey.org.uk/post-halloween-2.5.txt
> > 
> > Excerpt:
> > 
> > CD Recording.
> > ~~~~~~~~~~~~
> > - Jens Axboe added the ability to use DMA for writing CDs on
> >   ATAPI devices. Writing CDs should be much faster than it
> >   was in 2.4, and also less prone to buffer underruns and the like.
> > - Updated cdrecord in rpm and tar.gz can be found at
> >   *.kernel.org/pub/linux/kernel/people/axboe/tools/
> >...
> 
> @Dave:
> What about writing "You need cdrecord >= 2.0 for this." instead?

We already cleared this with Joerg some weeks ago, I'm sure the next
version of the post-halloween document will reflect reality. You need
1.11a38 or newer.

-- 
Jens Axboe


  reply	other threads:[~2003-07-21 14:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 10:08 how to use "ATAPI:" protocol for IDE CD/RWs?? Robert P. J. Day
2003-07-20 10:24 ` Markus Plail
2003-07-20 10:30   ` Robert P. J. Day
2003-07-20 10:26 ` Rudo Thomas
2003-07-20 22:28   ` Adrian Bunk
2003-07-21 14:49     ` Jens Axboe [this message]
2003-07-21 20:59       ` Ian Hastie

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=20030721144930.GG12516@suse.de \
    --to=axboe@suse.de \
    --cc=bunk@fs.tum.de \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    /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.