Lines Matching +full:simple +full:- +full:framebuffer

7 DisplayLink chips provide simple hline/blit operations with some compression,
8 pairing that with a hardware framebuffer (16MB) on the other end of the
9 USB wire.  That hardware framebuffer is able to drive the VGA, DVI, or HDMI
13 result with a local shadow of the remote hardware framebuffer to identify
15 pixels line-by-line via USB bulk transfers.
18 does not require any acks - the effect is very low latency that
20 non-gaming and non-video applications.
23 setting is very flexible - able to set nearly arbitrary modes from any timing.
32 Advantages of supporting DisplayLink chips with kernel framebuffer interface:
35    one-to-one with the fbdev interface, making the driver quite small and
44  * Fbdev's mmap interface assumes a real hardware framebuffer is mapped.
51  * Fbdev does not arbitrate client ownership of the framebuffer well.
52  * Fbcon assumes the first framebuffer it finds should be consumed for console.
66 At that point, a /dev/fb? interface will be present for user-mode applications
67 to open and begin writing to the framebuffer of the DisplayLink device using
71 defio support enabled, to support a page-fault based detection mechanism
74 The most common client of udlfb is xf86-video-displaylink or a modified
75 xf86-video-fbdev X server. These servers have no real DisplayLink specific
76 code. They write to the standard framebuffer interface and rely on udlfb
112 		module to track changed areas of the framebuffer by page faults.
122 		(e.g. X with --shared-vt) are in conflict.
125 shadow		Allocate a 2nd framebuffer to shadow what's currently across
136 Where ? is the sequential framebuffer id of the particular DisplayLink device
148 			 which can be passed to utilities like parse-edid.
150 metrics_bytes_rendered	 32-bit count of pixel bytes rendered
152 metrics_bytes_identical  32-bit count of how many of those bytes were found to be
153 			 unchanged, based on a shadow framebuffer check
155 metrics_bytes_sent	 32-bit count of how many bytes were transferred over
159 metrics_cpu_kcycles_used 32-bit count of CPU cycles used in processing the
162 metrics_reset		 Write-only. Any write to this file resets all metrics
163 			 above to zero.  Note that the 32-bit counters above