public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Prakash Punnoor <prakash@punnoor.de>
To: "Alexander E. Patrakov" <patrakov@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: MPlayer broken under 2.6.15-rc7-rt1?
Date: Sun, 1 Jan 2006 18:50:28 +0100	[thread overview]
Message-ID: <200601011850.29155.prakash@punnoor.de> (raw)
In-Reply-To: <43B7E576.6000004@gmail.com>

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

Am Sonntag Januar 1 2006 15:21 schrieb Alexander E. Patrakov:
> Arjan van de Ven wrote:
> > What you have here is a bit of a gray area; you're using one of the
> > maybe-illegal binary modules that has a really long history of
> > introducing bugs that, just from the oops, may appear unrelated to this
> > module, and you can't reproduce it without. Just not because the bug
> > won't happen, but because you state that the application that triggers
> > it won't run without it.
>
> Wrong. The "nv" driver supports xvideo, and does this better than the
> official "nvidia" driver. When I had a GeForce 2 MX 200 (now this card
> is dead), my computer was was fast enough to play DVDs with
> deinterlacing with the "nv" driver, but not with "nvidia". Probably due
> to improper MTRR setup done by the "nvidia" driver.

It depends on what you call "better". If you want to watch HD resolution 
videos w/o stutters, you need the Nvidia one, as the nv one just wastes CPU 
cycles.

-- 
(°=                 =°)
//\ Prakash Punnoor /\\
V_/                 \_V

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

  reply	other threads:[~2006-01-01 17:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-31 18:29 MPlayer broken under 2.6.15-rc7-rt1? Bradley Reed
2005-12-31 18:47 ` Alistair John Strachan
2005-12-31 18:59   ` Bradley Reed
2005-12-31 19:14     ` Alistair John Strachan
2005-12-31 19:51 ` Steven Rostedt
2005-12-31 20:07   ` Bradley Reed
2005-12-31 20:33     ` Steven Rostedt
2005-12-31 20:58   ` Jan Engelhardt
2005-12-31 22:46     ` RTC broken under 2.6.15-rc7-rt1 (was: Re: MPlayer broken under 2.6.15-rc7-rt1?) Steven Rostedt
2005-12-31 23:22       ` Bradley Reed
2006-01-01  0:04         ` Steven Rostedt
2006-01-01  9:14 ` MPlayer broken under 2.6.15-rc7-rt1? Arjan van de Ven
2006-01-01  9:51   ` Bradley Reed
2006-01-01 11:26     ` Arjan van de Ven
2006-01-01 12:12       ` jerome lacoste
2006-01-01 12:25         ` Arjan van de Ven
2006-01-02  9:57           ` [OT] " jerome lacoste
2006-01-01 13:28         ` Arjan van de Ven
2006-01-01 14:21       ` Alexander E. Patrakov
2006-01-01 17:50         ` Prakash Punnoor [this message]
2006-01-01 11:50     ` Adrian Bunk
     [not found]       ` <20060101145402.0c6292bb@galactus.example.org>
2006-01-01 13:16         ` Adrian Bunk
2006-01-01 13:25           ` Arjan van de Ven
2006-01-01 13:41     ` Steven Rostedt
2006-01-01 15:21     ` Jan Engelhardt
2006-01-01 15:24       ` Jan Engelhardt
2006-01-01 14:31   ` Alistair John Strachan
2006-01-01 18:57     ` Lee Revell
2006-01-01 21:33       ` Keith Owens
2006-01-01 22:57         ` Alistair John Strachan
  -- strict thread matches above, loose matches on Subject: below --
2005-12-31 18:18 Bradley Reed
2005-12-31 19:09 ` Mark Knecht

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=200601011850.29155.prakash@punnoor.de \
    --to=prakash@punnoor.de \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrakov@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