From: Tim Fairchild <tim@bcs4me.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: K3b and 2.6.9?
Date: Tue, 31 Aug 2004 20:37:00 +1000 [thread overview]
Message-ID: <200408312037.00994.tim@bcs4me.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408301917360.2295@ppc970.osdl.org>
On Tuesday 31 Aug 2004 12:29, Linus Torvalds wrote:
> Ehh.. This seems to imply that K3b opens the device for _reading_ when it
> wants to burn a CD-ROM. It also implies that K3b only uses the commands
> that are already marked as being "safe for writing", so the kernel command
> list is apparently fine.
On starting k3b seems to use 'safe for reading' commands and 'safe for
writing' command 0x55 (mode_select?) to test the drive function. file->f_mode
is returning with 0x0d during 'safe for writing' command.
growisofs also is returning file->f_mode as 0x0d with any 'safe for writing'
command if I disable the line and allow k3b to run and burn dvd and just
printk the cmd and file->f_mode values ...
I believe FMODE_WRITE is 0x02 tho don't know where that is defined... If this
bit not set does it mean the device is opened for reading? during a burn?
Sorry, I'm very new to this... but do notice that cdrecord returnes 0x0f
which does have the bit set correctly...
tim
next prev parent reply other threads:[~2004-08-31 10:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 0:47 K3b and 2.6.9? Tim Fairchild
2004-08-30 13:07 ` Alan Cox
2004-08-31 1:51 ` Tim Fairchild
2004-08-31 2:29 ` Linus Torvalds
2004-08-31 6:26 ` Frank Steiner
2004-08-31 16:29 ` Linus Torvalds
2004-08-31 10:37 ` Tim Fairchild [this message]
2004-08-31 17:05 ` Linus Torvalds
2004-09-01 8:37 ` Tim Fairchild
2004-08-31 20:16 ` ismail dönmez
2004-08-31 20:33 ` Linus Torvalds
2004-08-31 22:01 ` Tim Fairchild
2004-09-01 8:27 ` Tim Fairchild
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=200408312037.00994.tim@bcs4me.com \
--to=tim@bcs4me.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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