From: Erik Faye-Lund <erik.faye-lund@collabora.com>
To: Daniel Stone <daniel@fooishbar.org>, eric.smith@collabora.com
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
healych@amazon.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm: add modifiers for MediaTek tiled formats
Date: Fri, 24 Jan 2025 09:42:01 +0100 [thread overview]
Message-ID: <27c6cd114cd37131582e3e81716d09074cab0223.camel@collabora.com> (raw)
In-Reply-To: <CAPj87rPQZTg2Laws1BdzL-UOLV6jWinJqM=GeLdvm7UNEEnrdA@mail.gmail.com>
On Thu, 2025-01-09 at 13:14 +0000, Daniel Stone wrote:
> Hi Eric,
>
> On Thu, 19 Dec 2024 at 17:49, <eric.smith@collabora.com> wrote:
> > MediaTek (MTK) uses some unique tiled memory formats
> > for video decoding. Add these to the uapi drm_fourcc.h
> > so that we can use them in Mesa, GStreamer, and other
> > tools/libraries.
>
> Thanks, this is:
> Reviewed-by: Daniel Stone <daniels@collabora.com>
>
> I can push into drm-misc as well, but give me a bit to get dim set up
> again.
>
This is not yet in drm-misc, my understanding from back-channels is
that we're waiting for some sort of ack from MTK. Do we have any
timeline for this, so this can land at some point soonish?
next prev parent reply other threads:[~2025-01-24 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 17:49 [PATCH v2] drm: add modifiers for MediaTek tiled formats eric.smith
2025-01-09 13:14 ` Daniel Stone
2025-01-24 8:42 ` Erik Faye-Lund [this message]
2025-01-24 11:24 ` Daniel Stone
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=27c6cd114cd37131582e3e81716d09074cab0223.camel@collabora.com \
--to=erik.faye-lund@collabora.com \
--cc=airlied@gmail.com \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.smith@collabora.com \
--cc=healych@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox