dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102204] GLideN64 very slow on oland/radeonsi
Date: Mon, 14 Aug 2017 01:40:49 +0000	[thread overview]
Message-ID: <bug-102204-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 102204
           Summary: GLideN64 very slow on oland/radeonsi
           Product: Mesa
           Version: 17.1
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: aaronbpaden@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

I'm using:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland
PRO [Radeon R7 240/340]
Mesa: 17.1.6
Linux: 4.12.6

This is somewhat related to #98724.

I decided to give GLideN64 another try since it now works with Rogue Squadron,
but I've found that while it does render (I wouldn't say that #98724 has been
fixed. I just think that GLideN64/GLupeN64 no longer use
glDrawElementsIndirect) it's still unplayably slow. The Windows drivers do work
fine on the same hardware.

For this test, I was using the prebuilt and configured version found here:
https://m64p.github.io/ the executable is mupen64plus-gui. Because of #97226 it
has to be launched from the terminal.

The download link doesn't work with HTTPS Everywhere for some reason. Source is
here: https://github.com/m64p/mupen64plus-GLideN64

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

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

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

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

             reply	other threads:[~2017-08-14  1:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14  1:40 bugzilla-daemon [this message]
2018-01-22  7:41 ` [Bug 102204] GLideN64 very slow on oland/radeonsi bugzilla-daemon
2018-01-22  8:08 ` bugzilla-daemon
2018-01-22  8:14 ` [Bug 102204] GLideN64 very slow on r600/radeonsi bugzilla-daemon
2018-01-24 10:28 ` bugzilla-daemon
2018-01-24 10:30 ` bugzilla-daemon
2018-01-24 10:33 ` bugzilla-daemon
2018-03-11  7:16 ` [Bug 102204] GLideN64 very slow on r600/radeonsi - GL_ARB_buffer_storage bug bugzilla-daemon
2018-03-31 14:34 ` bugzilla-daemon
2018-03-31 14:36 ` 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-102204-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox