From: Rudo Thomas <thomr9am@ss1000.ms.mff.cuni.cz>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: how to use "ATAPI:" protocol for IDE CD/RWs??
Date: Sun, 20 Jul 2003 12:26:53 +0200 [thread overview]
Message-ID: <20030720122653.C22265@ss1000.ms.mff.cuni.cz> (raw)
In-Reply-To: <Pine.LNX.4.53.0307200606120.17848@localhost.localdomain>; from rpjday@mindspring.com on Sun, Jul 20, 2003 at 06:08:30AM -0400
> 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/
- With the above tools, you also no longer need ide-scsi in order to use
an IDE CD writer.
- Ripping audio tracks off of CDs now also uses DMA and should be
notably faster. You can also find an updated cdda2wav at the same location.
- Send good/bad reports of audio extraction with cdda2wav and burning with
the modified cdrecord to Jens Axboe <axboe@suse.de>
- Currently only 'open by device name' works in cdrecord.
cdrecord -dev=/dev/hdX -inq
- More info at http://lwn.net/Articles/13538/ & http://lwn.net/Articles/13160/
Rudo.
next prev parent reply other threads:[~2003-07-20 10:12 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 [this message]
2003-07-20 22:28 ` Adrian Bunk
2003-07-21 14:49 ` Jens Axboe
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=20030720122653.C22265@ss1000.ms.mff.cuni.cz \
--to=thomr9am@ss1000.ms.mff.cuni.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).