Home
last modified time | relevance | path

Searched +full:simple +full:- +full:framebuffer (Results 1 – 18 of 18) 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 Device Tree Bindings
10 - Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
11 - Hans de Goede <hdegoede@redhat.com>
14 A simple frame-buffer describes a frame-buffer setup by firmware or
20 sub-nodes of the chosen node (*). Simplefb nodes must be named
21 framebuffer@<address>.
[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/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/media/v4l-drivers/
Dvivid.rst1 .. SPDX-License-Identifier: GPL-2.0
8 defined radio receiver. In addition a simple framebuffer device is available for
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 …]
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 …]
Dbttv.rst1 .. SPDX-License-Identifier: GPL-2.0
7 ----------------------
11 .. code-block:: none
21 -----------------------------
34 .. code-block:: none
36 options i2c-algo-bit bit_test=1
39 hcwamc.rbf. The file is in the pvr45xxx.exe archive (self-extracting
45 audio work, you should read the Sound-FAQ.
49 -------------------
54 .. code-block:: none
[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 …]
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 …]
Dtodo.rst10 Subsystem-wide refactorings
14 ---------------------------------------------
24 --------------------------------------------------
32 non-converted driver (again virtual HW drivers for KVM are still all
42 ---------------------------------------------------------
48 avoid confusion - the other helpers in that file are all deprecated legacy
54 ----------------------------------------------------
57 nonblocking commits, and every driver had to hand-roll them. This is fixed
67 -----------------------
72 a bit too severe. So there's some follow-up work to adjust the function
[all …]
/Documentation/
Dbus-virt-phys-mapping.txt11 (see Documentation/DMA-API-HOWTO.txt). They continue
13 must not use them. --davidm 00/12/12
20 The AHA-1542 is a bus-master device, and your patch makes the driver give the
26 so-called "bus address".
29 that is, normal RAM--see later about other details):
31 - CPU untranslated. This is the "physical" address. Physical address
34 - CPU translated address. This is the "virtual" address, and is
38 - bus address. This is the address of memory as seen by OTHER devices,
40 addresses, with each device seeing memory in some device-specific way, but
46 address, and things are very simple indeed. However, they are that simple
[all …]
/Documentation/media/kapi/
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/devicetree/bindings/leds/
Dcommon.txt15 - led-sources : List of device current outputs the LED is connected to. The
19 - function: LED functon. Use one of the LED_FUNCTION_* prefixed definitions
20 from the header include/dt-bindings/leds/common.h.
23 - color : Color of the LED. Use one of the LED_COLOR_ID_* prefixed definitions
24 from the header include/dt-bindings/leds/common.h.
27 - function-enumerator: Integer to be used when more than one instance
31 - label : The label for this LED. If omitted, the label is taken from the node
34 label. This property is deprecated - use 'function' and 'color'
35 properties instead. function-enumerator has no effect when this
38 - default-state : The initial state of the LED. Valid values are "on", "off",
[all …]
/Documentation/ioctl/
Dbotching-up-ioctls.rst5 From: http://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/media/uapi/v4l/
Dhist-v4l2.rst4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
5 .. and no Back-Cover Texts. A copy of the license is included at
6 .. Documentation/media/uapi/fdl-appendix.rst.
8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
10 .. _hist-v4l2:
28 1998-08-20: First version.
30 1998-08-27: The :ref:`select() <func-select>` function was introduced.
32 1998-09-10: New video standard interface.
34 1998-09-18: The ``VIDIOC_NONCAP`` ioctl was replaced by the otherwise
35 meaningless ``O_TRUNC`` :ref:`open() <func-open>` flag, and the
[all …]
/Documentation/admin-guide/
Dkernel-parameters.txt5 force -- enable ACPI if default was off
6 on -- enable ACPI but allow fallback to DT [arm64]
7 off -- disable ACPI if default was on
8 noirq -- do not use ACPI for IRQ routing
9 strict -- Be less tolerant of platforms that are not
11 rsdt -- prefer RSDT over (default) XSDT
12 copy_dsdt -- copy DSDT to memory
56 Documentation/firmware-guide/acpi/debug.rst for more information about
119 Disable auto-serialization of AML methods
122 auto-serialization feature.
[all …]