All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Maarten Lankhorst <m.b.lankhorst@gmail.com>,
	Ben Skeggs <skeggsb@gmail.com>
Cc: mesa-dev@lists.freedesktop.org, nouveau@lists.freedesktop.org
Subject: Re: [PATCH v2] nouveau: Add support for XvMC acceleration
Date: Tue, 13 Sep 2011 15:52:55 +0200	[thread overview]
Message-ID: <20110913135255.GA6051@joi.lan> (raw)
In-Reply-To: <20110910225420.GB30222@joi.lan>

On Sun, Sep 11, 2011 at 12:54:20AM +0200, Marcin Slusarz wrote:
> On Sat, Sep 10, 2011 at 06:59:39PM +0200, Maarten Lankhorst wrote:
> > Hey ★,
> > 
> > On 09/10/2011 06:28 PM, ★ Emeric wrote:
> > > Hi Maarten,
> > > I tried the v2 patch with my good old geforce 8600M GS, and it worked well.
> > > The CPU usage seems a little higher than usual, I'd said 60% instead of 40%
> > > for a 720p video, but I'll try with a higher bitrate video and without
> > > building with debug parameters to see if I can found a performance gain.
> > > The only problem is that I cannot seek through the video without an segfault
> > > on that error "X11 error: BadAccess (attempt to access private resource
> > > denied)", I attached a gdb backtrace. It appears to be related to the
> > > drawing of the mplayer OSD.
> > >
> > That's either a bug in mplayer or in the state tracker. What's oy and ox
> > set to at the time of the crash? and where does xvimage->data point to :)
> > 
> This is a bug in xf86-video-nouveau actually, and it leads to memory corruption
> in mplayer.
> 
> Patch below fixes it, but OSD still doesn't work.
> 

With commit f626d99edf17a1d3203b257f6fe6993229ea6866 in mesa OSD in mplayer
works (Yeah! ;). I've submitted patch for mplayer to disable OSD instead of
crashing.

Ben, can you review and push patch in the previous mail? (xv: support AI44/IA44)
Thanks.

Marcin
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

  reply	other threads:[~2011-09-13 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4E6B180B.1070401@gmail.com>
     [not found] ` <CAMmP6nczOaGwXbuaNEc-nrTw7kvGdjOr-6+qbWTMqm9s_UkpMA@mail.gmail.com>
     [not found]   ` <4E6B977B.8040402@gmail.com>
2011-09-10 22:54     ` [PATCH v2] nouveau: Add support for XvMC acceleration Marcin Slusarz
2011-09-13 13:52       ` Marcin Slusarz [this message]
     [not found]         ` <20110913135255.GA6051-OI9uyE9O0yo@public.gmane.org>
2011-10-08 17:43           ` [PATCH] xv: add support for AI44/IA44 Marcin Slusarz

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=20110913135255.GA6051@joi.lan \
    --to=marcin.slusarz@gmail.com \
    --cc=m.b.lankhorst@gmail.com \
    --cc=mesa-dev@lists.freedesktop.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=skeggsb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.