mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Fritzsche" <tf@noto.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Re: Is controlling DVD speeds via SET_STREAMING supported?
Date: Fri, 26 Nov 2004 20:59:50 +0100 (CET)	[thread overview]
Message-ID: <33133.192.168.0.2.1101499190.squirrel@192.168.0.10> (raw)

Hi Jens,

absolute correct! I just tested it with speed = 1 yesterday night
(quick&duty). This is just a code snap to show that it's possible to set
the speed of a DVD drive this way.

You also wrote about the "End LBA" field in your other mail.
I set this to 0xffffffff but you think that this could be a problem if the
device don't have this LBA. The spec only writes this:
"The End LBA field is the last logical block for which the performance
request is being made." So it should be standard conform if we set here a
higher block number. Do you have experience with other (than NEC ND-3500)
drive that don't support this?

Using this high last block number would make sence, because it looks like
this setting is still valid if the media is changed (other end block!?).

Spec:
"The performance setting is persistent and remains until a new descriptor
is sent. The setting only applies to the extent
identified by the Start and End LBA field. Only zero or one performance
extents shall be valid at any time."

What do you think?

I also found out, that the Realtime-Streaming Feature is mandatory for all
kinds of DVD-+R+-RW-RAM drives. So it might be sufficient to simply use
SET STREAMING for DVD drives and SET SPEED for CD-R's. Isn't it?

I will also enhance this tool by setting the RDD flag if the user selects
speed = 0.

Thanks and kind regards,
 Thomas Fritzsche

> I should have read this more closely... You need to fill the speed
fields correctly:
>
> 	unsigned long read_size = 177 * speed;
>
> 	buffer[12] = (read_size >> 24) & 0xff;
> 	buffer[13] = (read_size >> 16) & 0xff;
> 	buffer[14] = (read_size >>  8) & 0xff;
> 	buffer[15] = read_size & 0xff;
>
> Ditto for write size.
>
> --
> Jens Axboe
>
>





             reply	other threads:[~2004-11-26 22:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-26 19:59 Thomas Fritzsche [this message]
2004-11-27  9:54 ` Thomas Fritzsche
2004-11-27 20:57   ` Pasi Savolainen
2004-11-27 21:02     ` Jan Engelhardt
2004-11-27 23:17     ` Thomas Fritzsche
2004-11-28 11:18       ` Pasi Savolainen
2004-11-28 14:25         ` Thomas Fritzsche
2004-11-28 16:52           ` Jens Axboe
2004-11-28 17:49             ` Pasi Savolainen
2004-11-28 16:53               ` Thomas Fritzsche
2004-11-28 18:53               ` Jens Axboe
2004-11-28 21:01                 ` Pasi Savolainen
2004-11-29  6:19                   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2004-11-24 22:16 Thomas Fritzsche
2004-11-25  7:56 ` Jens Axboe
2004-11-25  8:04 ` Jens Axboe
2004-11-25  9:22   ` Thomas Fritzsche

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=33133.192.168.0.2.1101499190.squirrel@192.168.0.10 \
    --to=tf@noto.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

all inboxes | Powered by JetHome®