From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106053] Drawing at screen boundary is very slow.
Date: Tue, 17 Apr 2018 01:22:27 +0000 [thread overview]
Message-ID: <bug-106053-502-DljmUj3xP4@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106053-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 839 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106053
--- Comment #5 from Roland Scheidegger <sroland@vmware.com> ---
(In reply to Marek Olšák from comment #4)
> I think the hw doesn't have a clipper, though it shouldn't be hard to verify
> if it's true. Yeah, draw could use some optimizations for the clipper, e.g.
> the guardband, but simply doing culling (not clipping) should be enough for
> point sprites.
That's what I meant with guardband clipping: there's no actual clipping, but
the hw will still cull pixels outside the viewport. Hence it probably would be
better if draw wouldn't clip if a primitive doesn't fit into the viewport, but
fits into the (hw) guardband. (And you are right that point sprites are a bit
of a special case.)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1745 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-04-17 1:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 10:08 [Bug 106053] Drawing at screen boundary is very slow bugzilla-daemon
2018-04-15 10:16 ` bugzilla-daemon
2018-04-15 15:40 ` bugzilla-daemon
2018-04-16 21:55 ` bugzilla-daemon
2018-04-16 22:05 ` bugzilla-daemon
2018-04-17 1:22 ` bugzilla-daemon [this message]
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=bug-106053-502-DljmUj3xP4@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).