[BACK]Return to README CVS log [TXT] [DIR] Up to [DVB] / dvb-kernel

Diff for /dvb-kernel/README between versions 1.9 and 1.10

version 1.9, 2004/01/25 17:47:32 version 1.10, 2004/01/25 18:44:40
Line 1 Line 1
 Instructions for building the standalone driver:  Instructions for building the standalone driver:
 ------------------------------------------------  ------------------------------------------------
   
 You must have the kernel sources for the kernel you are currently using  If you encounter any problems while executing the follwing steps please read
 installed, and symlinked to /lib/modules/$(KERNEL_VERSION)/build. This should  the TROUBLESHOOTING file.
 be the default in proper installations with installed kernel source package.  
   
 If you are in doubt please get a fresh and clean kernel source tarball from   
 http://www.kernel.org/, unpack, configure, install and boot this one before  
 building the DVB driver. 80% of the bug reports on the linux-dvb mailing list  
 have been related to not properly installed kernel source trees in the past.  
   
 For cards with MPEG decoder onboard make sure that CONFIG_VIDEO_DEV is enabled  
 in the config of your running kernel. If you get unresolved symbols named  
 video_XXXX when loading the driver then you missed this option.  
   
 For some cards you need Input and Event Device Support enabled to get the  
 IR receiver on the card running. Be sure to enable CONFIG_INPUT and   
 CONFIG_INPUT_EVDEV if you get unresolved symbols named input_XXX.  
   
 Now Type 'make' to build the driver. The compiled modules will be located  Simply type 'make' to build the driver. The compiled modules will be located
 in directory ./build-2.4/ or ./build-2.6, depening on the kernel version you  in directory ./build-2.4/ or ./build-2.6, depening on the kernel version you
 are running. There you will also find scripts to load and unload the modules.  are running. There you will also find scripts to load and unload the modules.
   
Line 26  For some cards you need to download addi Line 12  For some cards you need to download addi
 notified in the build process or when loading the modules, please follow the  notified in the build process or when loading the modules, please follow the
 instructions there if you own one of the cards that need a firmware to run.  instructions there if you own one of the cards that need a firmware to run.
   
   Be sure that you are root for the following steps.
   
 Now execute the ./MAKEDEV-DVB.sh script to create the DVB API device nodes.  Now execute the ./MAKEDEV-DVB.sh script to create the DVB API device nodes.
 In ./build-2.4/ or ./build-2.6/ you find the insmod script.    
   In ./build-2.4/ or ./build-2.6/ you find the insmod script.
   
 Use './insmod.sh load' to load the driver modules, './insmod.sh unload' to   Use './insmod.sh load' to load the driver modules, './insmod.sh unload' to 
 remove them. './insmod debug' loads the drivers with debugging enabled.   remove them. './insmod debug' loads the drivers with debugging enabled. 
 These scripts load all drivers for all cards, if you check what hardware you   These scripts load all drivers for all cards but the ones based on the bt8xx
 actually own you can accelerate the initialisation by loading only the driver   and the DEC2000-T, DEC2540-T and DEC3000-S USB boxes.
 modules you need.  
   For bt8xx based cards please use the insmod-bt8xx.sh script, for the DEC USB 
   boxes 'insmod dvb-core.o ttusb_dec.o'.
   
   Now check the klog and syslog (in doubt type 'dmesg') for errors messages.
   
 When you reached this point successfully you probably want to start some  When you reached this point successfully you probably want to start some
 test applications, download the linuxtv-dvb-apps-1.1.tar.gz package, unpack  test applications, download the linuxtv-dvb-apps-1.1.tar.gz package, unpack
Line 70  For 'real' everyday use you probably don Line 64  For 'real' everyday use you probably don
 but install a program like VDR or MythTV.  but install a program like VDR or MythTV.
 (Read ./linux/Documentation/dvb/faq.txt for some links)  (Read ./linux/Documentation/dvb/faq.txt for some links)
   
   When everything is working you probably want to install the driver on your 
   system by typing 'make install'. If you want to load the modules automatically
   when an application tries to open the device you need to add lines like these 
   to your modules.conf:
   
           probeall /dev/dvb dvb-ttpci
           alias /dev/dvb/* /dev/dvb
           below dvb-ttpci alps_bsrv2 alps_tdmb7 alps_tdlb7
           add below dvb-ttpci grundig_29504-401 grundig_29504-491
           add below dvb-ttpci stv0299 ves1820
   
   Note: this example is for people with Technotrend-based PCI cards, they must 
   load the dvb-ttpci driver and a matching frontend drivers that are potentially
   used on these cards. In order to find out which ones are required for your
   setup check the lsmod output after loading the driver like described above.
   Those DVB modules that have a usecount greater zero are required in your 
   setup - edit the modules.conf file appropriatly]
   
   Debian users don't edit modules.conf manually but add the lines above to a new
   file in /etc/modutils/ (e.g. /etc/modutils/dvb) and call 'update-modules' then.
   
 --------------------------------------------------------------------------------  --------------------------------------------------------------------------------
   
 The build system has been tested down to 2.4.20, if you run an older kernel  The build system has been tested down to 2.4.20, if you run an older kernel
Removed from v.1.9  
changed lines
  Added in v.1.10

LinuxTV legacy CVS <linuxtv.org/cvs>