From: Robert Foss <robert.foss@collabora.com>
To: dri-devel <dri-devel@lists.freedesktop.org>,
John Stultz <john.stultz@linaro.org>,
Emil Velikov <emil.l.velikov@gmail.com>,
Tomasz Figa <tfiga@google.com>,
Stefan Schake <stschake@gmail.com>,
Chih-Wei Huang <cwhuang@linux.org.tw>,
Daniel Stone <daniel.stone@collabora.com>
Cc: Robert Foss <robert.foss@collabora.com>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>
Subject: [RFC 0/1] DRM Node Probing functionality
Date: Thu, 12 Apr 2018 05:55:53 +0200 [thread overview]
Message-ID: <20180412035554.30874-1-robert.foss@collabora.com> (raw)
*Resend the whole actual series*
This patch implements a simple function for matching DRM device FDs against
the desired properties of a device that you are looking for.
The properties that are possible to look for are the elements of DrmVersion
and DrmDevice.
The discussion that led to this series can be found here:
https://lists.freedesktop.org/archives/mesa-dev/2018-January/183878.html
In the previous discussion we left off having settled on implementing this
in mesa/src/loader/loader.c, which I initially did. But the code ended up being
so generic that there's no reason for it not to live in libdrm, since it can be
used for any compositor and mesa.
The implementer will still have to iterate through all of the devices available
on the target, and see if they match. This additional functionality could be
moved into libdrm at a later point if it turns out that all of the users do this
in the same manner.
If there is some variety, for example with selecting fallback devices if nothing
matches maybe it is best left up to the user of libdrm.
The biggest problem with the approach as implemented, the way I see it, is how
we match against the DrmVersion/DrmDevice of a given FD.
Currently we use DrmVersion & DrmDevice as supplied by the caller to define what
we are looking for.
This is a little bit problematic, especially for DrmDevice, since all of the
elements of the struct do not have enough bitspace to signal that we are
uninterested in looking for that specific element. DrmDevice uses
drmDevicesEqual() to do what amounts to a memcmp of the DrmDevice argument and
the one of the FD. So looking for any device on any PCI bus with just the
PCI vendor ID supplied isn't possible.
An alternative Daniel Stone suggested is adding enums for different properties
and allowing the caller to supply a list of properties that are interesting and
their values. In terms of long-term maintainership this might be less pleasant
than the approach of the current implementation.
Robert Foss (1):
xf86drm: Add drmHandleMatch func
xf86drm.h | 2 ++
xf86drmMode.c | 69 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 71 insertions(+)
--
2.14.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-04-12 3:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 3:55 Robert Foss [this message]
2018-04-12 3:55 ` [RFC 1/1] xf86drm: Add drmHandleMatch func Robert Foss
2018-04-16 4:17 ` [RFC 0/1] DRM Node Probing functionality Tomasz Figa
-- strict thread matches above, loose matches on Subject: below --
2018-04-11 14:49 Robert Foss
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=20180412035554.30874-1-robert.foss@collabora.com \
--to=robert.foss@collabora.com \
--cc=cwhuang@linux.org.tw \
--cc=daniel.stone@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=john.stultz@linaro.org \
--cc=stschake@gmail.com \
--cc=tfiga@google.com \
--cc=tomeu.vizoso@collabora.com \
/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