mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Pekka Paalanen <pekka.paalanen@collabora.com>,
	dri-devel@lists.freedesktop.org, Hector Martin <marcan@marcan.st>,
	Javier Martinez Canillas <javierm@redhat.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	asahi@lists.linux.dev
Subject: Re: [PATCH] drm/simpledrm: Only advertise formats that are supported
Date: Fri, 28 Oct 2022 13:11:34 +0200	[thread overview]
Message-ID: <18b98740-6730-3c3a-c95b-c377cb355e77@suse.de> (raw)
In-Reply-To: <Y1upGwtjWgtLUZ1k@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 1078 bytes --]

Hi

Am 28.10.22 um 12:04 schrieb Ville Syrjälä:
> On Thu, Oct 27, 2022 at 01:08:24PM +0200, Thomas Zimmermann wrote:
>> I trust you when you say that <native>->XRGB8888 is not enough. But
>> although I've read your replies, I still don't understand why this
>> switch is necessary.
>>
>> Why don't we call drm_fb_build_fourcc_list() with the native
>> format/formats and let it append a number of formats, such as adding
>> XRGB888, adding ARGB8888 if necessary, adding ARGB2101010 if necessary.
>> Each with a elaborate comment why and which userspace needs the format. (?)
> 
> Are you saying there is some real userspace that breaks without
> the alpha formats? That would already be broken on many devices.

We should scrap them all IMHO, unless the hardware really supports them. 
See the other discussion on this patch's v2 as well.

Best regards
Thomas

> 

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

      reply	other threads:[~2022-10-28 11:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 10:13 Hector Martin
2022-10-27 10:53 ` Hector Martin
2022-10-28  9:18   ` Michel Dänzer
2022-10-27 11:08 ` Thomas Zimmermann
2022-10-27 12:22   ` Pekka Paalanen
2022-10-27 12:51     ` Thomas Zimmermann
2022-10-27 12:31   ` Hector Martin
2022-10-28 10:04   ` Ville Syrjälä
2022-10-28 11:11     ` Thomas Zimmermann [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=18b98740-6730-3c3a-c95b-c377cb355e77@suse.de \
    --to=tzimmermann@suse.de \
    --cc=asahi@lists.linux.dev \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcan@marcan.st \
    --cc=pekka.paalanen@collabora.com \
    --cc=stable@vger.kernel.org \
    --cc=ville.syrjala@linux.intel.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

all inboxes | Powered by JetHome®