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: Thu, 19 Oct 2006 17:42:58 +0100 [thread overview]
Message-ID: <1161276178.17335.100.camel@localhost.localdomain> (raw)
In-Reply-To: <c43b2e150610190935tefd11eev510c7dee36c15a51@mail.gmail.com>
Ar Iau, 2006-10-19 am 18:35 +0200, ysgrifennodd wixor:
> OK, but this is still mountable only from windows....... Is this ISO
> filesystem hidden somewhere, or what? And that still does not explain
It isn't hidden it should be in the first session
> errors from xine, and the 8 megs that i actually can read using dd.
> All after all - even if this disc would contain totally unsupported
> tracks, with absolutly weird data, kernel should recognize it and
> report something like:
The different types aren't per track but per sector.
> this just another hell-knows-what thing, the kernel implementation is
> ok, and this is only some m$-dontated extension that prevents us from
> accessing this disc? Even if it is, shouldn't it be implemented if it
> is possible?
Actually all the VCD stuff is a mix of the Chinese government and
Philips. The specs are available although pricy.
The kernel provides the infrastructure for arbitary CD handling, but
provides only the file system support in kernel. It can't (and doesn't
appear to need to) handle VCD in kernel it provides the tools to Xine
and friends instead.
Alan
next prev parent reply other threads:[~2006-10-19 16:40 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
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 [this message]
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=1161276178.17335.100.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