1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
|
Release notes for bttv-0.7.x
============================
This version is based on Ralphs 0.6.4 release. There are alot of
changes. Bugfixes, merged patches from other people, merged fixes
from the kernel version, port to the new i2c stack, removed support
for 2.0.x, code cleanups, ...
To compile this bttv version, you'll the new i2c stack. Kernels
newer than 2.3.34 have this already included. If you have a older
kernel, download it from:
http://www2.lm-sensors.nu/~lm78/download.html
You'll need at least these i2c config options for bttv:
CONFIG_I2C=m
CONFIG_I2C_ALGOBIT=m
The latest bttv version is available here:
http://me.in-berlin.de/~kraxel/bttv.html
You'll find Ralphs original (mostly outdated) documentation in the
ralphs-doc subdirectory.
Compile bttv
------------
If you are compiling the kernel version, just say 'm' if you are asked
for bttv. I /strongly/ suggest to compile bttv as module, because
there are some insmod options for configuring the driver.
If you downloaded the separate bttv bundle: You need configured kernel
sources to compile the bttv driver. The driver uses some Makefile
magic to compile the modules with your kernel's configuration
(wrt. module-versions, SMP, ...). If you already have compiled the
kernel at least once, you probably don't have do worry about this. If
not, go to /usr/src/linux and run at least "make config". Even
better, compile your own kernel, you'll never become a real hacker
else ;-)
Make bttv work with your card
-----------------------------
Of course you have to load the modules as very first thing. The
separate bttv bundle comes with a script called "update". I use this
one to load a new version while doing driver hacking. You can use it
too, but check the module arguments first. They work for my setup,
and probably do *not* for yours. Another way is to setup your
/etc/modules.conf file and let kmod load the modules. See also:
Modules.conf: some sample entries for /etc/modules.conf
Insmod-options: list of all insmod options available for bttv and
the helper modules.
MAKEDEV: a script to create the special files for v4l
CARDLIST: List of all supported cards
Loading just the bttv modules isn't enouth for most cards. The
drivers for the i2c tuner/sound chips must also be loaded. bttv tries
to load them automagically by calling request_module() now, but this
obviously works only with kmod enabled.
The most important insmod option for bttv is "card=n" to select the
correct card type. If you get video but no sound you've very likely
specified the wrong (or no) card type. A list of supported cards is
in CARDLIST.
If your card isn't listed in CARDLIST, you should read the Sound-FAQ.
Still doesn't work?
-------------------
I do NOT have a lab with 30+ different grabber boards and a
PAL/NTSC/SECAM test signal generator at home, so I often can't
reproduce your problems. This makes debugging very difficult for me.
If you have some knowledge and spare time, please try to fix this
yourself (patches very welcome of course...) You know: The linux
slogan is "Do it yourself".
There is a mailing list: video4linux-list@redhat.com. If you have
trouble with some specific TV card, try to ask there instead of
mailing me directly. The chance that someone with the same card
listens there is much higher...
Finally: If you mail some patches for bttv around the world (to
linux-kernel/Alan/Linus/...), please Cc: me.
Have fun with bttv,
Gerd
--
Gerd Knorr <kraxel@goldbach.in-berlin.de>
|
