From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101837] libdrm fails to get bus id
Date: Fri, 21 Jul 2017 12:32:57 +0000 [thread overview]
Message-ID: <bug-101837-502-g93tiWhtjO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101837-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 536 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101837
--- Comment #5 from Emil Velikov <emil.l.velikov@gmail.com> ---
(In reply to Lauri Kasanen from comment #4)
> The DRM node must be opened (and kept open for the lifetime of the app) to
> make the VRAM queries, or to make the register queries on kernels that
> prohibit direct access (e.g. Ubuntu).
Right - the fd is required for the queries. Yet the app does not seem to close
it upon exit ;-)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1355 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-21 12:32 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
2017-07-21 6:30 ` bugzilla-daemon
2017-07-21 12:32 ` bugzilla-daemon [this message]
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-g93tiWhtjO@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.