public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 1/2] lib/igt_fb: Add support for DRM_FORMAT_C8 format
Date: Tue, 14 Nov 2017 17:20:16 +0200	[thread overview]
Message-ID: <20171114152016.GJ10981@intel.com> (raw)
In-Reply-To: <1510671515-522-2-git-send-email-juhapekka.heikkila@gmail.com>

On Tue, Nov 14, 2017 at 04:58:34PM +0200, Juha-Pekka Heikkila wrote:
> DRM_FORMAT_C8 is needed for kms_rotation_crc test
> 
> Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> ---
>  lib/igt_fb.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/lib/igt_fb.c b/lib/igt_fb.c
> index d4eaed7..00d52f7 100644
> --- a/lib/igt_fb.c
> +++ b/lib/igt_fb.c
> @@ -67,6 +67,7 @@ static struct format_desc_struct {
>  	DF(XRGB8888,	RGB24,		32, 24),
>  	DF(XRGB2101010,	RGB30,		32, 30),
>  	DF(ARGB8888,	ARGB32,		32, 32),
> +	DF(C8,		A8,		 8,  8),

What I've been thinking for pixel formats not supported by cairo is that
we'd add software routines to convert between them and XRGB8888 and hook
that up so that we do the conversion to/from XRGB888 in the cairo
surface create/destroy hooks. And if we go nuts we could even expand
rendercopy to do some of the format conversions for us on the GPU.

For the time being, I think it's probably better to just check for C8
in the test and skip the cairo stuff entirely. Since this is just for
the bad-format test we don't actually need the fb to have any real
content.

>  };
>  #undef DF
>  
> -- 
> 2.7.4
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-11-14 15:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 14:58 [PATCH i-g-t 0/2] igt/kms_rotation_crc: Add RGB565 90 degree test for gen>9 Juha-Pekka Heikkila
2017-11-14 14:58 ` [PATCH i-g-t 1/2] lib/igt_fb: Add support for DRM_FORMAT_C8 format Juha-Pekka Heikkila
2017-11-14 15:20   ` Ville Syrjälä [this message]
2017-11-14 14:58 ` [PATCH i-g-t 2/2] igt/kms_rotation_crc: Add RGB565 90 degree test for gen>9 Juha-Pekka Heikkila
2017-11-14 15:24   ` Ville Syrjälä
2017-11-14 21:05 ` ✓ Fi.CI.BAT: success for igt/kms_rotation_crc: Add RGB565 90 degree test for gen>9 (rev2) Patchwork
2017-11-15  0:18 ` ✓ Fi.CI.IGT: " Patchwork

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=20171114152016.GJ10981@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=juhapekka.heikkila@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox