(→Architecture) |
(→Getting the Latest Version) |
||
| Line 9: | Line 9: | ||
== Getting the Latest Version == | == Getting the Latest Version == | ||
| - | * | + | Sources can be found in gitorius: |
| - | + | * http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-fbdev | |
| - | + | ||
| - | + | ||
| - | * | + | To clone a copy of the repository, see guides in: |
| + | * http://gitorious.org/qa-tools/mcts | ||
== Support & Contacts == | == Support & Contacts == | ||
Contents |
The framebuffer device is a device-independent interface for reading and writing raw data to the video memory. Uses of the device typically include things like text consoles, graphical boot progress indicators and so on. It is also possible to use the framebuffer device as a X11 window system display device.
The framebuffer device is typically used by memory-mapping the device file. The fbdev kernel driver translates any operations to the device-specific display driver. The blts-fbdev-tests asset tests the functionality and performance of this subsystem.
Sources can be found in gitorius:
To clone a copy of the repository, see guides in:
* Links to more documentation?
Supported
Not supported
blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs.
Current framebuffer coverage matrix:
The build environment must have the following packages installed:
The source package includes the pack.sh script, which is used for building RPM and Debian packages and source tar packages. To build an RPM package with the script, execute this command in the top level source directory of asset:
./pack.sh -r
To get help about the packaging script, execute
./pack.sh -h
The asset can also be built manually by executing:
./autogen.sh ./configure make
The test asset (blts-fbdev-tests) is built directly on top of the Linux kernel. Backlight tests use sysfs to test the functionality. The asset has been test to work with at least following Linux kernel versions: 2.6.28, 2.6.31 and 2.6.32.