Home
last modified time | relevance | path

Searched +full:simple +full:- +full:framebuffer (Results 1 – 20 of 20) sorted by relevance

/Documentation/devicetree/bindings/display/
Dsimple-framebuffer.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/simple-framebuffer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Simple Framebuffer
10 - Hans de Goede <hdegoede@redhat.com>
13 A simple frame-buffer describes a frame-buffer setup by firmware or
19 sub-nodes of the chosen node (*). Simplefb nodes must be named
20 framebuffer@<address>.
41 interaction, then the chosen node stdout-path property should point
[all …]
Dxylon,logicvc-display.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/display/xylon,logicvc-display.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Paul Kocialkowski <paul.kocialkowski@bootlin.com>
16 with Xilinx Zynq-7000 SoCs and Xilinx FPGAs.
20 synthesis time. As a result, many of the device-tree bindings are meant to
24 Layers are declared in the "layers" sub-node and have dedicated configuration.
26 starting from the video memory base address for its framebuffer. In version 4,
32 - xylon,logicvc-3.02.a-display
[all …]
/Documentation/devicetree/bindings/
Dxilinx.txt10 Each IP-core has a set of parameters which the FPGA designer can use to
20 properties of the device node. In general, device nodes for IP-cores
23 (name): (generic-name)@(base-address) {
24 compatible = "xlnx,(ip-core-name)-(HW_VER)"
27 interrupt-parent = <&interrupt-controller-phandle>;
29 xlnx,(parameter1) = "(string-value)";
30 xlnx,(parameter2) = <(int-value)>;
33 (generic-name): an open firmware-style name that describes the
36 (ip-core-name): the name of the ip block (given after the BEGIN
38 and all underscores '_' converted to dashes '-'.
[all …]
/Documentation/fb/
Dudlfb.rst7 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
[all …]
Dframebuffer.rst9 ---------------
13 software to access the graphics hardware through a well-defined interface, so
14 the software doesn't need to know anything about the low-level (hardware
22 --------------------------
39 /dev/fb0current -> fb0
40 /dev/fb1current -> fb1
50 graphics card in addition to the built-in hardware. The corresponding frame
56 $FRAMEBUFFER to the path name of a frame buffer device, e.g. (for sh/bash
59 export FRAMEBUFFER=/dev/fb1
63 setenv FRAMEBUFFER /dev/fb1
[all …]
Dvesafb.rst5 This is a generic driver for a graphic framebuffer on intel boxes.
7 The idea is simple: Turn on graphics mode at boot time with the help
8 of the BIOS, and use this as framebuffer device /dev/fb0, like the m68k
20 * You can run XF68_FBDev on top of /dev/fb0 (=> non-accelerated X11
22 * Most important: boot logo :-)
33 Documentation/admin-guide/svga.rst for details.
81 "vga=mode-number" you have to transform the numbers to decimal.
88 XF68_FBDev should work just fine, but it is non-accelerated. Running
89 another (accelerated) X-Server like XF86_SVGA might or might not work.
90 It depends on X-Server and graphics board.
[all …]
Dviafb.rst2 VIA Integration Graphic Chip Console Framebuffer Driver
6 --------
7 The console framebuffer driver is for graphics chips of
15 ---------------
34 ----------------------
47 - 640x480 (default)
48 - 720x480
49 - 800x600
50 - 1024x768
53 - 8, 16, 32 (default:32)
[all …]
/Documentation/gpu/amdgpu/display/
Dindex.rst1 .. _amdgpu-display-core:
4 drm/amd/display - Display Core (DC)
10 #. **Display Core (DC)** contains the OS-agnostic components. Things like
12 #. **Display Manager (DM)** contains the OS-dependent components. Hooks to the
16 ------------------
18 ------------------
30 `amd-staging-drm-next <https://gitlab.freedesktop.org/agd5f/linux>`_. All of
36 error, a developer will debug as fast as possible; usually, a simple bisect
60 * Cross-compilation for PowerPC 64/32, ARM 64/32, and x86 32.
65 #. In terms of userspace, we only use fully updated open-source components
[all …]
/Documentation/admin-guide/media/
Divtv.rst1 .. SPDX-License-Identifier: GPL-2.0
11 Hauppauge PVR-350.
29 --------
32 S-Video/Composite and audio line-in.
41 Additional features for the PVR-350 (CX23415 based)
42 ---------------------------------------------------
47 * Provides a framebuffer (allowing X applications to appear on the video
55 --------
60 ---
64 ----------------------------------------------------------
[all …]
Dvivid.rst1 .. SPDX-License-Identifier: GPL-2.0
9 simple framebuffer device is available for testing capture and output overlays.
13 Each input can be a webcam, TV capture device, S-Video capture device or an HDMI
14 capture device. Each output can be an S-Video output device or an HDMI output
23 - Support for read()/write(), MMAP, USERPTR and DMABUF streaming I/O.
24 - A large list of test patterns and variations thereof
25 - Working brightness, contrast, saturation and hue controls
26 - Support for the alpha color component
27 - Full colorspace support, including limited/full RGB range
28 - All possible control types are present
[all …]
Dbttv.rst1 .. SPDX-License-Identifier: GPL-2.0
8 ----------------------
12 ./scripts/config -e PCI
13 ./scripts/config -m I2C
14 ./scripts/config -m INPUT
15 ./scripts/config -m MEDIA_SUPPORT
16 ./scripts/config -e MEDIA_PCI_SUPPORT
17 ./scripts/config -e MEDIA_ANALOG_TV_SUPPORT
18 ./scripts/config -e MEDIA_DIGITAL_TV_SUPPORT
19 ./scripts/config -e MEDIA_RADIO_SUPPORT
[all …]
/Documentation/gpu/
Ddrm-kms-helpers.rst21 the same set of common helper vtables. For really simple drivers (anything
23 also the simple display pipe helpers.
27 for handling panel-related information and logic. Plus then a big set of
39 .. kernel-doc:: include/drm/drm_modeset_helper_vtables.h
42 .. kernel-doc:: include/drm/drm_modeset_helper_vtables.h
51 --------
53 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c
57 ---------------------------------------
59 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c
63 --------------------------
[all …]
Dtodo.rst11 ----------
29 Subsystem-wide refactorings
33 ---------------------------------------------
45 --------------------------------------------------
53 non-converted driver. The "Atomic mode setting design overview" series [2]_
60 .. [1] https://blog.ffwll.ch/2014/11/atomic-modeset-support-for-kms-drivers.html
69 ---------------------------------------------------------
75 avoid confusion - the other helpers in that file are all deprecated legacy
83 ----------------------------------
88 - drm_plane_helper_funcs->atomic_check gets called for enabled or disabled
[all …]
Dtegra.rst11 supports the built-in GPU, comprised of the gr2d and gr3d engines. Starting
18 - A host1x driver that provides infrastructure and access to the host1x
21 - A KMS driver that supports the display controllers as well as a number of
24 - A set of custom userspace IOCTLs that can be used to submit jobs to the
40 device using a driver-provided function which will set up the bits specific to
48 -------------------------------
50 .. kernel-doc:: include/linux/host1x.h
52 .. kernel-doc:: drivers/gpu/host1x/bus.c
56 --------------------------
58 .. kernel-doc:: drivers/gpu/host1x/syncpt.c
[all …]
/Documentation/driver-api/media/
Dv4l2-device.rst1 .. SPDX-License-Identifier: GPL-2.0
4 --------------------
7 Very simple devices can just allocate this struct, but most of the time you
16 dev->driver_data field is ``NULL``, it will be linked to
20 dev->driver_data manually to point to the driver-specific device structure
26 If :c:type:`v4l2_dev <v4l2_device>`\ ->name is empty then it will be set to a
30 :c:type:`v4l2_dev <v4l2_device>`\ ->name before calling
34 name and a driver-global atomic_t instance. This will generate names like
36 a dash: ``cx18-0``, ``cx18-1``, etc. This function returns the instance number.
44 You can also supply a ``notify()`` callback that can be called by sub-devices
[all …]
/Documentation/process/
Dbotching-up-ioctls.rst5 From: https://blog.ffwll.ch/2013/11/botching-up-ioctls.html
13 Which is nice, since there's no more insanity in the form of fake-generic, but
19 only cover technicalities and not the big-picture issues like what the command
25 -------------
28 will need to add a 32-bit compat layer:
33 * Align everything to the natural size and use explicit padding. 32-bit
34 platforms don't necessarily align 64-bit values to 64-bit boundaries, but
35 64-bit platforms do. So we always need padding to the natural size to get
38 * Pad the entire struct to a multiple of 64-bits if the structure contains
39 64-bit types - the structure size will otherwise differ on 32-bit versus
[all …]
/Documentation/driver-api/dmaengine/
Dprovider.rst20 DMA-eligible devices to the controller itself. Whenever the device
24 A very simple DMA controller would only take into account a single
32 physical bus allows to maximize performances when doing a simple
44 transfer into smaller sub-transfers.
49 non-contiguous buffers to a contiguous buffer, which is called
50 scatter-gather.
53 scatter-gather. So we're left with two cases here: either we have a
54 quite simple DMA controller that doesn't support it, and we'll have to
56 that implements in hardware scatter-gather.
79 These were just the general memory-to-memory (also called mem2mem) or
[all …]
/Documentation/userspace-api/
Ddma-buf-alloc-exchange.rst1 .. SPDX-License-Identifier: GPL-2.0
2 .. Copyright 2021-2023 Collabora Ltd.
9 support for sharing pixel-buffer allocations between processes, devices, and
12 approach this sharing for two-dimensional image data.
25 Conceptually a two-dimensional array of pixels. The pixels may be stored
30 A span along a single y-axis value, e.g. from co-ordinates (0,100) to
37 A span along a single x-axis value, e.g. from co-ordinates (100,0) to
46 A two-dimensional array of some or all of an image's color and alpha
80 A value that denotes the relationship between pixel-location co-ordinates
81 and byte-offset values. Typically used as the byte offset between two
[all …]
/Documentation/userspace-api/media/v4l/
Dhist-v4l2.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _hist-v4l2:
21 1998-08-20: First version.
23 1998-08-27: The :c:func:`select()` function was introduced.
25 1998-09-10: New video standard interface.
27 1998-09-18: The ``VIDIOC_NONCAP`` ioctl was replaced by the otherwise
36 1998-09-28: Revamped video standard. Made video controls individually
39 1998-10-02: The ``id`` field was removed from
47 1998-11-08: Many minor changes. Most symbols have been renamed. Some
50 1998-11-12: The read/write direction of some ioctls was misdefined.
[all …]
/Documentation/admin-guide/
Dkernel-parameters.txt16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
41 If set to vendor, prefer vendor-specific driver
73 Documentation/firmware-guide/acpi/debug.rst for more information about
[all …]