Home
last modified time | relevance | path

Searched full:framebuffer (Results 601 – 625 of 731) sorted by relevance

1...<<21222324252627282930

/linux-6.15/arch/arm64/boot/dts/qcom/
Dmsm8998-xiaomi-sagit.dts92 /* Bootloader display framebuffer region */
/linux-6.15/samples/vfio-mdev/
Dmdpy.c658 return sprintf(buf, "virtual display, %dx%d framebuffer\n", in mdpy_show_description()
/linux-6.15/drivers/video/fbdev/
Dleo.c679 MODULE_DESCRIPTION("framebuffer driver for LEO chipsets");
Dxen-fbfront.c697 MODULE_DESCRIPTION("Xen virtual framebuffer device frontend");
Dcarminefb.c792 MODULE_DESCRIPTION("Framebuffer driver for Fujitsu Carmine based devices");
Dpm3fb.c1341 * for the framebuffer. in pm3fb_probe()
1578 MODULE_DESCRIPTION("Permedia3 framebuffer device driver");
Doffb.c582 /* Ok, now we try to figure out the address of the framebuffer. in offb_init_nodriver()
/linux-6.15/drivers/hv/
Dring_buffer.c263 * atomic contexts, like panic path (see the Hyper-V framebuffer driver).
/linux-6.15/drivers/video/fbdev/mmp/hw/
Dmmp_ctrl.c576 MODULE_DESCRIPTION("Framebuffer driver for mmp");
/linux-6.15/drivers/gpu/drm/vc4/
Dvc4_render_cl.c28 * tiles of a framebuffer and optionally call out to binner-generated
/linux-6.15/tools/testing/selftests/powerpc/alignment/
Dalignment_handler.c611 printf("and either a usable framebuffer at /dev/fb0 or "); in usage()
/linux-6.15/drivers/video/fbdev/savage/
Dsavagefb_driver.c2 * linux/drivers/video/savagefb.c -- S3 Savage Framebuffer Driver
9 * Framebuffer framework code is based on code of cyber2000fb and tdfxfb.
1783 printk(KERN_INFO "savagefb: mapped framebuffer at %p, " in savage_map_video()
1791 /* Clear framebuffer, it's all white in memory after boot */ in savage_map_video()
/linux-6.15/drivers/gpu/drm/amd/display/amdgpu_dm/
Damdgpu_dm_crtc.c601 /* We need a framebuffer to be considered enabled. */ in amdgpu_dm_crtc_count_crtc_active_planes()
/linux-6.15/drivers/gpu/drm/
Ddrm_color_mgmt.c43 * from the framebuffer before it is given to the transformation matrix.
/linux-6.15/Documentation/driver-api/dmaengine/
Dprovider.rst175 ``glReadPielx()``, which might require a verbatim copy of a huge framebuffer
/linux-6.15/drivers/video/backlight/
Dbacklight.c87 * framebuffer driver. The backlight core only cares about FB_BLANK_UNBLANK
/linux-6.15/arch/arm/boot/dts/aspeed/
Daspeed-bmc-opp-swift.dts30 gfx_memory: framebuffer {
/linux-6.15/drivers/gpu/drm/gma500/
Doaktrail_crtc.c14 #include "framebuffer.h"
/linux-6.15/drivers/auxdisplay/
Dht16k33.c592 /* Framebuffer (2 bytes per column) */ in ht16k33_fbdev_probe()
/linux-6.15/drivers/gpu/drm/nouveau/
Dnouveau_chan.c213 * the framebuffer bar rather than direct vram access.. in nouveau_channel_prep()
Dnouveau_display.c280 DRM_DEBUG_KMS("Unsuitable framebuffer: format: %p4cc; pitches: 0x%x\n 0x%x\n", in nouveau_framebuffer_new()
/linux-6.15/drivers/mfd/
Dsm501.c1367 /* always create a framebuffer */ in sm501_init_dev()
1587 * so make the framebuffer swapped pixels */ in sm501_pci_probe()
/linux-6.15/drivers/video/fbdev/aty/
Daty128fb.c23 * - Convert to new framebuffer API,
2099 /* Virtualize the framebuffer */ in aty128_probe()
2410 * framebuffer before we put the chip to suspend state. On 2.4, I in aty128_pci_suspend_late()
/linux-6.15/Documentation/gpu/
Ddrm-mm.rst129 region, which provides space for the initial framebuffer and large,
/linux-6.15/Documentation/virt/kvm/x86/
Dmmu.rst33 and framebuffer-based displays

1...<<21222324252627282930