From: Pekka Paalanen <ppaalanen@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: How to design a DRM KMS driver exposing 2D compositing?
Date: Tue, 12 Aug 2014 10:10:21 +0300 [thread overview]
Message-ID: <20140812101021.7ec2f8c1@gmail.com> (raw)
In-Reply-To: <20140811153530.GR10500@phenom.ffwll.local>
On Mon, 11 Aug 2014 17:35:31 +0200
Daniel Vetter <daniel@ffwll.ch> wrote:
> Well for other drivers/stacks we'd fall back to GL compositing. pixman
> would obviously be terribly. Curious question: Can you provoke the
> hw/firmware to render into abitrary buffers or does it only work together
> with real display outputs?
Since we have been talking about on-line (direct to output) and
off-line (buffer target) use of the HVS (2D compositing engine), it
should be able to do both I think.
> So I guess the real question is: What kind of interface does videocore
> provide? Note that kms framebuffers are super-flexible and you're freee to
> add your own ioctl for special framebuffers which are rendered live by the
> vc. So that might be a possible way to expose this if you can't tell the
> vc which buffers to render into explicitly.
Right. I don't know the HVS details yet, but I'm hoping we can tell
it to render into a custom buffer, like the 3D core can.
This discussion is very helpful btw, I'm starting to see some possible
plans.
Thanks,
pq
next prev parent reply other threads:[~2014-08-12 7:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 10:38 How to design a DRM KMS driver exposing 2D compositing? Pekka Paalanen
2014-08-11 10:57 ` Damien Lespiau
2014-08-11 12:07 ` Pekka Paalanen
2014-08-11 13:14 ` Damien Lespiau
2014-08-11 13:44 ` Pekka Paalanen
2014-08-11 12:06 ` Daniel Vetter
2014-08-11 12:47 ` Pekka Paalanen
2014-08-11 15:35 ` Daniel Vetter
2014-08-11 16:09 ` Ville Syrjälä
2014-08-11 17:21 ` Daniel Vetter
2014-08-12 7:10 ` Pekka Paalanen [this message]
2014-08-11 13:32 ` Rob Clark
2014-08-11 15:24 ` Daniel Vetter
2014-08-12 7:20 ` Pekka Paalanen
2014-08-12 8:03 ` Daniel Vetter
2014-08-12 10:04 ` Ville Syrjälä
2014-08-11 17:16 ` Eric Anholt
2014-08-11 17:27 ` Daniel Vetter
2014-08-12 8:48 ` Pekka Paalanen
2014-08-12 16:10 ` Eric Anholt
2014-08-13 7:02 ` Pekka Paalanen
2014-08-11 14:37 ` Matt Roper
2014-08-12 8:42 ` Pekka Paalanen
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=20140812101021.7ec2f8c1@gmail.com \
--to=ppaalanen@gmail.com \
--cc=daniel@ffwll.ch \
--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.