From: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
dri devel <dri-devel@lists.freedesktop.org>
Subject: Re: RFC: hardware accelerated bitblt using dma engine
Date: Thu, 4 Aug 2016 01:19:13 +0200 [thread overview]
Message-ID: <57A27BF1.5090001@gr13.net> (raw)
In-Reply-To: <edeac241-c2e0-7daa-ebf7-a22e82e8f3b9@samsung.com>
On 03.08.2016 11:24, Marek Szyprowski wrote:
Hi,
> I'm working now on something similar, but more generic. There is
> already a framework for picture processing (converting, scaling,
> blitting, rotating) in Exynos DRM.
In DRM, not v4l ? Hmm, interesting.
On mx5/mx6 we've got an IPU, which is accessible via v4l, eg.for
colorspace conversion, jpeg encode/decode, rotation, etc.
(anyone of the involved folks @ptx here on the list ?)
Yet another overlap between DRM and V4L (IMHO, seems to be a matter of
perspective of perspective and usecases, where to put such stuff in)
By the way: what's the status of sharing buffers between DRM and V4L ?
I could also live with having such an hw-based image-copy operation
living within v4l, when they're operating on the the same buffers.
> http://thread.gmane.org/gmane.linux.kernel.samsung-soc/49743
seems to be offline
> I plan to propose an API based on DRM object/properties, which will be
> similar to KMS atomic API. I will let you know when I have it ready for
> presenting in public.
hmm, I'm getting curious ...
--mtx
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-08-03 23:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 13:21 RFC: hardware accelerated bitblt using dma engine Enrico Weigelt, metux IT consult
2016-08-02 14:04 ` Daniel Vetter
2016-08-02 21:43 ` Enrico Weigelt, metux IT consult
2016-08-02 23:12 ` Rob Clark
2016-08-03 3:33 ` Enrico Weigelt, metux IT consult
2016-08-03 3:47 ` Dave Airlie
2016-08-03 4:39 ` Enrico Weigelt, metux IT consult
2016-08-03 9:24 ` Marek Szyprowski
2016-08-03 11:47 ` Daniel Vetter
2016-08-03 23:32 ` Enrico Weigelt, metux IT consult
2016-08-04 7:50 ` Daniel Vetter
2016-08-04 10:09 ` Daniel Stone
2016-08-04 23:16 ` Enrico Weigelt, metux IT consult
2016-08-05 4:37 ` Enrico Weigelt, metux IT consult
2016-08-05 7:49 ` Daniel Vetter
2016-08-05 7:47 ` Daniel Vetter
2016-08-03 23:19 ` Enrico Weigelt, metux IT consult [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=57A27BF1.5090001@gr13.net \
--to=enrico.weigelt@gr13.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=m.szyprowski@samsung.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