From: Daniel Vetter <daniel@ffwll.ch>
To: Simon Ser <contact@emersion.fr>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] Non-dumb framebuffer tests
Date: Fri, 18 Jan 2019 10:56:26 +0100 [thread overview]
Message-ID: <20190118095626.GF3271@phenom.ffwll.local> (raw)
In-Reply-To: <ZhTOa2bj1T3rf44ApEZbYpWGX9kJnQsz9EGVxBvtdUTWCSLauluikhkkDFecORu2Sir_YF44xKr-eGL4nKdsqjjcD-t1n2fFQFPNrWKl8j0=@emersion.fr>
On Fri, Jan 18, 2019 at 09:07:48AM +0000, Simon Ser wrote:
> Hi,
>
> I've been wondering about tests with non-dumb framebuffers. From what I've
> understood, the create_bo_for_fb helper will use dumb framebuffers unless
> the format is tiling or a specific size/stride is requested or it's YUV.
Hm, maybe we need dumb_create2, like we have addfb2?
> This makes it so that some framebuffer type/usage combinations are not
> tested, especially for simple RGBA formats. For instance, cursor tests
> seem to always use dumb framebuffers.
>
> Would it be useful to add GEM (or GBM?) framebuffer tests?
Yeah. I think longer-term we might want to have plug-in library for
allocating buffers on the various gpus, if things get too extreme. Pulling
in something like gbm is probably too much (and wont solve anything for
display-only drivers).
This also gets into areas where kms isn't all the well-specified, so
definitely good to have better tests for it.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-01-18 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 9:07 [igt-dev] Non-dumb framebuffer tests Simon Ser
2019-01-18 9:56 ` Daniel Vetter [this message]
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=20190118095626.GF3271@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=contact@emersion.fr \
--cc=igt-dev@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