You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
hmz007
6d24f2138b
|
3 years ago | |
|---|---|---|
| .. | ||
| acpi | 3 years ago | |
| agp | 3 years ago | |
| base | 3 years ago | |
| block | 3 years ago | |
| cpufreq | 3 years ago | |
| dev_sim_framework | 3 years ago | |
| drm | 3 years ago | |
| include | 3 years ago | |
| locking | 3 years ago | |
| misc_modules | 3 years ago | |
| nls | 3 years ago | |
| pci | 3 years ago | |
| rcu | 3 years ago | |
| rtc | 3 years ago | |
| tbio | 3 years ago | |
| uaccess | 3 years ago | |
| usb | 3 years ago | |
| v4l | 3 years ago | |
| zram | 3 years ago | |
| Makefile | 3 years ago | |
| README | 3 years ago | |
README
Device Driver Testcases:
These tests should always be run individually and never concurrently. Since
these test will manipulate devices and may leave them in an unstable state,
these tests should not be run when other important system tasks are being
performed. These tests shouldn't be included in any system wide test scripts
as they may corrupt the test data from those tests.
To build and execute these tests:
1) change into each of the directories you want to test and run "make".
2) run the command 'insmod' on the .o file in the kernel space directory.
Note: If the insmod command fails with a QM_MODULE error, the module functions
are outdated and need to be upgraded.
3) Run "lsmod" to make sure the modules is loaded.
4) Change to the user space program directory and run the *.sh file or the
program executable.
5) The results should be output to the display.
6) These tests will complete very quickly, usually in a few seconds so if the
system doesn't return from the test it's probably hung and a re-boot may be
required.