Home | History | Annotate | only in /external/ltp/testcases/kernel/device-drivers
Up to higher level directory
NameDateSize
acpi/21-Aug-2018
agp/21-Aug-2018
base/21-Aug-2018
block/21-Aug-2018
cpufreq/21-Aug-2018
dev_sim_framework/21-Aug-2018
drm/21-Aug-2018
include/21-Aug-2018
locking/21-Aug-2018
Makefile21-Aug-20181K
misc_modules/21-Aug-2018
nls/21-Aug-2018
pci/21-Aug-2018
rcu/21-Aug-2018
README21-Aug-20181K
rtc/21-Aug-2018
tbio/21-Aug-2018
uaccess/21-Aug-2018
usb/21-Aug-2018
v4l/21-Aug-2018
zram/21-Aug-2018

README

      1 Device Driver Testcases:
      2 
      3 These tests should always be run individually and never concurrently.  Since
      4 these test will manipulate devices and may leave them in an unstable state,
      5 these tests should not be run when other important system tasks are being
      6 performed.  These tests shouldn't be included in any system wide test scripts
      7 as they may corrupt the test data from those tests.
      8 
      9 To build and execute these tests:
     10 
     11 1) change into each of the directories you want to test and run "make".
     12 2) run the command 'insmod' on the .o file in the kernel space directory.
     13 Note: If the insmod command fails with a QM_MODULE error, the module functions
     14       are outdated and need to be upgraded.
     15 3) Run "lsmod" to make sure the modules is loaded.
     16 4) Change to the user space program directory and run the *.sh file or the
     17    program executable.
     18 5) The results should be output to the display.
     19 6) 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