Home | History | Annotate | only in /external/ltp/testcases/kernel/device-drivers
Up to higher level directory
NameDateSize
acpi/06-Dec-2017
agp/06-Dec-2017
base/06-Dec-2017
block/06-Dec-2017
cpufreq/06-Dec-2017
dev_sim_framework/06-Dec-2017
drm/06-Dec-2017
include/06-Dec-2017
locking/06-Dec-2017
Makefile06-Dec-20171K
misc_modules/06-Dec-2017
nls/06-Dec-2017
pci/06-Dec-2017
rcu/06-Dec-2017
README06-Dec-20171K
rtc/06-Dec-2017
tbio/06-Dec-2017
uaccess/06-Dec-2017
usb/06-Dec-2017
v4l/06-Dec-2017
zram/06-Dec-2017

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