From: Emil Velikov <emil.l.velikov@gmail.com>
To: Simon Ser <contact@emersion.fr>
Cc: Pekka Paalanen <pekka.paalanen@collabora.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Maxime Ripard <maxime@cerno.tech>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 8/8] drm/modifiers: Enforce consistency between the cap an IN_FORMATS
Date: Tue, 4 May 2021 16:48:15 +0100 [thread overview]
Message-ID: <CACvgo51On7=M28b9X+k-SGe4q2btGOoe+2_1-nBTrqjr7XTjQw@mail.gmail.com> (raw)
In-Reply-To: <_ICN4Ho9WvMf55FvcWEqbzvApWTRd3hIiVAJ8vkrc0XTljEiq3f5aOB8ElxJL3WTL--P1-VZddkcjLcwdL3YxdPkYClHuyMhtQ0-Zv88Fh0=@emersion.fr>
On Tue, 4 May 2021 at 15:58, Simon Ser <contact@emersion.fr> wrote:
>
> Continuing on that idea to push for enabling the cap in more cases: do
> we have a policy to require new drivers to always support modifiers?
>
> That would be nice, even if it's just about enabling LINEAR.
Sounds perfectly reasonable IMHO. I think we ought to document this
policy (requirement ideally) somewhere - say alongside the "all new
KMS drivers must support atomic modeset", which lives in ...
-Emil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Emil Velikov <emil.l.velikov@gmail.com>
To: Simon Ser <contact@emersion.fr>
Cc: Pekka Paalanen <pekka.paalanen@collabora.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Inki Dae <inki.dae@samsung.com>,
Maxime Ripard <maxime@cerno.tech>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [Intel-gfx] [PATCH 8/8] drm/modifiers: Enforce consistency between the cap an IN_FORMATS
Date: Tue, 4 May 2021 16:48:15 +0100 [thread overview]
Message-ID: <CACvgo51On7=M28b9X+k-SGe4q2btGOoe+2_1-nBTrqjr7XTjQw@mail.gmail.com> (raw)
In-Reply-To: <_ICN4Ho9WvMf55FvcWEqbzvApWTRd3hIiVAJ8vkrc0XTljEiq3f5aOB8ElxJL3WTL--P1-VZddkcjLcwdL3YxdPkYClHuyMhtQ0-Zv88Fh0=@emersion.fr>
On Tue, 4 May 2021 at 15:58, Simon Ser <contact@emersion.fr> wrote:
>
> Continuing on that idea to push for enabling the cap in more cases: do
> we have a policy to require new drivers to always support modifiers?
>
> That would be nice, even if it's just about enabling LINEAR.
Sounds perfectly reasonable IMHO. I think we ought to document this
policy (requirement ideally) somewhere - say alongside the "all new
KMS drivers must support atomic modeset", which lives in ...
-Emil
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-05-04 15:48 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 9:20 [PATCH 1/8] drm/arm: Don't set allow_fb_modifiers explicitly Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` [PATCH 2/8] drm/arm/malidp: Always list modifiers Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` Daniel Vetter
2021-04-27 15:41 ` Liviu Dudau
2021-04-27 15:41 ` [Intel-gfx] " Liviu Dudau
2021-04-27 15:41 ` Liviu Dudau
2021-04-27 9:20 ` [PATCH 3/8] drm/i915: Don't set allow_fb_modifiers explicitly Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` [PATCH 4/8] drm/msm/dpu1: " Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` [PATCH 5/8] drm/msm/mdp4: Fix modifier support enabling Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` Daniel Vetter
2021-04-27 9:20 ` [PATCH 6/8] drm/nouveau: Don't set allow_fb_modifiers explicitly Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` Daniel Vetter
2021-04-27 9:20 ` [Nouveau] " Daniel Vetter
2021-04-27 9:20 ` [PATCH 7/8] drm/stm: " Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` Daniel Vetter
2021-04-29 19:35 ` Philippe CORNU - foss
2021-04-29 19:35 ` [Intel-gfx] " Philippe CORNU - foss
2021-04-29 19:35 ` Philippe CORNU - foss
2021-04-27 9:20 ` [PATCH 8/8] drm/modifiers: Enforce consistency between the cap an IN_FORMATS Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:30 ` Simon Ser
2021-04-27 9:30 ` [Intel-gfx] " Simon Ser
2021-04-27 11:32 ` Emil Velikov
2021-04-27 11:32 ` [Intel-gfx] " Emil Velikov
2021-04-27 12:22 ` Daniel Vetter
2021-04-27 12:22 ` [Intel-gfx] " Daniel Vetter
2021-05-04 14:10 ` Emil Velikov
2021-05-04 14:10 ` [Intel-gfx] " Emil Velikov
2021-05-04 14:58 ` Simon Ser
2021-05-04 14:58 ` [Intel-gfx] " Simon Ser
2021-05-04 15:48 ` Emil Velikov [this message]
2021-05-04 15:48 ` Emil Velikov
2021-05-04 13:38 ` Pekka Paalanen
2021-05-04 13:38 ` [Intel-gfx] " Pekka Paalanen
2021-05-05 19:24 ` Daniel Vetter
2021-05-05 19:24 ` [Intel-gfx] " Daniel Vetter
2021-05-06 9:55 ` Daniel Vetter
2021-05-06 9:55 ` [Intel-gfx] " Daniel Vetter
2021-04-27 10:58 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/8] drm/arm: Don't set allow_fb_modifiers explicitly Patchwork
2021-04-27 11:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-04-27 15:25 ` [PATCH 1/8] " Liviu Dudau
2021-04-27 15:25 ` [Intel-gfx] " Liviu Dudau
2021-04-27 15:46 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/8] " 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='CACvgo51On7=M28b9X+k-SGe4q2btGOoe+2_1-nBTrqjr7XTjQw@mail.gmail.com' \
--to=emil.l.velikov@gmail.com \
--cc=airlied@linux.ie \
--cc=contact@emersion.fr \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maxime@cerno.tech \
--cc=pekka.paalanen@collabora.com \
--cc=tzimmermann@suse.de \
/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.