Searched refs:fb1 (Results 1 – 7 of 7) sorted by relevance
19 it will create fb0 and fb1 (or fb1,fb2 if fb0 already exist) under /dev37 and this driver will use fb1, fb2. In that case, you need to configure your X-server38 to use fb1. Another simple althernative is to disable vesafb from your config.
125 struct drm_framebuffer *fb, *fb1 = NULL; in vbox_set_up_input_mapping() local140 if (!fb1) { in vbox_set_up_input_mapping()141 fb1 = fb; in vbox_set_up_input_mapping()142 if (fb1 == vbox->ddev.fb_helper->fb) in vbox_set_up_input_mapping()144 } else if (fb != fb1) { in vbox_set_up_input_mapping()148 if (!fb1) in vbox_set_up_input_mapping()153 vbox->input_mapping_width = fb1->width; in vbox_set_up_input_mapping()154 vbox->input_mapping_height = fb1->height; in vbox_set_up_input_mapping()
72 buffer driver, the voodoo fb will likely be /dev/fb1. if not,148 con2fb /dev/fb1 /dev/tty5153 sst_dbg_vgapass /dev/fb1 1 (enables vga cable)154 sst_dbg_vgapass /dev/fb1 0 (disables vga cable)
32 1 = /dev/fb1 Second frame buffer40 /dev/fb1current -> fb151 buffer devices (/dev/fb0 and /dev/fb1 etc.) work independently.59 export FRAMEBUFFER=/dev/fb163 setenv FRAMEBUFFER /dev/fb1
230 fb1=/sys/class/graphics/fb1277 echo "" > $fb1/overlays325 "1:4M" to allocate 4M for fb1.
52 given to it by aligning fb0 to the start of the area and fb1 to the end
634 1 = /dev/fb1 Second frame buffer