• Home
  • History
  • Annotate
  • only in /external/ltp/testcases/kernel/device-drivers/
NameDateSize

..10-Aug-20184 KiB

acpi/10-Aug-20184 KiB

agp/10-Aug-20184 KiB

base/10-Aug-20184 KiB

block/10-Aug-20184 KiB

cpufreq/10-Aug-20184 KiB

dev_sim_framework/10-Aug-20184 KiB

drm/10-Aug-20184 KiB

include/10-Aug-20184 KiB

locking/10-Aug-20184 KiB

Makefile10-Aug-20181 KiB

misc_modules/10-Aug-20184 KiB

nls/10-Aug-20184 KiB

pci/10-Aug-20184 KiB

rcu/10-Aug-20184 KiB

README10-Aug-20181 KiB

rtc/10-Aug-20184 KiB

tbio/10-Aug-20184 KiB

uaccess/10-Aug-20184 KiB

usb/10-Aug-20184 KiB

v4l/10-Aug-20184 KiB

zram/10-Aug-20184 KiB

README

1Device Driver Testcases:
2
3These tests should always be run individually and never concurrently.  Since
4these test will manipulate devices and may leave them in an unstable state,
5these tests should not be run when other important system tasks are being
6performed.  These tests shouldn't be included in any system wide test scripts
7as they may corrupt the test data from those tests.
8
9To build and execute these tests:
10
111) change into each of the directories you want to test and run "make".
122) run the command 'insmod' on the .o file in the kernel space directory.
13Note: If the insmod command fails with a QM_MODULE error, the module functions
14      are outdated and need to be upgraded.
153) Run "lsmod" to make sure the modules is loaded.
164) Change to the user space program directory and run the *.sh file or the
17   program executable.
185) The results should be output to the display.
196) These tests will complete very quickly, usually in a few seconds so if the
20   system doesn't return from the test it's probably hung and a re-boot may be
21   required.
22