From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42025] [RADEON:KMS:R600] wine, Halo Trial: glPointSize error = INVALID_VALUE
Date: Thu, 20 Oct 2011 18:24:08 +0000 [thread overview]
Message-ID: <bug-42025-502-Kby1RwN2V2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-42025-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=42025
Sven Arvidsson <sa@whiz.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sa@whiz.se
--- Comment #1 from Sven Arvidsson <sa@whiz.se> 2011-10-20 11:24:08 PDT ---
I have played through Halo with Mesa drivers, but this was a while back and
with Intel, not Radeon hardware. Still, it's probably worth trying older
releases of both Wine and Mesa to rule out regressions.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-10-20 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 3:31 [Bug 42025] New: [RADEON:KMS:R600] wine, Halo Trial: glPointSize error = INVALID_VALUE bugzilla-daemon
2011-10-20 18:24 ` bugzilla-daemon [this message]
2019-09-18 18:58 ` [Bug 42025] " 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-42025-502-Kby1RwN2V2@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