| /linux/drivers/firmware/ |
| H A D | Kconfig | 191 Firmwares often provide initial graphics framebuffers so the BIOS, 194 Extensions and EFI-framebuffers for this, which are mostly limited 196 This option, if enabled, marks VGA/VBE/EFI framebuffers as generic 197 framebuffers so the new generic system-framebuffer drivers can be 201 If this option is not selected, all system framebuffers are always 202 marked as fallback platform framebuffers as usual. 205 not be able to pick up generic system framebuffers if this option 208 with generic system framebuffers. But you should still keep vesafb
|
| /linux/Documentation/arch/arm/omap/ |
| H A D | dss.rst | 106 The omapfb driver implements arbitrary number of standard linux framebuffers. 107 These framebuffers can be routed flexibly to any overlays, thus allowing very 238 framebuffers, overlays, overlay managers, displays. Framebuffers are 336 - Use VRFB rotation for all framebuffers. 339 - Default rotation applied to all framebuffers. 346 - Default mirror for all framebuffers. Only works with DMA rotation.
|
| /linux/drivers/gpu/drm/ |
| H A D | drm_framebuffer.c | 59 * Framebuffers are tracked with &struct drm_framebuffer. They are published 67 * them again with drm_framebuffer_put(). For driver-private framebuffers for 322 * the 2nd version of the addfb ioctl, which supports multi-planar framebuffers 535 /* Multi-planar framebuffers need getfb2. */ in drm_mode_getfb() 598 /* For multi-plane framebuffers, we require the driver to place the in drm_mode_getfb2_ioctl() 600 * framebuffers, we can fall back to create_handle. in drm_mode_getfb2_ioctl() 941 * Drivers need to call this when cleaning up driver-private framebuffers, e.g. 946 * NOTE: This function is deprecated. For driver-private framebuffers it is not 971 * driver private framebuffers embedded into a larger structure. 978 * user-created framebuffers this will happen in the rmfb ioctl. For [all …]
|
| H A D | drm_gem_atomic_helper.c | 346 * drm_gem_begin_shadow_fb_access - prepares shadow framebuffers for CPU access 373 * drm_gem_end_shadow_fb_access - releases shadow framebuffers from CPU access 395 * drm_gem_simple_kms_begin_shadow_fb_access - prepares shadow framebuffers for CPU access 415 * drm_gem_simple_kms_end_shadow_fb_access - releases shadow framebuffers from CPU access
|
| /linux/include/linux/platform_data/ |
| H A D | simplefb.h | 32 * Data-Format for Simple-Framebuffers 50 * If the arch-boot code creates simple-framebuffers without DT support, it
|
| /linux/Documentation/fb/ |
| H A D | tgafb.rst | 5 This is a driver for DECChip 21030 based graphics framebuffers, a.k.a. TGA 29 This driver does not (yet) support the TGA2 family of framebuffers, so the
|
| H A D | udlfb.rst | 50 of virtual or remote framebuffers. 80 framebuffers that need damage info). These damage notifications allow 120 console Allow fbcon to attach to udlfb provided framebuffers.
|
| H A D | pxafb.rst | 93 However, there are some differences between these overlay framebuffers 94 and normal framebuffers, as listed below:
|
| /linux/include/linux/ |
| H A D | dio.h | 24 * like framebuffers. [0x400000-0x600000) is for miscellaneous internal I/O. 140 * In practice this is only important for framebuffers, 214 /* These are the secondary IDs for the framebuffers */
|
| H A D | aperture.h | 48 * aperture_remove_all_conflicting_devices - remove all existing framebuffers
|
| /linux/drivers/video/ |
| H A D | aperture.c | 310 * PCI graphics device with framebuffers in non-BAR locations. Drivers 314 * If your hardware has its framebuffers accessible via PCI BARS, use 336 * aperture_remove_conflicting_pci_devices - remove existing framebuffers for PCI devices
|
| /linux/drivers/gpu/drm/i915/display/ |
| H A D | intel_dpt.c | 191 * Restore the memory mapping during system resume for all framebuffers which 220 * Suspend the memory mapping during system suspend for all framebuffers which
|
| /linux/include/drm/ |
| H A D | drm_framebuffer.h | 276 * drm_for_each_fb - iterate over all framebuffers 280 * Iterate over all framebuffers of @dev. User must hold
|
| H A D | drm_gem_atomic_helper.h | 76 * for framebuffers with non-zero offset fields.
|
| /linux/Documentation/driver-api/firmware/ |
| H A D | other_interfaces.rst | 16 Generic System Framebuffers Interface
|
| /linux/arch/mips/include/asm/ |
| H A D | fixmap.h | 45 * future, say framebuffers for the console driver(s) could be
|
| /linux/arch/sh/include/asm/ |
| H A D | fixmap.h | 39 * future, say framebuffers for the console driver(s) could be
|
| /linux/Documentation/gpu/amdgpu/display/ |
| H A D | mpo-overview.rst | 9 Multiplane Overlay (MPO) allows for multiple framebuffers to be composited via 116 prepare the framebuffers for the planes as follows:
|
| /linux/drivers/gpu/drm/mxsfb/ |
| H A D | mxsfb_drv.c | 359 * Remove early framebuffers (ie. simplefb). The framebuffer can be in mxsfb_probe() 365 "can't kick out existing framebuffers\n"); in mxsfb_probe()
|
| /linux/include/uapi/linux/ |
| H A D | major.h | 55 #define FB_MAJOR 29 /* /dev/fb* framebuffers */
|
| /linux/drivers/of/ |
| H A D | platform.c | 533 * For OF framebuffers, first create the device for the boot display, in of_platform_default_populate_init() 534 * then for the other framebuffers. Only fail for the boot display; in of_platform_default_populate_init() 579 * here, disable the Generic System Framebuffers (sysfb) in of_platform_default_populate_init()
|
| /linux/arch/arm/include/uapi/asm/ |
| H A D | setup.h | 101 /* initial values for vesafb-type framebuffers. see struct screen_info
|
| /linux/drivers/gpu/drm/sti/ |
| H A D | NOTES | 41 - The Framebuffers and planes are mapped to the Compositor GDP (non video
|
| /linux/drivers/video/fbdev/ |
| H A D | macfb.c | 331 * which can act as separate framebuffers for doing video 333 * Can add another 1MB RAM to give the two framebuffers 818 * them have separate framebuffers for external and in macfb_init()
|
| /linux/Documentation/gpu/ |
| H A D | zynqmp.rst | 8 supports in-memory framebuffers with the DisplayPort DMA controller
|