From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: wixor <wixorpeek@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VCD not readable under 2.6.18
Date: Tue, 17 Oct 2006 23:38:52 +0100 [thread overview]
Message-ID: <1161124732.5014.20.camel@localhost.localdomain> (raw)
In-Reply-To: <c43b2e150610171116w2d13e47ancbea07c09bd5ffbf@mail.gmail.com>
Ar Maw, 2006-10-17 am 20:16 +0200, ysgrifennodd wixor:
> Hmm.... so this is more like audio CD with separate tracks and no data
> track than like film on DVD? OK then, but how does xine tell kernel
Yes. To make video fit the mpeg video stream is encoded without all the
error correction. There may or may not be multiple tracks, each is a
chapter in the film basically.
> "give me video tracks"? Is there some magic switch_to_video ioctl on
> cdrom devices or what? And should the dd test fail with kernel errors
There are ioctls for getting sectors in non data format (just like for
reading audio bitstreams to play them).
Now where it all gets weirder is that some forms of VCD (especially the
ones for philips short lived interactive stuff) have an ISO file system
on them but where sector numbers in the file system for video blocks
point to blocks that are not 2K data blocks but mpeg blocks that the
file system layer can't handle, so a VCD disk can appear mountable and
the like.
Alan
next prev parent reply other threads:[~2006-10-17 22:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 18:53 VCD not readable under 2.6.18 wixor
2006-10-16 23:12 ` Alan Cox
2006-10-17 18:16 ` wixor
2006-10-17 22:38 ` Alan Cox [this message]
2006-10-17 22:21 ` Prakash Punnoor
2006-10-17 22:45 ` Olivier Galibert
2006-10-19 16:35 ` wixor
2006-10-19 16:42 ` Alan Cox
2006-10-19 17:39 ` wixor
2006-10-20 13:05 ` Alan Cox
2006-10-24 16:06 ` wixor
2006-10-29 19:23 ` S.Çağlar Onur
-- strict thread matches above, loose matches on Subject: below --
2006-12-09 6:06 Rakhesh Sasidharan
2006-12-09 8:14 ` Ismail Donmez
2006-12-09 13:21 ` Alan
2006-12-09 14:15 ` Ismail Donmez
2006-12-09 14:36 ` Alan
2006-12-09 14:31 ` Ismail Donmez
2006-12-09 16:09 ` S.Çağlar Onur
2006-12-09 8:48 Rakhesh Sasidharan
2006-12-09 13:33 Rakhesh Sasidharan
2006-12-09 17:23 Rakhesh Sasidharan
2006-12-09 19:46 ` Bill Davidsen
2006-12-10 0:50 ` Alan
2006-12-09 23:19 ` S.Çağlar Onur
2006-12-10 0:44 ` Alan
2006-12-10 4:27 Rakhesh Sasidharan
2006-12-10 4:33 Rakhesh Sasidharan
2006-12-11 17:58 Rakhesh Sasidharan
2006-12-12 19:21 Rakhesh Sasidharan
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=1161124732.5014.20.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=wixorpeek@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox