Home
last modified time | relevance | path

Searched full:fb0 (Results 1 – 25 of 67) sorted by relevance

123

/kernel/linux/linux-6.6/drivers/staging/sm750fb/
Dreadme19 it will create fb0 and fb1 (or fb1,fb2 if fb0 already exist) under /dev
36 if you have vesafb enabled in your config then /dev/fb0 will be created by vesafb
/kernel/linux/linux-5.10/drivers/staging/sm750fb/
Dreadme19 it will create fb0 and fb1 (or fb1,fb2 if fb0 already exist) under /dev
36 if you have vesafb enabled in your config then /dev/fb0 will be created by vesafb
/kernel/linux/linux-6.6/Documentation/arch/arm/omap/
Ddss.rst229 fb0=/sys/class/graphics/fb0
241 FB0 --- GFX -\ DVI
255 fbset -fb /dev/fb0 -xres $w -yres $h -vxres $w -vyres $h
262 FB0 --- GFX -\ -- DVI
278 echo "0,1" > $fb0/overlays
290 FB0 +-- GFX ---- LCD ---- LCD
/kernel/linux/linux-5.10/Documentation/arm/omap/
Ddss.rst229 fb0=/sys/class/graphics/fb0
241 FB0 --- GFX -\ DVI
255 fbset -fb /dev/fb0 -xres $w -yres $h -vxres $w -vyres $h
262 FB0 --- GFX -\ -- DVI
278 echo "0,1" > $fb0/overlays
290 FB0 +-- GFX ---- LCD ---- LCD
/kernel/linux/linux-5.10/Documentation/fb/
Dframebuffer.rst31 0 = /dev/fb0 First frame buffer
39 /dev/fb0current -> fb0
47 cp /dev/fb0 myfile
51 buffer devices (/dev/fb0 and /dev/fb1 etc.) work independently.
54 use /dev/fb0 by default (older software uses /dev/fb0current). You can specify
138 up in the resolution determined by /dev/fb0 (or $FRAMEBUFFER, if set). You
Dvesafb.rst8 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
Dgxfb.rst15 * You can run XF68_FBDev on top of /dev/fb0
Dlxfb.rst16 * You can run XF68_FBDev on top of /dev/fb0
Dpvr2fb.rst12 * You can run XF86_FBDev on top of /dev/fb0
Daty128fb.rst14 * You can run XF68_FBDev on top of /dev/fb0
/kernel/linux/linux-6.6/Documentation/fb/
Dframebuffer.rst31 0 = /dev/fb0 First frame buffer
39 /dev/fb0current -> fb0
47 cp /dev/fb0 myfile
51 buffer devices (/dev/fb0 and /dev/fb1 etc.) work independently.
54 use /dev/fb0 by default (older software uses /dev/fb0current). You can specify
138 up in the resolution determined by /dev/fb0 (or $FRAMEBUFFER, if set). You
Dvesafb.rst8 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
Dlxfb.rst16 * You can run XF68_FBDev on top of /dev/fb0
Dgxfb.rst15 * You can run XF68_FBDev on top of /dev/fb0
Dpvr2fb.rst12 * You can run XF86_FBDev on top of /dev/fb0
Daty128fb.rst14 * You can run XF68_FBDev on top of /dev/fb0
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/
Datmel,lcdc.txt30 fb0: fb@00500000 {
44 fb0: fb@00500000 {
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/
Datmel,lcdc.txt29 fb0: fb@00500000 {
43 fb0: fb@00500000 {
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/reserved-memory/
Dmemory-region.yaml34 fb0: video@12300000 {
/kernel/linux/linux-6.6/Documentation/driver-api/
Dsm501.rst52 given to it by aligning fb0 to the start of the area and fb1 to the end
/kernel/linux/linux-5.10/Documentation/driver-api/
Dsm501.rst52 given to it by aligning fb0 to the start of the area and fb1 to the end
/kernel/linux/linux-6.6/tools/testing/selftests/powerpc/alignment/
Dalignment_handler.c12 * the other cache-inhibited (by default we use /dev/fb0 for this, but an
57 char *cipath = "/dev/fb0";
611 printf("and either a usable framebuffer at /dev/fb0 or "); in usage()
/kernel/linux/linux-5.10/tools/testing/selftests/powerpc/alignment/
Dalignment_handler.c12 * the other cache-inhibited (by default we use /dev/fb0 for this, but an
66 char *cipath = "/dev/fb0";
620 printf("and either a usable framebuffer at /dev/fb0 or "); in usage()
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/reserved-memory/
Dreserved-memory.txt127 fb0: video@12300000 {
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dat91sam9rlek.dts35 fb0: fb@500000 { label

123