Skip to content
Lekensteyn edited this page Aug 5, 2011 · 16 revisions

This page tries to establish a design for Bumblebee. It's aimed at developers. Developers are encouraged to discuss the points below.

Installation

The installation is distinct from configuration because it has to be executed only once.

  • display driver installation (currently nvidia, nouveau as option for the future)
  • (Ubuntu, possibly others?) to avoid breaking the Intel display, set the default GL lib to Mesa
  • virtualgl
  • setup initscript / daemon (for now, it starts the X server)
  • add a group which is allowed to use bumblebee
  • (old approach) add user to sudoers to allow enabling/disabling the X server using the initscript

Installation configuration

  • Xorg settings (these should propably be moved to Installation, at leas):
  • ConnectedMonitor setting, known values: CRT-0, DFP-0
  • BusID setting, should be the PCI Bus ID of the nVidia card

Runtime configuration

We should allow for unattended installations and choose sensible defaults.

  • VGL preferences (see also User's Guide for VirtualGL: 19 Advanced configuration)
  • VGL_COMPRESS sets the compression method for framestransport possible values: yuv, jpeg, proxy (VGL default), xv (BB default), rgb
  • VGL_DISPLAY sets the X display to be used (this display is started by Bumblebee)
  • VGL_READBACK - "Specify the method used by VirtualGL to read back the 3D pixels from the 3D graphics hardware" (???)
  • VGL_LOG - set to /dev/null to discard all VGL messages, an empty value should default to outputting to stderr
  • Bumblebee-specific stuff:
  • ECO_MODE - if not connected to a power supply, new programs do not use the nvidia card when ECO_MODE is set to 1.

Daemon

  • should start X server on request (multiple X servers for each user? XXX: check security)
  • allow for driver switching? (probably not)
  • automatically shutdown X when unused for seconds?

Clone this wiki locally