public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mount -w of dvd+rw etc. in vanilla 2.6
Date: 04 Sep 2003 16:36:02 -0600	[thread overview]
Message-ID: <1062714962.5959.17.camel@lintel> (raw)


> mount -w -t udf works with my dvd-ram ...
> mistakenly sees my dvd+rw as read-only ...

Besides that Andy Polyakov patch for mount -w of dvd+rw, the web has
Jens Axboe patches for mount -w of cd-rw, via the udf faq (Not via the
udftools faq):

http://sourceforge.net/projects/linux-udf/
udf-0.9.7.tar.gz
FAQ
http://w1.894.telia.com/~u89404340/patches/packet/

---

>From these two clues, kindly offline people have identified the Four
fragments of kernel source that cooperate to conclude erroneously that
dvd+rw etc. are not writable:

1)

drivers/scsi/sr.c understands only the CDC_DVD_RAM profile of the seven
standard mmc "writable" device "profile"s, because sr.c neglects to look
beyond the "Capabilities" mode page x2a i.e. does not look beyond the
mmc 1 standard of 1997.  Ansi did not publish an op x46 Get
Configuration standard until the mmc 2 of 1999.

2)

include/scsi/scsi.h does not yet #define GET_CONFIGURATION 0x46.

3)

drivers/cdrom/cdrom.c also understands only CDC_DVD_RAM: cdrom.c
erroneously claims all mmc profiles except CDC_DVD_RAM are not
FMODE_WRITE-able.

4)

include/linux/cdrom.h names only CDC_DVD_RAM.

---

Anyone have an idea of how best to patch this?

I've seen a few linux-2.6.0-test4/ and linux-2.4.22/ alternatives mostly
work.  Anyone interested in evaluating some of them?

Pat LaVarre




                 reply	other threads:[~2003-09-04 22:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1062714962.5959.17.camel@lintel \
    --to=p.lavarre@ieee.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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