From: Rahul Karnik <deathdruid@gmail.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: cdrecord dev=ATA cannont scanbus as non-root [u]
Date: Fri, 3 Dec 2004 06:51:57 -0500 [thread overview]
Message-ID: <5b64f7f041203035133c53d10@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0412030834330.26749@yvahk01.tjqt.qr>
On Fri, 3 Dec 2004 08:35:32 +0100 (MET), Jan Engelhardt
<jengelh@linux01.gwdg.de> wrote:
> > Ok, so I am a bit confused here. We basically have 3 ways to use
> >> cdrecord on linux-2.6 without ide-scsi:
> >>
> >> 1) cdrecord dev=/dev/hdx
> >> 2) cdrecord dev=ATA
> >> 3) cdrecord dev=ATAPI
> >>
> >> Now, if I run all three and grep for '^Warning', I get:
>
> Worse, yet, there is no DMA for any of these three :-(
Not true in 2.6. 1 definitely uses DMA now (disregard the damn
warning). And why would anyone use 2 or 3?
-Rahul
next prev parent reply other threads:[~2004-12-03 11:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 21:33 cdrecord dev=ATA cannont scanbus as non-root J.A. Magallon
2004-11-29 21:50 ` Jan Engelhardt
2004-11-29 21:59 ` J.A. Magallon
2004-11-30 6:51 ` Jan Engelhardt
2004-11-30 7:16 ` Jens Axboe
2004-11-30 16:29 ` J.A. Magallon
2004-11-30 17:12 ` J.A. Magallon
2004-11-30 17:37 ` Jan Engelhardt
2004-11-30 17:49 ` J.A. Magallon
2004-11-30 17:56 ` Jan Engelhardt
2004-11-30 18:29 ` J.A. Magallon
2004-12-01 21:16 ` cdrecord dev=ATA cannont scanbus as non-root [u] Martin Schlemmer [c]
2004-12-02 16:23 ` Radoslaw Szkodzinski
2004-12-02 21:50 ` Martin Schlemmer [c]
2004-12-03 7:35 ` Jan Engelhardt
2004-12-03 11:51 ` Rahul Karnik [this message]
2004-12-03 12:06 ` Jan Engelhardt
2004-12-03 12:10 ` Jens Axboe
2004-12-01 21:56 ` cdrecord dev=ATA cannont scanbus as non-root Markus Plail
2004-12-02 8:07 ` Jens Axboe
2004-12-02 12:51 ` J.A. Magallon
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=5b64f7f041203035133c53d10@mail.gmail.com \
--to=deathdruid@gmail.com \
--cc=jengelh@linux01.gwdg.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