From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95089] EON game ports black screen on RC410M [Mobility Radeon Xpress 200M]
Date: Tue, 26 Apr 2016 13:28:54 +0000 [thread overview]
Message-ID: <bug-95089-502-X5HiH5CJqr@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95089-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1026 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95089
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTOURBUG
--- Comment #3 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Emil Velikov from comment #2)
> The game seems to be trying to use GL_ARB_shader_texture_lod without
> checking if the extension is available. I would report that with the game
> and/or EON wrapper) developers - no program should ever do that.
>
> Based on the gallium code PIPE_CAP_SM3 (the toggle used to control the
> extension) is "/* Supported on r500 only. */". I'm not familiar with the
> hardware capabilities, but I'm leaning that this might be it.
Right. Xpress 200M is r3xx based and doesn't support SM3 features.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2657 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:[~2016-04-26 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 16:18 [Bug 95089] Stronghold3 Black screen with glove on RC410M [Mobility Radeon Xpress 200M] bugzilla-daemon
2016-04-23 16:19 ` bugzilla-daemon
2016-04-25 15:04 ` [Bug 95089] EON game ports black screen " bugzilla-daemon
2016-04-26 8:29 ` bugzilla-daemon
2016-04-26 13:28 ` 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-95089-502-X5HiH5CJqr@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