From: Antonio Vargas <windenntw@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ian Romanick <idr@us.ibm.com>, Allen Akin <akin@pobox.com>,
Discuss issues related to the xorg tree
<xorg@lists.freedesktop.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: State of Linux graphics
Date: Thu, 1 Sep 2005 15:57:22 +0200 [thread overview]
Message-ID: <69304d110509010657d397a6f@mail.gmail.com> (raw)
In-Reply-To: <1125570042.15768.3.camel@localhost.localdomain>
On 9/1/05, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Iau, 2005-09-01 at 08:00 +0200, Antonio Vargas wrote:
> > 2. whole screen z-buffer, for depth comparison between the pixels
> > generated from each window.
>
> That one I question in part - if the rectangles are (as is typically the
> case) large then the Z buffer just ups the memory accesses. I guess for
> round windows it might be handy.
>
There are multiple ways to enhance the speed for zbuffer:
1. Use an hierarchical z-buffer
Divide the screen in 16x16 pixel tiles, and then a per-tile minimum
value. When rendering a poly, you first check the tile-z against the
poly-z and if it fails you can skip 256 pixels in one go.
2. Use scanline-major rendering:
for_each_scanline{
clear_z_for_scanline();
for_each_polygon{
draw_pixels_for_current_polygon_and scanline();
}
}
This is easily done by modeling the scanliner with a coroutine for each polygon
to be painted. The zbuffer is reduced to a scanline and is reused for
all scanlines,
so it's rather fast :)
--
Greetz, Antonio Vargas aka winden of network
http://wind.codepixel.com/
Las cosas no son lo que parecen, excepto cuando parecen lo que si son.
next prev parent reply other threads:[~2005-09-01 13:57 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 16:03 State of Linux graphics Jon Smirl
2005-08-30 17:26 ` David Reveman
2005-08-30 18:13 ` Jon Smirl
2005-08-30 22:38 ` Dave Airlie
2005-08-31 6:33 ` Allen Akin
2005-08-31 8:11 ` Anshuman Gholap
2005-08-31 17:20 ` David Reveman
2005-08-31 17:48 ` Jim Gettys
2005-08-31 18:23 ` Jon Smirl
2005-08-31 19:06 ` Allen Akin
2005-08-31 19:14 ` Jim Gettys
2005-08-31 18:29 ` Keith Packard
2005-08-31 20:06 ` Allen Akin
2005-08-31 20:20 ` Ian Romanick
2005-09-01 1:04 ` James Cloos
2005-08-31 21:06 ` Keith Packard
2005-09-01 1:58 ` Allen Akin
2005-09-01 3:11 ` Ian Romanick
2005-09-01 6:00 ` Antonio Vargas
2005-09-01 10:20 ` Alan Cox
2005-09-01 13:57 ` Antonio Vargas [this message]
2005-09-01 6:11 ` Allen Akin
2005-09-01 3:59 ` Keith Packard
2005-09-01 15:24 ` Brian Paul
2005-09-01 15:59 ` Jim Gettys
2005-09-01 16:39 ` Andreas Hauser
2005-09-01 20:18 ` Jim Gettys
2005-09-01 20:38 ` Jon Smirl
2005-09-01 21:29 ` Sean
2005-09-01 16:09 ` Alan Cox
2005-09-01 16:04 ` Brian Paul
2005-09-01 17:21 ` Ian Romanick
2005-09-01 17:26 ` Keith Whitwell
2005-09-01 20:03 ` Allen Akin
2005-08-31 3:11 ` Daniel Stone
2005-08-31 4:29 ` Jon Smirl
2005-08-31 4:50 ` Jon Smirl
[not found] ` <1125464500.8730.68.camel@localhost.localdomain>
2005-08-31 5:17 ` Jon Smirl
2005-08-31 5:23 ` Jon Smirl
2005-08-31 5:40 ` Jon Smirl
2005-08-31 6:15 ` Eric Anholt
2005-08-31 13:38 ` Jon Smirl
-- strict thread matches above, loose matches on Subject: below --
2005-09-02 2:44 rep stsb
2005-09-03 4:00 mcartoaje
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=69304d110509010657d397a6f@mail.gmail.com \
--to=windenntw@gmail.com \
--cc=akin@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=idr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xorg@lists.freedesktop.org \
/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.