All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29012] New: [r300g] Driver needs some kind of force_s3tc_enable option
Date: Mon, 12 Jul 2010 01:27:59 -0700 (PDT)	[thread overview]
Message-ID: <bug-29012-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [r300g] Driver needs some kind of force_s3tc_enable
                    option
           Product: Mesa
           Version: git
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: rankincj@googlemail.com


Some games (such as World of Warcraft) need S3TC texture support, and so will
crash if the OpenGL S3TC extensions are not advertised. Currently, the only way
to make Gallium advertise the S3TC extensions is to load the IP-encumbered
libtxc_dxtn library.

WoW can run successfully using the r300c driver without the libtxc_dxtn,
provided the force_s3tc_enable option is used. (There are some issues with
corrupt textures, although some of these issues might be caused e.g. by r300c
not supporting texture cache regions. However, my point is that WoW doesn't
crash instantly with a null pointer exception if the S3TC extensions are
available.)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-07-12  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-12  8:27 bugzilla-daemon [this message]
2010-09-10 22:16 ` [Bug 29012] [r300g] Driver needs some kind of force_s3tc_enable option bugzilla-daemon
2010-10-11  9:07 ` [Bug 29012] Gallium drivers should respect force_s3tc_enable option (and maybe other) as classic driver 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-29012-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.