(Difference between revisions)
Revision as of 14:29, 17 December 2010
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.
Getting the Latest Version
- Link to gitorious
- Step-by-step guide how to obtain the sources for ...
- Latest release version (official)
- Latest development version
- Link to meego repo to rpm package
Support & Contacts
- Where to get help? IRC, e-mail ...
- Maintainer name + e-mail + substitute name + e-mail
- If there are any specific instructions for reporting bugs for this specific test module, list them here (logs etc)
- Where to report bugs (what component etc)
* Links to more documentation?
- Please see the file called COPYING
Supported Devices and SW
- List of supported (+ not supported devices, if needed for clarity)
- Info about what is known to work
- nCDK Medfield (starting from version x.z)
- Info about supported MeeGo releases (?)
- List of / link to list of test cases (test case title + description etc)
- If the list is long put them on a separate page
blts-fbdev-tests (0.0.8) is testing Linux kernel framebuffer ioctls and backlight subsystem via sysfs.
Current framebuffer coverage matrix:
Running the Tests
Hardware setup and test environment
- What SW is needed? What packages need to be installed? What versions?
- What HW is needed? What versions?
- How to get accurate measurement results?
- Step-by-step guide for checking that prerequisites are met
- HW version
- Installed packages
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:
To get help about the packaging script, execute
The asset can also be built manually by executing:
Running test cases
- Step-by-step instructions how to execute tests with an example
- Root or user privileges?
- What to do if something goes wrong?
- How to run in debug mode?
- What to look in log files?
Test result analysis
- Where are the results?
- Log files?
- What to do if something fails?
- What to check first?
Configuration file examples
- Configuration file explained
- Example of configuration file
Module Design and Architecture
- What APIs are used? What API versions? E.g. Qt Mobility Messaging 1.0.1, link to API doc
- Architecture Diagrams
- Link to open bugs on meego bugzilla
- Other known issues listed
- List of planned future improvements
- Later, link to backlog items to be done