All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106053] Drawing at screen boundary is very slow.
Date: Sun, 15 Apr 2018 15:40:51 +0000	[thread overview]
Message-ID: <bug-106053-502-emRB8NDprM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106053-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 748 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106053

Marek Olšák <maraeo@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |NOTABUG
             Status|NEW                         |RESOLVED

--- Comment #2 from Marek Olšák <maraeo@gmail.com> ---
r300-r500 hardware capabilities don't meet the requirements of OpenGL core
profile.

r300g on RC410 uses software emulation for vertex shaders and clipping (the
same code as llvmpipe), because the hardware doesn't have any vertex processor
and clipper.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2223 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

  parent reply	other threads:[~2018-04-15 15:40 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 [this message]
2018-04-16 21:55 ` bugzilla-daemon
2018-04-16 22:05 ` bugzilla-daemon
2018-04-17  1:22 ` bugzilla-daemon

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-emRB8NDprM@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 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.