From: Pekka Paalanen <ppaalanen@gmail.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>,
linux-amlogic@lists.infradead.org, nd <nd@arm.com>,
Brian Starkey <brian.starkey@arm.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/4] drm/fourcc: Add modifier definitions for describing Amlogic Video Framebuffer Compression
Date: Fri, 6 Mar 2020 18:17:47 +0200 [thread overview]
Message-ID: <20200306181747.5dbda69d@eldfell.localdomain> (raw)
In-Reply-To: <27d09559-055a-7bf3-0f23-9948da0e1f76@baylibre.com>
[-- Attachment #1.1: Type: text/plain, Size: 1367 bytes --]
On Fri, 6 Mar 2020 15:40:01 +0100
Neil Armstrong <narmstrong@baylibre.com> wrote:
> Hi Pekka, Brian, Daniel,
>
> On 06/03/2020 11:13, Daniel Vetter wrote:
> > On Tue, Mar 03, 2020 at 05:33:32PM +0200, Pekka Paalanen wrote:
...
> >> Sorry, it's waypipe, not pipewire:
> >> https://gitlab.freedesktop.org/mstoeckl/waypipe/
> >
> > I do think this is very much something we want to make possible. They
> > might pick a silly modifier (compression modifiers only compress bw, by
> > necessity the lossless ones have to increase storage space so kinda dumb
> > thing to push over the network if you don't add .xz or whatever on top).
>
> The AFBC, and Amlogic FBC are not size optimized compressions, but really
> layout and memory access optimized compressions, without a proper network
> size compression, transferring plain NV12 would be the same.
FWIW, waypipe is not intended to be the most efficient network
streaming protocol, but it is intended to be a direct Wayland protocol
proxy (X11 forwarding, anyone?), which means that it needs to be able to
transmit also dmabuf buffers as is. It does not want to understand
modifiers but just send opaque data.
It may or may not do lossless compression of the data it sends over the
wire, but it will replicate the dmabuf on the remote end.
Or so I'm told.
Thanks,
pq
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2020-03-06 16:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 9:08 [PATCH 0/4] drm/meson: add support for Amlogic Video FBC Neil Armstrong
2020-02-21 9:08 ` [PATCH 1/4] drm/fourcc: Add modifier definitions for describing Amlogic Video Framebuffer Compression Neil Armstrong
2020-03-02 16:28 ` Maxime Jourdan
2020-03-03 10:10 ` Pekka Paalanen
2020-03-03 10:53 ` Brian Starkey
2020-03-03 11:37 ` Daniel Vetter
2020-03-03 13:25 ` Pekka Paalanen
2020-03-03 15:33 ` Pekka Paalanen
2020-03-06 10:13 ` Daniel Vetter
2020-03-06 12:30 ` Pekka Paalanen
2020-03-06 14:40 ` Neil Armstrong
2020-03-06 16:17 ` Pekka Paalanen [this message]
2020-03-03 13:43 ` Brian Starkey
2020-02-21 9:08 ` [PATCH 2/4] drm/meson: add Amlogic Video FBC registers Neil Armstrong
2020-02-21 9:08 ` [PATCH 3/4] drm/meson: overlay: setup overlay for Amlogic FBC Neil Armstrong
2020-02-21 9:08 ` [PATCH 4/4] drm/meson: crtc: handle commit of Amlogic FBC frames Neil Armstrong
-- strict thread matches above, loose matches on Subject: below --
2020-02-20 16:27 [PATCH 0/4] drm/meson: add support for Amlogic Video FBC Neil Armstrong
2020-02-20 16:27 ` [PATCH 1/4] drm/fourcc: Add modifier definitions for describing Amlogic Video Framebuffer Compression Neil Armstrong
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=20200306181747.5dbda69d@eldfell.localdomain \
--to=ppaalanen@gmail.com \
--cc=brian.starkey@arm.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=nd@arm.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;
as well as URLs for NNTP newsgroup(s).