1# framebuffer 2 3**NOTE**: This is not a general purpose library. Clients should be aware of this 4library's limitations before using it. 5 6This library provides a simple framebuffer abstraction on top of the Zircon display 7APIs. Applications can use this library to provide a low level UI on systems which lack 8a normal UI framework. **Important**: When a normal UI framework is running, this 9library will not be able to bind to the display. 10 11The library supports two modes of operation: a single buffer mode where the library 12initializes the display hardware with a single, linear VMO that clients can then 13render to in place, and a page flip mode where the client can provide multiple VMO 14backed images and flip between them. Clients are responsible for ensuring buffers 15are kept coherent with main memory. 16 17The library does not expose support for multiple monitors, hotplugging, modesetting, 18or 2D hardware composition. Applications which want these features should use the Zircon 19display APIs directly. 20