From: Chris Wilson <chris@chris-wilson.co.uk>
To: Clemens Eisserer <linuxhippy@gmail.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [ANNOUNCE] xf86-video-intel 2.11.901
Date: Tue, 15 Jun 2010 22:40:58 +0100 [thread overview]
Message-ID: <89kc63$h60g7r@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <AANLkTilRurGmlJGOa8OJfDshXUatUpx_71oqJVaFsD2q@mail.gmail.com>
On Tue, 15 Jun 2010 23:03:27 +0200, Clemens Eisserer <linuxhippy@gmail.com> wrote:
> Hi Chris,
>
> > Vasily, Clemens can you both try reverting f74b3f82 on top of 2.11.901
> > and seeing if that fixes the corruption for you. It did not seem to make
> > a difference here...
>
> Sorry if that sounds stupid, but how can I do that?
Starting from scratch:
$ git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel.git
$ cd xf86-video-intel
$ git checkout 2.11.901
$ git revert f74b3f82
Build and install as usual.
> Thanks Clemens
>
> PS: Saw you experimented with shader based trapezoid rasterization.
> just to be curious, what were the results so far?
Give-or-take that it is dubious that we can do a simple coverage based
accumulation of subpixels trapezoids within the specification of
PolyModeImprecise, benchmarking shows a small performance win for most
cairo traces [the improvements matching the elimination of
pixman_image_rasterize_trapezoid() and co], but in a few cases it can be
twice as slow. So I think it is back to a span renderer -- even if I just
trade GPU time for CPU time, that should be a win for application
performance.
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-06-15 21:41 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 0:39 [ANNOUNCE] xf86-video-intel 2.11.901 Carl Worth
2010-06-15 9:18 ` Julien Cristau
2010-06-15 16:46 ` Carl Worth
2010-06-15 16:51 ` Julien Cristau
2010-06-15 17:16 ` Sergio Monteiro Basto
2010-06-15 17:31 ` Julien Cristau
2010-06-15 17:46 ` Sergio Monteiro Basto
2010-06-15 14:05 ` Marc Deop i Argemí
2010-06-15 14:18 ` Julien Cristau
2010-06-15 15:02 ` Marc Deop i Argemí
2010-06-15 16:47 ` Carl Worth
2010-06-15 17:12 ` Marc Deop i Argemí
2010-06-15 21:23 ` Carl Worth
2010-06-16 8:45 ` Marc Deop i Argemí
2010-06-16 13:10 ` Marc Deop i Argemí
2010-06-16 13:57 ` Chris Wilson
2010-06-16 16:12 ` Marc Deop i Argemí
2010-06-17 13:30 ` Marc Deop i Argemí
2010-06-17 21:34 ` Elias Gabriel Amaral da Silva
2010-06-18 6:09 ` Carl Worth
2010-06-21 5:09 ` Elias Gabriel Amaral da Silva
2010-06-21 6:08 ` Elias Gabriel Amaral da Silva
2010-06-21 6:37 ` Christopher James Halse Rogers
2010-06-22 18:42 ` Elias Gabriel Amaral da Silva
2010-06-21 5:31 ` Elias Gabriel Amaral da Silva
2010-06-25 6:23 ` Carl Worth
2010-06-25 8:53 ` Clemens Eisserer
2010-06-16 9:20 ` Chris Wilson
2010-06-16 11:25 ` Marc Deop i Argemí
2010-06-16 11:38 ` Andrew Lutomirski
2010-06-16 15:07 ` Andrew Lutomirski
2010-06-17 20:32 ` Jesse Barnes
2010-06-17 22:27 ` Marc Deop i Argemí
2010-06-18 0:17 ` Andrew Lutomirski
2010-06-18 0:20 ` Marc Deop i Argemí
2010-06-18 2:44 ` Jesse Barnes
2010-06-18 20:04 ` Jesse Barnes
2010-06-18 20:07 ` Jesse Barnes
2010-06-19 16:35 ` Marc Deop i Argemí
2010-06-20 15:29 ` Andrew Lutomirski
2010-06-21 20:32 ` Andrew Lutomirski
2010-06-23 16:07 ` Jesse Barnes
2010-07-01 20:55 ` Andrew Lutomirski
2010-07-01 21:21 ` Jesse Barnes
2010-07-01 21:34 ` Andrew Lutomirski
2010-06-15 14:54 ` Vasily Khoruzhick
2010-06-15 16:49 ` Carl Worth
2010-06-15 16:55 ` Vasily Khoruzhick
2010-06-15 17:36 ` Vasily Khoruzhick
2010-06-15 19:58 ` Clemens Eisserer
2010-06-15 20:15 ` Chris Wilson
2010-06-15 21:03 ` Clemens Eisserer
2010-06-15 21:26 ` Carl Worth
2010-06-15 21:40 ` Chris Wilson [this message]
2010-06-15 22:05 ` Clemens Eisserer
2010-06-15 22:24 ` Clemens Eisserer
2010-06-15 22:31 ` Chris Wilson
2010-06-15 22:56 ` Clemens Eisserer
2010-06-16 5:45 ` Vasily Khoruzhick
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='89kc63$h60g7r@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linuxhippy@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.