Home
last modified time | relevance | path

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

12345678

/linux/Documentation/userspace-api/media/v4l/
H A Dvidioc-g-fbuf.rst39 to get and set the framebuffer parameters for a
62 :c:type:`v4l2_framebuffer`. Since the framebuffer is
66 framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>` does, or it returns an error
72 the overlay and returns the framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>`
90 :ref:`framebuffer-cap`.
95 :ref:`framebuffer-flags`
99 - Physical base address of the framebuffer, that is the address of
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.
[all …]
H A Ddev-osd.rst12 Some video output devices can overlay a framebuffer image onto the
39 Contrary to the *Video Overlay* interface the framebuffer is normally
41 accessible as a framebuffer device (``/dev/fbN``). Given a V4L2 device,
42 applications can find the corresponding framebuffer device by calling
44 other information, the physical address of the framebuffer in the
46 The framebuffer device ioctl ``FBIOGET_FSCREENINFO`` returns the same
52 The width and height of the framebuffer depends on the current video
54 (or any other ioctl which would imply a framebuffer size change) with an
55 ``EBUSY`` error code until all applications closed the framebuffer device.
57 Example: Finding a framebuffer device for OSD
[all …]
/linux/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
67 The physical address of the framebuffer can be controlled using the
71 EP93XXFB_USE_SDCSN0 Use SDCSn[0] for the framebuffer. This
74 EP93XXFB_USE_SDCSN1 Use SDCSn[1] for the framebuffer.
76 EP93XXFB_USE_SDCSN2 Use SDCSn[2] for the framebuffer.
78 EP93XXFB_USE_SDCSN3 Use SDCSn[3] for the framebuffer.
84 The EP93xx framebuffer driver supports three optional platform
86 are called when the framebuffer driver is installed and removed
99 /* Board specific framebuffer setup */
[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.
52 * Fbcon assumes the first framebuffer it finds should be consumed for console.
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.
[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/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/arch/arm/boot/dts/mediatek/
H A Dmt6572-lenovo-a369i.dts22 framebuffer: framebuffer@9fa00000 { label
23 compatible = "simple-framebuffer";
47 framebuffer_reserved: framebuffer@9fa00000 {
H A Dmt6572-jty-d101.dts22 framebuffer: framebuffer@bf400000 { label
23 compatible = "simple-framebuffer";
52 framebuffer_reserved: framebuffer@bf400000 {
H A Dmt6582-alcatel-yarisxl.dts22 framebuffer: framebuffer@9fa00000 { label
23 compatible = "simple-framebuffer";
52 framebuffer_reserved: framebuffer@9fa00000 {
/linux/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/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 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 Ds800-0-3-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 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";
H A Dt8103-jxxx.dtsi27 framebuffer0: framebuffer@0 {
28 compatible = "apple,simple-framebuffer", "simple-framebuffer";
/linux/Documentation/arch/arm/omap/
H A Ddss.rst42 The DSS driver does not itself have any support for Linux framebuffer, V4L or
121 From omapdss point of view the V4L2 drivers should be similar to framebuffer
133 screen. The overlay may be smaller than framebuffer, thus displaying only
134 part of the framebuffer. The position of the overlay may be changed if
140 A framebuffer can be connected to multiple overlays to show the same pixel data
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
[all …]
/linux/Documentation/devicetree/bindings/display/
H A Dgoogle,goldfish-fb.txt1 Android Goldfish framebuffer
3 Android Goldfish framebuffer device used by Android emulator.
/linux/arch/arm64/boot/dts/exynos/
H A Dexynos2200-g0s.dts24 framebuffer: framebuffer { label
25 compatible = "simple-framebuffer";
78 cont_splash_mem: framebuffer@f6200000 {

12345678