* Adding X damage support to xf86-video-fbdev and standardizing ioctl
@ 2010-05-21 18:59 Bernie Thompson
0 siblings, 0 replies; only message in thread
From: Bernie Thompson @ 2010-05-21 18:59 UTC (permalink / raw)
To: linux-fbdev
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/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-05-21 18:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-21 18:59 Adding X damage support to xf86-video-fbdev and standardizing ioctl Bernie Thompson
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).