From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206351] RX 5600 XT Not Correctly Recognized, Max Memory Frequency Below Where it Should Be
Date: Thu, 30 Jan 2020 18:12:39 +0000 [thread overview]
Message-ID: <bug-206351-2300-7aHClANt7O@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206351-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206351
Alex Deucher (alexdeucher@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexdeucher@gmail.com
--- Comment #2 from Alex Deucher (alexdeucher@gmail.com) ---
The only thing missing is the marketing strings. See this libdrm merge
request:
https://gitlab.freedesktop.org/mesa/drm/merge_requests/44
that will provide a proper string for mesa libraries like OpenGL or vulkan.
Tools like lspci and inxi use the pci ids database (http://pci-ids.ucw.cz/) to
get their strings. However the strings on that site are tied to the device
ids. The marketing names for AMD parts vary based on the device id and the
revision id as well as the subsystem ids in some cases. the pci ids database
does not provide a way to provide a string based on a combination of ids.
If you want the newer smc firmware, it's available here:
https://people.freedesktop.org/~agd5f/radeon_ucode/navi10/new/navi10_smc.bin
it will be upstreamed to linux-firmware once it's finished it's internal QA
cycle.
As to the clocks, they are provided in the vbios. That is where the driver
gets them. Can you provide more information about what OEM product this is?
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-01-30 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 9:24 [Bug 206351] New: RX 5600 XT Not Correctly Recognized, Max Memory Frequency Below Where it Should Be bugzilla-daemon
2020-01-30 9:31 ` [Bug 206351] " bugzilla-daemon
2020-01-30 18:12 ` bugzilla-daemon [this message]
2020-01-30 18:52 ` bugzilla-daemon
2020-01-30 21:21 ` bugzilla-daemon
2020-01-31 1:46 ` bugzilla-daemon
2020-01-31 18:00 ` bugzilla-daemon
2020-01-31 18:28 ` bugzilla-daemon
2020-01-31 19:26 ` 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-206351-2300-7aHClANt7O@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.