Home
last modified time | relevance | path

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

12

/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/lvgl/files/
H A D0003-Make-fbdev-device-node-runtime-configurable-via-envi.patch9 Otherwise fall back to /dev/fb0, i.e. the current behavior. This way,
33 + const char *videocard = lv_linux_get_video_card_node("/dev/fb0");
38 - lv_linux_fbdev_set_file(disp, "/dev/fb0");
H A D0004-Factor-out-fbdev-initialization-code.patch29 const char *videocard = lv_linux_get_video_card_node("/dev/fb0");
/openbmc/linux/drivers/staging/sm750fb/
H A 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
/openbmc/openbmc/meta-raspberrypi/recipes-core/psplash/files/
H A Dframebuf.conf2 Requires=sys-devices-platform-gpu-graphics-fb0.device
3 After=sys-devices-platform-gpu-graphics-fb0.device
/openbmc/openbmc/poky/meta/recipes-core/psplash/files/
H A Dpsplash-init13 if [ ! -e /dev/fb0 ]; then
14 echo "Framebuffer /dev/fb0 not detected"
/openbmc/linux/Documentation/arch/arm/omap/
H A 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
/openbmc/linux/Documentation/fb/
H A 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
H A 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
H A Dlxfb.rst16 * You can run XF68_FBDev on top of /dev/fb0
H A Dgxfb.rst15 * You can run XF68_FBDev on top of /dev/fb0
H A Dpvr2fb.rst12 * You can run XF86_FBDev on top of /dev/fb0
H A Daty128fb.rst14 * You can run XF68_FBDev on top of /dev/fb0
/openbmc/linux/Documentation/devicetree/bindings/display/
H A Datmel,lcdc.txt29 fb0: fb@00500000 {
43 fb0: fb@00500000 {
/openbmc/openbmc/poky/meta/recipes-core/udev/udev-extraconf/
H A Dlocalextra.rules20 KERNEL=="fb0", SYMLINK+="fb"
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/memstat/memstat/
H A D0001-Include-limits.h-for-PATH_MAX-definition.patch18 index 5039fb0..3ff6ee4 100644
/openbmc/linux/Documentation/devicetree/bindings/reserved-memory/
H A Dmemory-region.yaml34 fb0: video@12300000 {
/openbmc/openbmc/poky/meta/recipes-core/busybox/files/
H A Dmdev.conf5 fb0:0 44 0660
/openbmc/openbmc/poky/meta/files/
H A Ddevice_table-minimal.txt13 /dev/fb0 c 600 root root 29 0 - - -
/openbmc/linux/Documentation/driver-api/
H A Dsm501.rst52 given to it by aligning fb0 to the start of the area and fb1 to the end
/openbmc/linux/tools/testing/selftests/powerpc/alignment/
H A 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()
/openbmc/u-boot/arch/arm/dts/
H A Dat91sam9rlek.dts36 fb0: fb@00500000 { label
H A Dat91sam9263ek.dts100 fb0: fb@0x00700000 { label
H A Dat91sam9261ek.dts39 fb0: fb@0x00600000 { label
/openbmc/linux/arch/arm/boot/dts/microchip/
H A Dat91sam9263ek.dts114 fb0: fb@700000 { label
H A Dat91sam9rlek.dts35 fb0: fb@500000 { label

12