Lines Matching refs:to
9 USB wire. That hardware framebuffer is able to drive the VGA, DVI, or HDMI
10 monitor with no CPU involvement until a pixel has to change.
13 result with a local shadow of the remote hardware framebuffer to identify
23 setting is very flexible - able to set nearly arbitrary modes from any timing.
27 * Ability to add a nearly arbitrary number of displays to any USB 2.0
35 one-to-one with the fbdev interface, making the driver quite small and
36 tight relative to the functionality it provides.
38 from user mode to talk to the device, without needing to know anything
46 Writes need to be detected and encoded into USB bulk transfers by the CPU.
49 interface to allow mmap clients to report damage, for the benefit
55 How to use it?
59 DisplayLink chips (Alex and Ollie family). It will then attempt to read the EDID
67 to open and begin writing to the framebuffer of the DisplayLink device using
69 application must send down damage notifcations to trigger repaints of the
71 defio support enabled, to support a page-fault based detection mechanism
76 code. They write to the standard framebuffer interface and rely on udlfb
77 to do its thing. The one extra feature they have is the ability to report
78 rectangles from the X DAMAGE protocol extension down to udlfb via udlfb's
81 udlfb to efficiently process the changed pixels.
89 From the command line, pass options to modprobe
96 Unplug/replug USB device to apply with new settings
104 module to track changed areas of the framebuffer by page faults.
106 report damage, should be able to work with this enabled.
112 console Allow fbcon to attach to udlfb provided framebuffers.
117 shadow Allocate a 2nd framebuffer to shadow what's currently across
119 do not transmit. Spends host memory to save USB transfers.
129 edid If a valid EDID blob is written to this file (typically
132 attached to the DisplayLink device fails. This is
137 useful to get the EDID of the attached monitor,
138 which can be passed to utilities like parse-edid.
142 metrics_bytes_identical 32-bit count of how many of those bytes were found to be
146 USB to communicate the resulting changed pixels to the
152 metrics_reset Write-only. Any write to this file resets all metrics
153 above to zero. Note that the 32-bit counters above
155 performance tests to start and finish in a very short