From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 49484] New: invalid enum 0x500, invalid value 0x501
Date: Fri, 04 May 2012 13:14:22 +0000 [thread overview]
Message-ID: <bug-49484-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=49484
Bug #: 49484
Summary: invalid enum 0x500, invalid value 0x501
Classification: Unclassified
Product: Mesa
Version: 8.0
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: enhancement
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: hramrach@gmail.com
running D3D application in wine I get lots of
err:d3d_surface:surface_allocate_surface >>>>>>>>>>>>>>>>> GL_INVALID_VALUE
(0x501) from glTexImage2D @ surface.c / 2566
err:d3d_surface:surface_upload_data >>>>>>>>>>>>>>>>> GL_INVALID_ENUM (0x500)
from glTexSubImage2D @ surface.c / 2349
Needless to say I get pretty much nothing visible.
OpenGL renderer string: Gallium 0.4 on AMD REDWOOD
OpenGL version string: 2.1 Mesa 8.0.2
Maybe wine is using a format/feature without checking it is available here.
However, r600 could implement it I guess.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-05-04 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 13:14 bugzilla-daemon [this message]
2012-05-04 13:15 ` [Bug 49484] invalid enum 0x500, invalid value 0x501 bugzilla-daemon
2012-05-04 16:22 ` bugzilla-daemon
2012-05-04 18:21 ` bugzilla-daemon
2012-05-07 16:55 ` bugzilla-daemon
2012-05-07 17:02 ` bugzilla-daemon
2012-05-07 17:37 ` bugzilla-daemon
2012-05-07 18:03 ` 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-49484-502@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.