From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 41613] New: [r300g] Latest Mesa breaks Wine - "Bad vertex format"
Date: Sun, 9 Oct 2011 07:24:52 -0700 (PDT) [thread overview]
Message-ID: <bug-41613-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=41613
Summary: [r300g] Latest Mesa breaks Wine - "Bad vertex format"
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: rankincj@googlemail.com
Trying to run Wine against the latest Mesa causes this error message:
r300: Bad vertex format r32g32b32a32_sint.
err:module:attach_process_dlls "opengl32.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"H:\\World of
Warcraft\\Wow.exe" failed, status 80000101
The following commit seems to be responsible:
commit 4e28e6f6c777841b9ffe7a7ad1e865e2595f70f9
Author: Dave Airlie <airlied@redhat.com>
Date: Mon Sep 26 19:05:18 2011 +0100
u_blitter: add integer clear support
We need add a new set of fragment shader variants, along with new vertex
elements for signed and unsigned clears.
The new fragment shader variants are due to the integers values requiring
CONSTANT interpolation. The new vertex element descriptions are for passing
the clear color as an unsigned or signed integer value.
Signed-off-by: Dave Airlie <airlied@redhat.com>
--
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:[~2011-10-09 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 14:24 bugzilla-daemon [this message]
2011-10-09 14:25 ` [Bug 41613] [r300g] Latest Mesa breaks Wine - "Bad vertex format" bugzilla-daemon
2011-10-09 15:37 ` bugzilla-daemon
2011-10-09 18:48 ` bugzilla-daemon
2011-10-09 19:24 ` 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-41613-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.