Return to README CVS log

Up to [DVB] / dvb-kernel

Annotation of dvb-kernel/README, revision 1.7

1.6       hunold      1: Instructions for building the "new" driver under 2.6.x:
1.1       hunold      2: -------------------------------------------------------
                      3: 
1.4       hunold      4: (This won't work with *2.4.x*, so don't even try, have a look
                      5: at the build-2.4 directory instead)
1.1       hunold      6: 
1.7     ! hunold      7: You need a kernel >= 2.6.0.
        !             8: 
        !             9: The DVB driver in 2.6.0 is fairly up-to-date, so it's usable for most of
        !            10: the cards. 
        !            11: 
        !            12: Three options:
        !            13: a) If you're satisfied with it and not interested in driver development 
        !            14:    and/or debugging, then you can stop reading here. This stuff is not of
        !            15:    interest for you and won't bring you further. 8-)
        !            16: b) If you'd like to use a more recent driver version, but don't want to 
        !            17:    hassle with CVS, have a look at the "patches-2.6" directory. There you
        !            18:    can find patches which sync the most recent 2.6 kernel with the CVS
        !            19:    driver. Simply apply these patches and recompile the drivers. That's it.
        !            20: c) If you want bleeding edge technology and drivers, read on:
        !            21: 
        !            22: There is a script called "makelinks" which -- well -- makes links from the 
        !            23: CVS version of the driver to the kernel tree you supply on the command line.
        !            24: The driver from the kernel is erased, instead the CVS driver will be used if
        !            25: you compile your kernel again.
1.1       hunold     26: 
                     27: 1) Call "./makelinks <your-kernel-directory>. This will copy and link the
1.5       hunold     28: driver files to your kernel, remove some old files, move some files around.
1.1       hunold     29: 
1.7     ! hunold     30: 2) Next, use "make menuconfig" or whatever and select the av7110 driver if
        !            31: you haven't done so before. 
        !            32: 
        !            33: The av7110 driver needs a firmware to work properly. You can download firmware
        !            34: files from http://www.linuxtv.org:81/download/dvb/
        !            35: The most recent version is dvb-ttpci-01.fw
        !            36: 
1.6       hunold     37: If you have problems with modules and 2.6.x you can also compile the driver
1.3       hunold     38: statically into the kernel.
1.2       hunold     39: 
1.7     ! hunold     40: *Pitfall*:  Normally, this firmware is loaded to the device by the firmware
        !            41: hotplug daemon when the module is loaded. If you compile the driver statically
        !            42: into the kernel this won't work. You need to enable the option "Compile av7110
        !            43: firmware into the driver" then and select the path to the firmware file. In this
        !            44: case, the firmware will be compiled into the driver as it used to be in former
        !            45: times.
        !            46: 
1.1       hunold     47: Build and install the new kernel as usual.
                     48: 
1.7     ! hunold     49: If you copy an old ".config" from an older kernel version (before 2.6.0)  where
        !            50: you already selected the av7110 driver, some dependencies are not set up correctly
        !            51: and the  driver won't be build completely. 
1.4       hunold     52: 
                     53: You need to delete everything between the 
                     54: > # Supported SAA7146 based PCI Adapters
                     55: and
                     56: > # File systems
                     57: line in your ".config", then run "make oldconfig". You will be asked about
                     58: these devices again, and the dependencies are set correctly.
                     59: 
1.6       hunold     60: 3) You need to have at least the following modules loaded:
                     61: 
                     62: - videodev: Video4Linux core module
                     63: - v4l2-common: common functions for Video4Linux-2 drivers
                     64: - v4l1-compat: backward compatiblity layer for Video4Linux-1 legacy applications
                     65: - dvb-core: DVB core module
                     66: - saa7146: SAA7146 core driver functions
                     67: - saa7146_vv: SAA7146 video and vbi functions
                     68: - video-buf: capture helper module for the saa7146_vv driver
                     69: - dvb-ttpci: Driver for AV7110 based DVB-S/C/T cards
                     70: 
                     71: Additionally, you need a frontend driver, ie. ves1x93, ves1820.
                     72: 
1.7     ! hunold     73: Normally it's sufficient to use
        !            74: > modprobe dvb-ttpci
        !            75: > modprobe ves1x93
        !            76: 
        !            77: if you have a ves1x93 based card.
        !            78: 
1.6       hunold     79: Note: The "alps_bsrv2" driver is gone, please use the ves1x93 driver instead!
1.1       hunold     80: 
                     81: 4) Try your favourite programs, the behaviour should be exactly the same.
                     82: Good luck!
                     83: 
                     84: If you have problems or questions:
                     85: 
1.3       hunold     86: 1) Look at the TODO file. If the problem is mentionend there,
1.1       hunold     87: it will be fixed asap.
                     88: 
1.4       hunold     89: 2) Ask on the mailing list. If you choose to do so, please include the
                     90: following informations:
                     91: 
                     92: - Do you really use the "dvb-kernel" driver?
                     93: - When did you check out the driver?
                     94: - Which kernel version are using?
                     95: - Which card do you have? (Name, board revision, frontend type, ...)
                     96: - What are the problems exactly?