From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: atapi write support? No
Date: Tue, 09 Sep 2003 16:09:51 -0400 [thread overview]
Message-ID: <3F5E338F.2000007@wmich.edu> (raw)
In-Reply-To: <20030909195428.GQ4755@suse.de>
Jens Axboe wrote:
> On Tue, Sep 09 2003, Ed Sweetman wrote:
>
>>Is anyone able to actually use the atapi write support present in the
>>later cdrecord releases? 2.6 can't seem to work with it at all. Is
>
>
> Based on the clues you pass above, noone can help you. What are you
> trying to do and how? What kernel version? What cdrecord version?
There is no other information needed. By use atapi write support i mean
Get it to do anything besides error out reporting that it cant access
the drive. If you can query the drive much less actually write anything
to it using the ATAPI interface than that's more than i've been able to do.
for example cdrecord dev=ATAPI:1,0,0 checkdisk
1,0,0 should conform to secondary channel master as this is how devfs
sets the cdr up too.
kernel version, if you look above it's 2.6, but for the sake of
comparison, test4 or test5 with or without mm patches.
cdrecord version: atapi support was introduced with 2.0 but again, for
the sake of comparison, anything after a13.
>
>>this due to the kernel being broken or cdrecord not being up to date
>>with 2.6 semantics?
>
>
> I'll polish my crystal ball and let you know!
>
next prev parent reply other threads:[~2003-09-09 20:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 19:36 atapi write support? No Ed Sweetman
2003-09-09 19:54 ` Jens Axboe
2003-09-09 20:09 ` Ed Sweetman [this message]
2003-09-09 20:16 ` Jens Axboe
2003-09-09 20:24 ` Markus Plail
2003-09-09 22:04 ` Ed Sweetman
2003-09-10 6:11 ` Markus Plail
2003-09-10 8:33 ` Jens Axboe
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=3F5E338F.2000007@wmich.edu \
--to=ed.sweetman@wmich.edu \
--cc=axboe@suse.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