From: Frediano Ziglio <freddyz77@tin.it>
To: Peter Osterlund <petero2@telia.com>
Cc: axboe@suse.de, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: Packet writing problems
Date: Mon, 16 Aug 2004 21:51:41 +0200 [thread overview]
Message-ID: <1092685901.4255.5.camel@freddy> (raw)
In-Reply-To: <m3657iq4rk.fsf@telia.com>
Il lun, 2004-08-16 alle 21:09, Peter Osterlund ha scritto:
> ...
> > >
> > > DVD+RW
> > > mkudffs /dev/hdc does not works... doing a strace opening /dev/hdc for
> > > read/write open returns EROFS (or similar). I tried with blockdev
> > > --setrw but still same errors...
> >
> > I see two problems. The first problem is that the Mt Rainier detection
> > can succeed when it shouldn't, because it forgets to check that the
> > "GET CONFIGURATION" command returns the MRW feature number.
>
> The second problem is in the dvdrw-support patch in the -mm kernel.
> (This patch is also included in the patch you are using.)
>
> The problem is that some drives fail the "GET CONFIGURATION" command
> when asked to only return 8 bytes. This happens for example on my
> drive, which is identified as:
>
> hdc: HL-DT-ST DVD+RW GCA-4040N, ATAPI CD/DVD-ROM drive
>
> Since the cdrom_mmc3_profile() function already allocates 32 bytes for
> the reply buffer, this patch is enough to make the command succeed on
> my drive.
>
With these two patch both DVD-RW and DVD+RW works !!! Thanks you very much, it's a dream coming true.
It seems that DVD+RW works better (it's faster) with packet device than with direct writing (mounting /dev/hdc).
When I'll get back to work (on September) I'll test your patch with USB 2 device and another DVD writer.
freddy77
next prev parent reply other threads:[~2004-08-16 19:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 15:16 Packet writing problems Frediano Ziglio
2004-08-16 18:50 ` Peter Osterlund
2004-08-16 19:09 ` Peter Osterlund
2004-08-16 19:51 ` Frediano Ziglio [this message]
2004-08-16 19:55 ` Frediano Ziglio
2004-08-17 19:59 ` Peter Osterlund
2004-08-17 20:24 ` Peter Osterlund
2004-08-17 23:31 ` Julien Oster
2004-08-17 23:36 ` Peter Osterlund
2004-08-18 8:25 ` Julien Oster
2004-08-18 8:38 ` Julien Oster
2004-08-18 8:48 ` Julien Oster
[not found] <20040818125719.GA6021@linux-ari.internal>
2004-08-18 17:08 ` Julien Oster
2004-08-19 6:56 ` Alex Riesen
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=1092685901.4255.5.camel@freddy \
--to=freddyz77@tin.it \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.