All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 52997] evergreen_cs_track_validate_cb:477 cb[0] bo too small when launching ds2 in wine
Date: Fri, 02 Nov 2012 15:23:28 +0000	[thread overview]
Message-ID: <bug-52997-502-87Rw2hR4GM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-52997-502@http.bugs.freedesktop.org/>


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

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

--- Comment #15 from mailbox.tec@gmail.com ---
(In reply to comment #14)
> You can install a 32 bit version of the open source 3D driver as well.  Just
> because the graphics in a game do not appear to be 3D, they generally still
> use a 3D API (OpenGL or Direct3D) which requires a 32 bit 3D driver since
> the apps are 32 bit.  Also there seem to be several possibly unrelated
> issues now piled onto this bug.

You've focused on minor point about the inability of having open source 32-bit
driver alongside 64-bit one. I don't know the cause of it, I only know that my
distribution provides this kind of setup for closed source catalyst package:
https://wiki.archlinux.org/index.php/Wine#Graphics_Drivers

To clarify, I do have 32-bit DRI Mesa drivers installed - the lib32-ati-dri
package mentioned in the link above - but I assume you mean xorg kind of
drivers. If this is some sort of distro-related bug, please state it so I can
nag other people about it ;-)

At the same time, I see my main point about display being fine in virtual
desktop mode has been ignored? To reiterate: it doesn't seem to me that, since
Wine is capable of rendering and display on the very same setup in different
mode, there are some unfullfilled requirements that block said display. After
all, as I described before, even in fullscreen mode there was some kind of
output, albeit buggy to the point of being unusable. But without the crucial
part of plumbing there would be no output at all.

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

[-- Attachment #1.2: Type: text/html, Size: 2581 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2012-11-02 15:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 10:10 [Bug 52997] New: evergreen_cs_track_validate_cb:477 cb[0] bo too small when launching ds2 in wine bugzilla-daemon
2012-07-31 18:38 ` [Bug 52997] " bugzilla-daemon
2012-08-03  7:49 ` bugzilla-daemon
2012-08-05 11:33 ` bugzilla-daemon
2012-08-05 11:54 ` bugzilla-daemon
2012-08-06 12:54 ` bugzilla-daemon
2012-09-05 17:22 ` bugzilla-daemon
2012-09-05 17:30 ` bugzilla-daemon
2012-09-28  6:52 ` bugzilla-daemon
2012-09-28 13:01 ` bugzilla-daemon
2012-10-03  0:32 ` bugzilla-daemon
2012-10-03 13:01 ` bugzilla-daemon
2012-10-05 21:28 ` bugzilla-daemon
2012-10-05 22:04 ` bugzilla-daemon
2012-11-01 23:46 ` bugzilla-daemon
2012-11-02 13:15 ` bugzilla-daemon
2012-11-02 15:23 ` bugzilla-daemon [this message]
2012-11-02 16:55 ` bugzilla-daemon
2019-09-18 19:00 ` 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-52997-502-87Rw2hR4GM@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.