From: Thierry Reding <treding@nvidia.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: ML dri-devel <dri-devel@lists.freedesktop.org>,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH libdrm] tests/util: Add support for meson module
Date: Fri, 20 Jan 2017 17:17:39 +0100 [thread overview]
Message-ID: <20170120161739.GA28228@ulmo.ba.sec> (raw)
In-Reply-To: <CACvgo51hJDBrd977_bVznAaZwvCyy6gF-88BAbqJsoJPAp1Dww@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1473 bytes --]
On Fri, Jan 20, 2017 at 02:13:00PM +0000, Emil Velikov wrote:
> On 19 January 2017 at 09:19, Thierry Reding <treding@nvidia.com> wrote:
> > On Wed, Jan 18, 2017 at 02:59:21PM +0100, Neil Armstrong wrote:
> >> Add support for Amlogic Meson DRM driver merged for Linux 4.10.
> >>
> >> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> >> ---
> >> tests/util/kms.c | 1 +
> >> 1 file changed, 1 insertion(+)
> >
> > Applied, thanks.
> >
> Was going to say "NACK use Thierry's helpers" but you've beat me to it.
> As a Tl;DR: we _really_ want to stop using drmOpen* for anything that's KMS.
I think it's still useful to have this helper to iterate over all
supported driver because it enables easy testing with just a simple
modetest.
That said, for (almost) as long as I remember I've been using the -M
option to prevent modetest from iterating over the list, which can take
fairly long if you've got DRM_DEBUG messages enabled.
I'm not sure I understand exactly what you're suggesting by "use
Thierry's helpers". modetest and other tests use util_open() internally
now. That in turn uses drmOpen(), though we're of course open to change
that. Are you suggesting we somehow use drmDevice to locate existing
devices?
We could implement some heuristic that finds the first device with a
primary node, but what if we want to support the -M option? There is
currently no way of getting the driver from drmDevice. Maybe that's
something we should add anyway.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 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-01-20 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 13:59 [PATCH libdrm] tests/util: Add support for meson module Neil Armstrong
2017-01-19 9:19 ` Thierry Reding
2017-01-20 14:13 ` Emil Velikov
2017-01-20 16:17 ` Thierry Reding [this message]
2017-01-20 18:28 ` Emil Velikov
2017-01-26 15:49 ` Thierry Reding
2017-01-26 16:14 ` Emil Velikov
2017-01-27 7:47 ` Thierry Reding
2017-01-27 15:42 ` Emil Velikov
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=20170120161739.GA28228@ulmo.ba.sec \
--to=treding@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=narmstrong@baylibre.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 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.