From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101837] libdrm fails to get bus id
Date: Thu, 20 Jul 2017 11:16:37 +0000 [thread overview]
Message-ID: <bug-101837-502-IFser4xDUB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101837-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 766 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101837
--- Comment #3 from Emil Velikov <emil.l.velikov@gmail.com> ---
DanielP an orthogonal solution is to simply not use drmOpen. While it works,
sometimes, there's a lot of hidden gotchas.
Simply replace the pciaccess + drmOpen with drmDevice2 - see
libdrm/tests/drmdevice.c.
Notes:
* radeon-top does _not_ need to open the card node, hence no need for auth -
directly or via xcb
* using pciaccess, or drmDevice2 with DRM_DEVICE_GET_PCI_REVISION will wake up
your discrete GPU, even if you're looking for the stats of you APU - you want
to avoid that if possible.
* do not forget to close the fd - currently it's leaked.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1508 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
next prev parent reply other threads:[~2017-07-20 11:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 7:57 [Bug 101837] libdrm fails to get bus id bugzilla-daemon
2017-07-19 11:01 ` bugzilla-daemon
2017-07-20 2:46 ` bugzilla-daemon
2017-07-20 11:16 ` bugzilla-daemon [this message]
2017-07-21 6:30 ` bugzilla-daemon
2017-07-21 12:32 ` bugzilla-daemon
2017-07-21 13:10 ` bugzilla-daemon
2017-07-21 14:56 ` bugzilla-daemon
2017-07-22 6:34 ` bugzilla-daemon
2019-09-24 17:09 ` 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-101837-502-IFser4xDUB@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