(→Test Cases) |
(→Test Cases) |
||
| Line 61: | Line 61: | ||
#: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices. | #: Performance test of reading visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured framebuffer devices. | ||
# Core-Framebuffer 1-pixel uncached write | # Core-Framebuffer 1-pixel uncached write | ||
| + | #: Performance test of writing into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer device into the log and standard output. Done for all configured framebuffer devices. | ||
# Core-Framebuffer 1-pixel uncached modify | # Core-Framebuffer 1-pixel uncached modify | ||
| + | #: Performance test of both reading and vriting into visible framebuffer pixel by pixel. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and and stadard output. Done for all configured framebuffer devices. | ||
# Core-Framebuffer fullscreen buffer read | # Core-Framebuffer fullscreen buffer read | ||
| + | #: Performance test of reading a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices. | ||
# Core-Framebuffer fullscreen buffer write | # Core-Framebuffer fullscreen buffer write | ||
| + | #: Performance test of writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices. | ||
# Core-Framebuffer fullscreen buffer modify | # Core-Framebuffer fullscreen buffer modify | ||
| + | #: Performance test of both reading and writing into a fullscreen framebuffer at once. Uses rusage to estimate the CPU usage %. Prints information about the test and framebuffer into the log and standard output. Done for all configured devices. | ||
# Core-Backlight verify backlight levels | # Core-Backlight verify backlight levels | ||
| + | #: Verify backlight system's backlight level limits against configured limits. Tests the limit values, by using the actual limit and going one step over it. | ||
# Core-Backlight linear backlight level changes | # Core-Backlight linear backlight level changes | ||
| + | #: Linearly goes through all values between configured minimum and maximum values, by first going from min -> max and then from max -> min. NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step. | ||
# Core-Backlight logarithmic backlight level changes | # Core-Backlight logarithmic backlight level changes | ||
| + | #: Goes through all values between configured minimum and maximum values, by going from min -> max. The values are increased by following pattern: (max light / log10 (max light)) * log10 (between min and max). NOTE: This case can timeout if the min and max are very big. The case sleeps for two seconds between each step. | ||
== Coverage == | == Coverage == | ||
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.
The display backlight driver registers a sysfs based directory upon device activation. This is how the blts-fbdev-tests asset uses the backlight system to change display brightness.
Sources can be found in gitorius:
To clone a copy of the repository, see guides in:
Latest binary release is planned to be available via MeeGo OBS, see MeeGo Build Infrastructure for more information.
* 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.