Home
last modified time | relevance | path

Searched refs:framebuffer (Results 1 – 25 of 237) sorted by relevance

12345678910

/linux-6.15/Documentation/devicetree/bindings/display/
H A Dsimple-framebuffer.yaml20 framebuffer@<address>.
62 - apple,simple-framebuffer
63 - allwinner,simple-framebuffer
64 - amlogic,simple-framebuffer
65 - const: simple-framebuffer
66 - const: simple-framebuffer
96 Format of the framebuffer:
168 const: allwinner,simple-framebuffer
178 const: amlogic,simple-framebuffer
198 framebuffer0: framebuffer@1d385000 {
[all …]
H A Dgoogle,goldfish-fb.txt1 Android Goldfish framebuffer
3 Android Goldfish framebuffer device used by Android emulator.
/linux-6.15/Documentation/fb/
H A Dep93xx-fb.rst26 are in pixel clocks. See Documentation/fb/framebuffer.rst for further
39 The framebuffer device can be registered by adding the following to
68 The physical address of the framebuffer can be controlled using the
72 EP93XXFB_USE_SDCSN0 Use SDCSn[0] for the framebuffer. This
75 EP93XXFB_USE_SDCSN1 Use SDCSn[1] for the framebuffer.
77 EP93XXFB_USE_SDCSN2 Use SDCSn[2] for the framebuffer.
79 EP93XXFB_USE_SDCSN3 Use SDCSn[3] for the framebuffer.
86 The EP93xx framebuffer driver supports three optional platform
88 are called when the framebuffer driver is installed and removed
101 /* Board specific framebuffer setup */
[all …]
H A Dfbcon.rst5 The framebuffer console (fbcon), as its name implies, is a text
6 console running on top of the framebuffer device. It has the functionality of
8 features that can be attributed to the graphical nature of the framebuffer.
10 In the x86 architecture, the framebuffer console is optional, and
14 What are the features of fbcon? The framebuffer console supports
22 The framebuffer console can be enabled by using your favorite kernel
28 In order for fbcon to activate, at least one framebuffer driver is
78 The framebuffer console has several, largely unknown, boot options
109 Later on, when you want to map the console the to the framebuffer
144 use the framebuffer will remain at their 'normal' orientation.
[all …]
H A Ddeferred_io.rst10 - userspace app like Xfbdev mmaps framebuffer
20 completes the work associated with updating the framebuffer. this is
25 As can be seen from above, one benefit is roughly to allow bursty framebuffer
27 have gone quiet, we go and really update the framebuffer which would be
38 Another one may be if one has a device framebuffer that is in an usual format,
40 apps to pretend to have a normal framebuffer but reswizzle for the device
41 framebuffer at vsync time based on the touched pagelist.
45 No changes needed. mmap the framebuffer like normal and just use it.
H A Dudlfb.rst8 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
32 Advantages of supporting DisplayLink chips with kernel framebuffer interface:
44 * Fbdev's mmap interface assumes a real hardware framebuffer is mapped.
51 * Fbdev does not arbitrate client ownership of the framebuffer well.
67 to open and begin writing to the framebuffer of the DisplayLink device using
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.
125 shadow Allocate a 2nd framebuffer to shadow what's currently across
[all …]
H A Dpxafb.rst88 base framebuffer (although under-neath the base is also possible). They
91 behave in a similar way as a framebuffer.
97 framebuffer, which means they have a start (x, y). This information
101 2. overlay framebuffer is allocated dynamically according to specified
134 framebuffer:
152 framebuffer framework, application has to take care of the offsets
153 and lengths of each component within the framebuffer.
/linux-6.15/Documentation/userspace-api/media/v4l/
H A Ddev-osd.rst11 Some video output devices can overlay a framebuffer image onto the
38 Contrary to the *Video Overlay* interface the framebuffer is normally
40 accessible as a framebuffer device (``/dev/fbN``). Given a V4L2 device,
41 applications can find the corresponding framebuffer device by calling
43 other information, the physical address of the framebuffer in the
45 The framebuffer device ioctl ``FBIOGET_FSCREENINFO`` returns the same
51 The width and height of the framebuffer depends on the current video
56 Example: Finding a framebuffer device for OSD
95 /* Apparently not a framebuffer device. */
102 /* fb_fd is the file descriptor of the framebuffer device
[all …]
H A Dvidioc-g-fbuf.rst39 to get and set the framebuffer parameters for a
62 :c:type:`v4l2_framebuffer`. Since the framebuffer is
90 :ref:`framebuffer-cap`.
95 :ref:`framebuffer-flags`
100 the pixel in the top left corner of the framebuffer.
105 find the corresponding Linux framebuffer device (see
123 - The pixel format of the framebuffer.
183 Together with ``base`` it defines the framebuffer memory
290 framebuffer pixels with video images. The blend function is:
305 framebuffer to clip or blend framebuffer pixels with video images,
[all …]
/linux-6.15/drivers/video/fbdev/geode/
H A DKconfig3 # Geode family framebuffer configuration
6 bool "AMD Geode family framebuffer support"
10 Say 'Y' here to allow you to select framebuffer drivers for
14 tristate "AMD Geode LX framebuffer support"
27 tristate "AMD Geode GX framebuffer support"
40 tristate "AMD Geode GX1 framebuffer support"
/linux-6.15/drivers/gpu/drm/tegra/
H A Dfb.c20 struct tegra_bo *tegra_fb_get_plane(struct drm_framebuffer *framebuffer, in tegra_fb_get_plane() argument
23 return to_tegra_bo(drm_gem_fb_get_obj(framebuffer, index)); in tegra_fb_get_plane()
26 bool tegra_fb_is_bottom_up(struct drm_framebuffer *framebuffer) in tegra_fb_is_bottom_up() argument
28 struct tegra_bo *bo = tegra_fb_get_plane(framebuffer, 0); in tegra_fb_is_bottom_up()
36 int tegra_fb_get_tiling(struct drm_framebuffer *framebuffer, in tegra_fb_get_tiling() argument
39 uint64_t modifier = framebuffer->modifier; in tegra_fb_get_tiling()
/linux-6.15/drivers/media/pci/ivtv/
H A DKconfig49 tristate "Conexant cx23415 framebuffer support"
53 This is a framebuffer driver for the Conexant cx23415 MPEG
62 bool "force cx23415 framebuffer init with x86 PAT enabled"
65 With PAT enabled, the cx23415 framebuffer driver does not
66 utilize write-combined caching on the framebuffer memory.
75 With this setting enabled, the framebuffer will initialize on
76 PAT-enabled systems but the framebuffer memory will be uncached.
/linux-6.15/arch/arm64/boot/dts/apple/
H A Dt8012-touchbar.dtsi12 framebuffer0: framebuffer@0 {
13 compatible = "apple,simple-framebuffer", "simple-framebuffer";
H A Dt7000-handheld.dtsi16 framebuffer0: framebuffer@0 {
17 compatible = "apple,simple-framebuffer", "simple-framebuffer";
H A Dt7000-j42d.dts20 framebuffer0: framebuffer@0 {
21 compatible = "apple,simple-framebuffer", "simple-framebuffer";
H A Dt8011-common.dtsi22 framebuffer0: framebuffer@0 {
23 compatible = "apple,simple-framebuffer", "simple-framebuffer";
H A Ds5l8960x-common.dtsi24 framebuffer0: framebuffer@0 {
25 compatible = "apple,simple-framebuffer", "simple-framebuffer";
H A Ds8001-common.dtsi24 framebuffer0: framebuffer@0 {
25 compatible = "apple,simple-framebuffer", "simple-framebuffer";
H A Dt8015-common.dtsi24 framebuffer0: framebuffer@0 {
25 compatible = "apple,simple-framebuffer", "simple-framebuffer";
H A Dt8010-common.dtsi24 framebuffer0: framebuffer@0 {
25 compatible = "apple,simple-framebuffer", "simple-framebuffer";
H A Ds800-0-3-common.dtsi24 framebuffer0: framebuffer@0 {
25 compatible = "apple,simple-framebuffer", "simple-framebuffer";
H A Dt8112-jxxx.dtsi25 framebuffer0: framebuffer@0 {
26 compatible = "apple,simple-framebuffer", "simple-framebuffer";
H A Dt7001-air2.dtsi20 framebuffer0: framebuffer@0 {
21 compatible = "apple,simple-framebuffer", "simple-framebuffer";
/linux-6.15/drivers/video/console/
H A DKconfig81 Low-level framebuffer-based console driver.
89 This option enables the fbcon (framebuffer text-based) hardware
108 If this option is selected, the framebuffer console will
110 supports this feature). Otherwise, the framebuffer console will
111 always select the first framebuffer driver that is loaded. The latter
123 Enable display rotation for the framebuffer console. This is done
126 such that other users of the framebuffer will remain normally
133 If enabled this defers the framebuffer console taking over the
136 commandline option to keep the framebuffer contents initially put up
/linux-6.15/Documentation/arch/arm/omap/
H A Ddss.rst42 The DSS driver does not itself have any support for Linux framebuffer, V4L or
143 framebuffer can be connected to any overlay.
169 overlays List of overlay numbers to which framebuffer pixels go
170 phys_addr Physical address of the framebuffer
171 virt_addr Virtual address of the framebuffer
172 size Size of the framebuffer
176 input_size width,height (ie. the framebuffer size)
310 framebuffer parameters.
322 - VRAM allocated for a framebuffer. Normally omapfb allocates vram
324 more or define the physical address of each framebuffer. For example,
[all …]

12345678910