blob: 897ab834839adf005e195f182ed9a9db5a6ff80a [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001
2cx8800 release notes
3====================
4
5This is a v4l2 device driver for the cx2388x chip.
6
7
8current status
9==============
10
11video
12 - Basically works.
13 - Some minor image quality glitches.
14 - For now only capture, overlay support isn't completed yet.
15
16audio
17 - The chip specs for the on-chip TV sound decoder are next
18 to useless :-/
19 - Neverless the builtin TV sound decoder starts working now,
20 at least for PAL-BG. Other TV norms need other code ...
21 FOR ANY REPORTS ON THIS PLEASE MENTION THE TV NORM YOU ARE
22 USING.
23 - Most tuner chips do provide mono sound, which may or may not
24 be useable depending on the board design. With the Hauppauge
25 cards it works, so there is mono sound available as fallback.
26 - audio data dma (i.e. recording without loopback cable to the
27 sound card) should be possible, but there is no code yet ...
28
29vbi
30 - some code present. Doesn't crash any more, but also doesn't
31 work yet ...
32
33
34how to add support for new cards
35================================
36
37The driver needs some config info for the TV cards. This stuff is in
38cx88-cards.c. If the driver doesn't work well you likely need a new
39entry for your card in that file. Check the kernel log (using dmesg)
40to see whenever the driver knows your card or not. There is a line
41like this one:
42
43 cx8800[0]: subsystem: 0070:3400, board: Hauppauge WinTV \
44 34xxx models [card=1,autodetected]
45
46If your card is listed as "board: UNKNOWN/GENERIC" it is unknown to
47the driver. What to do then?
48
49 (1) Try upgrading to the latest snapshot, maybe it has been added
50 meanwhile.
51 (2) You can try to create a new entry yourself, have a look at
52 cx88-cards.c. If that worked, mail me your changes as unified
53 diff ("diff -u").
54 (3) Or you can mail me the config information. I need at least the
55 following informations to add the card:
56
57 * the PCI Subsystem ID ("0070:3400" from the line above,
58 "lspci -v" output is fine too).
59 * the tuner type used by the card. You can try to find one by
60 trial-and-error using the tuner=<n> insmod option. If you
61 know which one the card has you can also have a look at the
62 list in CARDLIST.tuner
63
64Have fun,
65
66 Gerd
67
68--
69Gerd Knorr <kraxel@bytesex.org> [SuSE Labs]