Device Driver Build guide

Steps for Building and executing the Video/Framebuffer testscenarios:
1) Clone the device drivers from the git://dev.omapzoom.org/pub/scm/richo/device_driver_test.git, currently the master branch.



2) First export the following parameters : export CROSS_COMPILE=arm-none-linux-gnueabi-  export KDIR=path to kerneldirectory  export HOST=arm-none-linux-gnueabi  export ARCH=arm  export PATH=$PATH:

for framebuffer: export TESTSUITES="framebuffer" for video tests: export TESTSUITES="video" 3) There are two ways for building: 3.1) 1. execute the make command The test binaries are created in the "build" directory. At the end of successful build you will see 2 folders utils and video/framebuffer in the "build" folder. cd build/video/scripts/ or cd build/framebuffer/scripts/

3.2) 1. goto required folder        cd framebuffer/test_code      2. Execute make         make      Testsuite binaries would be created in framebuffer/test_code/bin directory.

4) The test binaries are created in the "build" directory. At the end of successful build you will see 2 folders utils and video/framebuffer in the "build" folder.

5) cd build/video/scripts/ or cd build/framebuffer/scripts/

6) To excute the scenarios run this command.  ./test_runner -S 

   

7) The above command would execute the testscenario without human intervention.

8) If the "-S" option is not given in the above command, the script will ask for the key press for various tasks. And the user needs to press the appropriate key to feed the responce.

Note: Based on the .config of the kernel exported, testsuite would be built for OMAP3 or OMAP4.

Note: Build fails for utils/bc Before running make always run "git reset --hard HEAD" and "make distclean" to avoid linking of obsolete files. 1. goto utils/bc folder. 2. delete "missing" file. 3. automake -a -c 4. CC=arm-none-linux-gnueabi-gcc ./configure --host=arm-none-linux-gnueabi 5. make Note: Build fails for video testsuite for linux kernel v3.0.

Building Tomi's testsuite
1) clone the test tree git clone git://gitorious.org/linux-omap-dss2/omapfb-tests.git

2) Modify Makefile to point ot your kernel  cd omapfb-tests/   vi Makefile   Replace: CFLAGS=-I/home/valkeine/work/linux/usr/include -O2 -Wall   with your kernel path like:   CFLAGS=-I/home/mayuresh/kernel-display/include -O2 -Wall

3) Do a clean:  make CROSS_COMPILE=arm-none-linux-gnueabi- clean

4) Do a make:  make CROSS_COMPILE=arm-none-linux-gnueabi-

Binaries would be created in the same folder.

For Further configuration details refer: http://omappedia.org/wiki/Bootargs_for_enabling_display


 * BACK to Display Domain Wiki