Lines Matching full:framebuffer

25  * ownership of framebuffer memory and hand-over between drivers.
29  * driver that is currently associated with the given framebuffer memory.
62  * device instance. An active framebuffer will be located within this range.
65  * output on the framebuffer. If successful, the new driver can take over
69  * with every bus that has an addressable framebuffer. In the case of PCI,
72  * knowledge of the framebuffer's location can call
77  * framebuffer apertures. Ownership of the framebuffer memory is achieved
79  * driveris the owner of the framebuffer range. The function fails if the
80  * framebuffer is already owned by another driver. See below for an example.
120  * of the framebuffer memory from its probe function. This will fail if the
126  * et al for the registered framebuffer range, the aperture helpers call
130  * registers, framebuffer memory, ROM, etc afterwards.
303 	 * that consumes the VGA framebuffer I/O range. Remove this device  in aperture_remove_conflicting_devices()