From: Eric Anholt <eric@anholt.net>
To: Stefan Wahren <stefan.wahren@i2se.com>,
Boris Brezillon <boris.brezillon@bootlin.com>,
"Schake, Stefan" <stschake@gmail.com>
Cc: khilman@baylibre.com, dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: vc4: Detect working driver from cmdline
Date: Mon, 21 May 2018 10:55:01 -0700 [thread overview]
Message-ID: <87vabgdhca.fsf@anholt.net> (raw)
In-Reply-To: <2128012459.52582.1526639683667@email.1und1.de>
[-- Attachment #1.1: Type: text/plain, Size: 891 bytes --]
Stefan Wahren <stefan.wahren@i2se.com> writes:
> Hi,
> in order to improve kernelci.org results and avoid false positive cases like this [1], i suggested to also test for a working VC4 driver. In order to keep it simple, we should do it from userspace.
>
> My first idea was:
>
> test -d /sys/kernel/debug/dri/0 || echo "Error case"
>
> But maybe you have a better / more reliable solution?
>
> [1] - https://storage.kernelci.org/mainline/master/v4.17-rc5-69-g3acf4e395260/arm64/defconfig/lab-mhart/boot-bcm2837-rpi-3-b.html
GL testing involves running piglit and comparing to a previous run to
confirm no regressions, and we're building out the intel-gpu-tools
support for display testing now. That's what you'd need to make sure
the driver actually works. If you just want to make sure module probe
doesn't fail, I guess that test is fine (it would catch bugs we've seen
in the past).
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 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:[~2018-05-21 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 10:34 vc4: Detect working driver from cmdline Stefan Wahren
2018-05-21 17:55 ` Eric Anholt [this message]
2018-05-21 19:02 ` Stefan Wahren
2018-05-22 9:27 ` Tomeu Vizoso
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=87vabgdhca.fsf@anholt.net \
--to=eric@anholt.net \
--cc=boris.brezillon@bootlin.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=khilman@baylibre.com \
--cc=stefan.wahren@i2se.com \
--cc=stschake@gmail.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.