From: Bernie Thompson <bernie@plugable.com>
To: linux-fbdev@vger.kernel.org
Subject: Adding X damage support to xf86-video-fbdev and standardizing ioctl
Date: Fri, 21 May 2010 18:59:21 +0000 [thread overview]
Message-ID: <AANLkTil4329qzpdruGtyBHNn4PrglyO7PUC04UNNxlZ8@mail.gmail.com> (raw)
For virtual framebuffers that need to shuffle pixels over a bus or
network, to be efficient they need to get notification of what pixels
are changing in the case of a memory mapped framebuffer.
This has come up before (Jaya/others have thought and talked about
this), and here's another example implementation (for DisplayLink USB
devices):
http://plugable.com/2010/05/21/linux-support-for-higher-res-monitors-on-lower-res-displaylink-devices/
This uses a hacked ioctl. But there's a commented out proposal in
there for cleaning it up.
It would be great to standardize the interface for passing damage
notifications (from X or other) down to kernel. Some open questions:
* Which ioctl ordinal could be reserved for this (maybe 'F' 0x1A?)
* What struct (just a single rect as above, or pass X damage struct
down directly?)
* User-configured (with X option as with implementation above), or
auto-negotiated between kernel and user?
Any thoughts or comments on this, and the feasibility of eventually
getting this into fbdev (and xf86-video-fbdev) are welcome.
Best wishes,
Bernie
http://plugable.com/
reply other threads:[~2010-05-21 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AANLkTil4329qzpdruGtyBHNn4PrglyO7PUC04UNNxlZ8@mail.gmail.com \
--to=bernie@plugable.com \
--cc=linux-fbdev@vger.kernel.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 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).