public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Rakhesh Sasidharan <rakhesh@rakhesh.com>
Cc: Alan <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: VCD not readable under 2.6.18
Date: Sat, 09 Dec 2006 14:46:42 -0500	[thread overview]
Message-ID: <457B12A2.7090104@tmr.com> (raw)
In-Reply-To: <20061209172332.2915.qmail@web57808.mail.re3.yahoo.com>

Rakhesh Sasidharan wrote:
> Infact, just inserting a CD is enough. No need for a media player to try and access the files. :)
> 
> The backend must be polling and trying to mount the disc upon insertion. Kernel 2.6.16 and before did that fine, but kernel 2.6.17 and above don't and give error messages. Which explains why downgrading the kernel solves the problem. (If it were a HAL or KDE/ GNOME problem then shouldn't downgrading the kernel *not* help?) Just thinking aloud ... 

I believe the problem is not that the kernel is providing an error, but 
that it is providing an error which is taken as "DIDN'T WORK THIS TIME, 
BUT TRY AGAIN" rather than a permanent error. Asking every 
media-consious application to be rewritten is perhaps not the best 
solution, either return another error, or return what application expect 
(non-error but no data??)

Changes which break a large number of applications are probably ill-advised.
> 
> ----- Original Message ----
> From: S.Çağlar Onur <caglar@pardus.org.tr>
> To: Ismail Donmez <ismail@pardus.org.tr>
> Cc: Alan <alan@lxorguk.ukuu.org.uk>; Rakhesh Sasidharan <rakhesh@rakhesh.com>; rakheshster@yahoo.com; linux-kernel@vger.kernel.org
> Sent: Saturday, December 9, 2006 8:09:05 PM
> Subject: Re: VCD not readable under 2.6.18
> 
> 09 Ara 2006 Cts 16:15 tarihinde, Ismail Donmez şunları yazmıştı: 
>> Well my bet is xine-lib is buggy somehow as I can reproduce this bug with
>> kaffeine ( KDE media player ).
> 
> Same symptoms occur with mplayer also, dmesg flooded with warnings, what about 
> hal or KDE's cdpolling backend?
> 
> Cheers



  reply	other threads:[~2006-12-09 19:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-09 17:23 VCD not readable under 2.6.18 Rakhesh Sasidharan
2006-12-09 19:46 ` Bill Davidsen [this message]
2006-12-10  0:50   ` Alan
2006-12-09 23:19 ` S.Çağlar Onur
2006-12-10  0:44 ` Alan
  -- strict thread matches above, loose matches on Subject: below --
2006-12-12 19:21 Rakhesh Sasidharan
2006-12-11 17:58 Rakhesh Sasidharan
2006-12-10  4:33 Rakhesh Sasidharan
2006-12-10  4:27 Rakhesh Sasidharan
2006-12-09 13:33 Rakhesh Sasidharan
2006-12-09  8:48 Rakhesh Sasidharan
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-10-16 18:53 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
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

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=457B12A2.7090104@tmr.com \
    --to=davidsen@tmr.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rakhesh@rakhesh.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