Searched refs:fb1 (Results 1 – 8 of 8) 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.
172 struct drm_framebuffer *fb1 = NULL; in vbox_set_up_input_mapping() local183 if (!fb1) { in vbox_set_up_input_mapping()184 fb1 = CRTC_FB(crtci); in vbox_set_up_input_mapping()185 if (to_vbox_framebuffer(fb1) == &vbox->fbdev->afb) in vbox_set_up_input_mapping()187 } else if (CRTC_FB(crtci) && fb1 != CRTC_FB(crtci)) { in vbox_set_up_input_mapping()
59 buffer driver, the voodoo fb will likely be /dev/fb1. if not, 120 con2fb /dev/fb1 /dev/tty5123 sst_dbg_vgapass /dev/fb1 1 (enables vga cable)124 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
226 fb1=/sys/class/graphics/fb1269 echo "" > $fb1/overlays317 "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
1224 /dev/fb1 is the framebuffer associated with base address 0x12800000
643 1 = /dev/fb1 Second frame buffer
