Linux Hotplug development
 help / color / mirror / Atom feed
From: Matthew Dharm <mdharm-usb@one-eyed-alien.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: What variables are important when a cdrom is in or out?
Date: Wed, 21 Jul 2010 21:02:24 +0000	[thread overview]
Message-ID: <20100721210224.GA25467@one-eyed-alien.net> (raw)
In-Reply-To: <AANLkTilWvuVVCWFvw33OjfmFhqGeazobCqIRoQp-Mgee@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]

On Wed, Jul 21, 2010 at 08:38:53AM +0200, Kay Sievers wrote:
> On Wed, Jul 21, 2010 at 00:25, Stef Bon <stefbon@gmail.com> wrote:
> > ID_CDROM_MEDIA_TRACK_COUNT equal to 18,
> > and ID_CDROM_MEDIA_TRACK_COUNT_AUDIO also 18. Does this mean that
> > there is also an
> > ID_CDROM_MEDIA_TRACK_COUNT_VIDEO??
> 
> Seems, you have 18 tracks, and 18 of them are audio. There seems nothing else.
> 
> And video is usually DVD and this would be on a mountable UDF
> filesystem. There is no real native video track like audio.

It is possible, however, to mix audio tracks and data tracks on the same
disc.  It's really rare, but it can be done.  I would guess that is why you
get a "whole disk" track count and an "audio" track count.

Matt

-- 
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
Maintainer, Linux USB Mass Storage Driver

C:  They kicked your ass, didn't they?
S:  They were cheating!
					-- The Chief and Stef
User Friendly, 11/19/1997

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2010-07-21 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 21:36 What variables are important when a cdrom is in or out? Stef Bon
2010-07-20 22:03 ` Kay Sievers
2010-07-20 22:25 ` Stef Bon
2010-07-21  6:38 ` Kay Sievers
2010-07-21 21:02 ` Matthew Dharm [this message]

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=20100721210224.GA25467@one-eyed-alien.net \
    --to=mdharm-usb@one-eyed-alien.net \
    --cc=linux-hotplug@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