Annotation of dvb-kernel/README-2.6, revision 1.4.2.1
1.4.2.1 ! js 1: ******************************************************************************
! 2: NOTE: This is the linux_2_4 CVS branch. Drivers for linux-2.6 are in CVS HEAD.
! 3: ******************************************************************************
! 4:
! 5:
1.2 hunold 6: Instructions for patching a 2.6 kernel with this release
7: --------------------------------------------------------
1.1 holger 8:
1.3 js 9: (Note: Alternatively you can use build-2.6/ to build without
10: patching the kernel, but this currently does not work for
11: bt878 based cards due to include patch problems.)
12:
13:
1.2 hunold 14: The DVB driver in 2.6.1 and above is regularly kept up-to-date, so it's possible
15: that it's even newer than the latest release tarball. There might be some cases
16: though, where you want a specific release tarball driver compiled into the
17: kernel.
1.1 holger 18:
19: There is a script called "makelinks" which -- well -- makes links from the
20: CVS version of the driver to the kernel tree you supply on the command line.
1.2 hunold 21: The driver from the kernel is erased, instead the local source will be used if
1.1 holger 22: you compile your kernel again.
23:
1.2 hunold 24: Step-by-step instruction:
25:
1.1 holger 26: 1) Call "./makelinks <your-kernel-directory>. This will copy and link the
27: driver files to your kernel, remove some old files, move some files around.
28:
29: 2) Next, use "make menuconfig" or whatever and select the av7110 driver if
30: you haven't done so before.
31:
1.2 hunold 32: The av7110 driver needs a firmware to work properly.
33:
34: If you want to compile it into the driver as it used to be in the past, you can
1.4 js 35: download firmware files from http://www.linuxtv.org/download/dvb/ The most
1.2 hunold 36: recent version is dvb-ttpci-01.fw. You need to select "Compile av7110 firmware
37: into the driver" and specify the filename path (usually
38: /usr/lib/hotplug/firmware/dvb-ttpci-01.fw) within the DVB subsystem configuration
39: of the kernel.
40:
41: Alternatively, you can use the hotplug facilities of 2.6 to let the driver load
42: it's firmware upon driver insertion. Have a look at
43: linux/documentation/firmware.txt for further details.
44:
45: *Pitfall*:
46: If you compile the driver statically into the kernel, you must make sure that
47: you compile the firmware into the driver. There is currently no way to prevent
48: in-kernel compilation without the firmware being compiled in. If you do it anyway,
49: there will be no way that you can load the firmware.
1.1 holger 50:
51: Build and install the new kernel as usual.
LinuxTV legacy CVS <linuxtv.org/cvs>