From: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
To: dri-devel@lists.freedesktop.org
Subject: Re: RFC: hardware accelerated bitblt using dma engine
Date: Fri, 5 Aug 2016 06:37:26 +0200 [thread overview]
Message-ID: <57A41806.6020106@gr13.net> (raw)
In-Reply-To: <57A3CCE7.8070509@gr13.net>
On 05.08.2016 01:16, Enrico Weigelt, metux IT consult wrote:
<snip>
Seems I've been on a completely wrong path - what I'm looking
for is dma-buf. So my idea now goes like this:
* add a new 'virtual GPU' as render node.
* the basic operations are:
-> create a virtual dumb framebuffer (just inside system memory),
-> import dma-buf's as bo's
-> blitting between bo's using dma-engine
That way, everything should be cleanly separated.
As the application needs to be aware of that buffer-and-blit approach
anyways (IOW: allocate two BO's and trigger the blitting when it done
rendering), the extra glue needed for opening and talking to the
render node should be quite minimal.
--mtx
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-08-05 4:37 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 [this message]
2016-08-05 7:49 ` Daniel Vetter
2016-08-05 7:47 ` Daniel Vetter
2016-08-03 23:19 ` Enrico Weigelt, metux IT consult
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=57A41806.6020106@gr13.net \
--to=enrico.weigelt@gr13.net \
--cc=dri-devel@lists.freedesktop.org \
/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.