All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109619] Add new alias for R600_TEX_ANISO for radeonsi
Date: Wed, 13 Feb 2019 02:24:18 +0000	[thread overview]
Message-ID: <bug-109619-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 109619
           Summary: Add new alias for R600_TEX_ANISO for radeonsi
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: shtetldik@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Now that radeonsi and r600 have separate code, R600_TEX_ANISO variable for
forcing anisotropic filtering looks out of place for radeonsi. While it might
be good to keep it for backwards compatibility and not breaking existing usage,
it would be nice to have some more appropriate alias as well.

May be RADEONSI_TEX_ANISO? Or may be make a new alias for both, like
AMD_TEX_ANISO to simplify things.

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

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

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

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

             reply	other threads:[~2019-02-13  2:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13  2:24 bugzilla-daemon [this message]
2019-05-07 23:36 ` [Bug 109619] Add new alias for R600_TEX_ANISO for radeonsi 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-109619-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.