Mailing List Archive

On Sun, 2008-09-21 at 20:20 +0200, Martin Patzak wrote:
> Hello Developers,
>
> my card seems to be unknown and not working. Here is the relevant
> section from dmesg:
>
> [20662.259290] ivtv: Start initialization, version 1.3.0
> [20662.259402] ivtv0: Initializing card #0
> [20662.259415] ivtv0: Unknown card: vendor/device: 4444/0016
> [20662.259419] ivtv0: subsystem vendor/device: 104d/813d
> [20662.259423] ivtv0: cx23416 based

This is a Sony (VAIO?) card, which two other users have asked about this
year and at least one other two years ago.

At least one other Sony card is mentioned on the wiki (see the last
entry here):

http://www.ivtvdriver.org/index.php/Supported_hardware

(not very heartening..)


> [20662.259427] ivtv0: Defaulting to Hauppauge WinTV PVR-150 card
> [20662.259430] ivtv0: Please mail the vendor/device and subsystem
> vendor/device IDs and what kind of

[snip]

> Please let me know if you need more information or tests I can do for you!

The things we would need at first are:

1. a list of all the chips on the card
2. a high resolution photograph of both sides of the card

>From there, if all the chips are known or data sheets available, and if
we can make good guesess as to how the card is wired up, we can add an
initial entry to ivtv-cards.c. Once that's done, you can run tests we
can explain to you to hopefully get the card entry working properly.


There's a lot of "if"s involved.

Regards,
Andy





> Thanks,
>
> Martin



_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

On Sun, 2008-09-21 at 20:20 +0200, Martin Patzak wrote:
> Hello Developers,
>
> my card seems to be unknown and not working. Here is the relevant
> section from dmesg:
>
> [20662.259290] ivtv: Start initialization, version 1.3.0
> [20662.259402] ivtv0: Initializing card #0
> [20662.259415] ivtv0: Unknown card: vendor/device: 4444/0016
> [20662.259419] ivtv0: subsystem vendor/device: 104d/813d
> [20662.259423] ivtv0: cx23416 based
> [20662.259427] ivtv0: Defaulting to Hauppauge WinTV PVR-150 card
> [20662.259430] ivtv0: Please mail the vendor/device and subsystem
> vendor/device IDs and what kind of
> [20662.259434] ivtv0: card you have to the ivtv-devel mailinglist
> (www.ivtvdriver.org)
> [20662.259438] ivtv0: Prefix your subject line with [UNKNOWN IVTV CARD].
> [20662.267254] ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 17 (level,
> low) -> IRQ 17
> [20662.327183] tveeprom 1-0050: Encountered bad packet header [aa].
> Corrupt or not a Hauppauge eeprom.
> [20662.327183] ivtv0: Invalid EEPROM
> [20662.367192] cx25840 1-0044: cx25 0-21 found @ 0x88 (ivtv i2c driver #0)
> [20662.371696] All bytes are equal. It is not a TEA5767
> [20662.371781] tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #0)
> [20662.371837] wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> [20662.379196] wm8775 1-001b: I2C: cannot write 000 to register R23
> [20662.383191] wm8775 1-001b: I2C: cannot write 000 to register R7
> [20662.387191] wm8775 1-001b: I2C: cannot write 021 to register R11
> [20662.387810] wm8775 1-001b: I2C: cannot write 102 to register R12
> [20662.391191] wm8775 1-001b: I2C: cannot write 000 to register R13
> [20662.395193] wm8775 1-001b: I2C: cannot write 1d4 to register R14
> [20662.399190] wm8775 1-001b: I2C: cannot write 1d4 to register R15
> [20662.403193] wm8775 1-001b: I2C: cannot write 1bf to register R16
> [20662.407193] wm8775 1-001b: I2C: cannot write 185 to register R17
> [20662.411193] wm8775 1-001b: I2C: cannot write 0a2 to register R18
> [20662.411903] wm8775 1-001b: I2C: cannot write 005 to register R19
> [20662.415190] wm8775 1-001b: I2C: cannot write 07a to register R20
> [20662.475191] wm8775 1-001b: I2C: cannot write 102 to register R21
> [20662.475191] ivtv0: Registered device video0 for encoder MPG (4096 kB)
> [20662.475191] ivtv0: Registered device video32 for encoder YUV (2048 kB)
> [20662.475191] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
> [20662.475191] ivtv0: Registered device video24 for encoder PCM (320 kB)
> [20662.475191] ivtv0: Registered device radio0 for encoder radio
> [20662.475191] ivtv0: Initialized card #0: Hauppauge WinTV PVR-150
> [20662.475191] ivtv: End initialization
> [20663.140378] firmware: requesting v4l-cx2341x-enc.fw
> [20663.168363] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> [20663.364870] ivtv0: Encoder revision: 0x02060039
> [20663.395685] firmware: requesting v4l-cx23885-avcore-01.fw
> [20663.404821] cx25840 1-0044: unable to open firmware v4l-cx23885-avcore-01.fw
> [20663.531298] wm8775 1-001b: I2C: cannot write 0c0 to register R21
> [20663.535483] wm8775 1-001b: I2C: cannot write 1d4 to register R14
> [20663.538515] wm8775 1-001b: I2C: cannot write 1d4 to register R15
> [20663.541461] wm8775 1-001b: I2C: cannot write 102 to register R21
> [20663.582459] tuner 1-0060: tuner type not set
>
> here is the information from lspci -vv:
>
> 03:05.0 Multimedia video controller: Internext Compression Inc iTVC16
> (CX23416) MPEG-2 Encoder (rev 01)
> Subsystem: Sony Corporation Device 813d
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 16 bytes
> Interrupt: pin A routed to IRQ 17
> Region 0: Memory at d8000000 (32-bit, prefetchable) [size=64M]
> Capabilities: <access denied>
> Kernel driver in use: ivtv
> Kernel modules: ivtv
>
> Please let me know if you need more information or tests I can do for you!

Martin,

Based on the pictures you sent, I cannot add support for this card. The
SAA7115 video decoder is supported under linux as is the CX23416 MPEG
Encoder.

However, the Sony CXD9795BR chip is not supported AFAICT and I can't
find a publicly available datasheet for it.

I wouldn't know who to contact at Sony for getting at data sheet or how
forthcoming they would be. If I did have a datasheet it would still
take time to write a driver for the chip, and would also mean I'd have
to have the hardware in hand for testing.

Hans is the official ivtv maintainer, maybe he has some past experience
with Sony. BTW, an accurate list of devices on the card appears to be
listed here:

http://pukiwiki.damedas.com/index.php?Linux%2Fivtv%2F%CC%A4%A5%B5%A5%DD%A1%BC%A5%C8%A5%AB%A1%BC%A5%C9%2FSONY%20ENX-26%20AOI


Regards,
Andy

> Thanks,
>
> Martin



_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

On Thursday 02 October 2008 02:19:12 Andy Walls wrote:
> On Sun, 2008-09-21 at 20:20 +0200, Martin Patzak wrote:
> > Hello Developers,
> >
> > my card seems to be unknown and not working. Here is the relevant
> > section from dmesg:
> >
> > [20662.259290] ivtv: Start initialization, version 1.3.0
> > [20662.259402] ivtv0: Initializing card #0
> > [20662.259415] ivtv0: Unknown card: vendor/device: 4444/0016
> > [20662.259419] ivtv0: subsystem vendor/device:
> > 104d/813d [20662.259423] ivtv0: cx23416 based
> > [20662.259427] ivtv0: Defaulting to Hauppauge WinTV PVR-150 card
> > [20662.259430] ivtv0: Please mail the vendor/device and subsystem
> > vendor/device IDs and what kind of
> > [20662.259434] ivtv0: card you have to the ivtv-devel mailinglist
> > (www.ivtvdriver.org)
> > [20662.259438] ivtv0: Prefix your subject line with [UNKNOWN IVTV
> > CARD]. [20662.267254] ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 17
> > (level, low) -> IRQ 17
> > [20662.327183] tveeprom 1-0050: Encountered bad packet header [aa].
> > Corrupt or not a Hauppauge eeprom.
> > [20662.327183] ivtv0: Invalid EEPROM
> > [20662.367192] cx25840 1-0044: cx25 0-21 found @ 0x88 (ivtv i2c
> > driver #0) [20662.371696] All bytes are equal. It is not a TEA5767
> > [20662.371781] tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #0)
> > [20662.371837] wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver
> > #0) [20662.379196] wm8775 1-001b: I2C: cannot write 000 to register
> > R23 [20662.383191] wm8775 1-001b: I2C: cannot write 000 to register
> > R7 [20662.387191] wm8775 1-001b: I2C: cannot write 021 to register
> > R11 [20662.387810] wm8775 1-001b: I2C: cannot write 102 to register
> > R12 [20662.391191] wm8775 1-001b: I2C: cannot write 000 to register
> > R13 [20662.395193] wm8775 1-001b: I2C: cannot write 1d4 to register
> > R14 [20662.399190] wm8775 1-001b: I2C: cannot write 1d4 to register
> > R15 [20662.403193] wm8775 1-001b: I2C: cannot write 1bf to register
> > R16 [20662.407193] wm8775 1-001b: I2C: cannot write 185 to register
> > R17 [20662.411193] wm8775 1-001b: I2C: cannot write 0a2 to register
> > R18 [20662.411903] wm8775 1-001b: I2C: cannot write 005 to register
> > R19 [20662.415190] wm8775 1-001b: I2C: cannot write 07a to register
> > R20 [20662.475191] wm8775 1-001b: I2C: cannot write 102 to register
> > R21 [20662.475191] ivtv0: Registered device video0 for encoder MPG
> > (4096 kB) [20662.475191] ivtv0: Registered device video32 for
> > encoder YUV (2048 kB) [20662.475191] ivtv0: Registered device vbi0
> > for encoder VBI (1024 kB) [20662.475191] ivtv0: Registered device
> > video24 for encoder PCM (320 kB) [20662.475191] ivtv0: Registered
> > device radio0 for encoder radio [20662.475191] ivtv0: Initialized
> > card #0: Hauppauge WinTV PVR-150 [20662.475191] ivtv: End
> > initialization
> > [20663.140378] firmware: requesting v4l-cx2341x-enc.fw
> > [20663.168363] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836
> > bytes) [20663.364870] ivtv0: Encoder revision: 0x02060039
> > [20663.395685] firmware: requesting v4l-cx23885-avcore-01.fw
> > [20663.404821] cx25840 1-0044: unable to open firmware
> > v4l-cx23885-avcore-01.fw [20663.531298] wm8775 1-001b: I2C: cannot
> > write 0c0 to register R21 [20663.535483] wm8775 1-001b: I2C: cannot
> > write 1d4 to register R14 [20663.538515] wm8775 1-001b: I2C: cannot
> > write 1d4 to register R15 [20663.541461] wm8775 1-001b: I2C: cannot
> > write 102 to register R21 [20663.582459] tuner 1-0060: tuner type
> > not set
> >
> > here is the information from lspci -vv:
> >
> > 03:05.0 Multimedia video controller: Internext Compression Inc
> > iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
> > Subsystem: Sony Corporation Device 813d
> > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
> > ParErr- Stepping- SERR- FastB2B- DisINTx-
> > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> >
> > >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> >
> > Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 16
> > bytes Interrupt: pin A routed to IRQ 17
> > Region 0: Memory at d8000000 (32-bit, prefetchable)
> > [size=64M] Capabilities: <access denied>
> > Kernel driver in use: ivtv
> > Kernel modules: ivtv
> >
> > Please let me know if you need more information or tests I can do
> > for you!
>
> Martin,
>
> Based on the pictures you sent, I cannot add support for this card.
> The SAA7115 video decoder is supported under linux as is the CX23416
> MPEG Encoder.
>
> However, the Sony CXD9795BR chip is not supported AFAICT and I can't
> find a publicly available datasheet for it.
>
> I wouldn't know who to contact at Sony for getting at data sheet or
> how forthcoming they would be. If I did have a datasheet it would
> still take time to write a driver for the chip, and would also mean
> I'd have to have the hardware in hand for testing.
>
> Hans is the official ivtv maintainer, maybe he has some past
> experience with Sony.

I had similar problems in the past: I wouldn't know how to get hold of
Sony datasheets. If anyone knows a contact there I'd certainly
appreciate it.

Regards,

Hans

> BTW, an accurate list of devices on the card
> appears to be listed here:
>
> http://pukiwiki.damedas.com/index.php?Linux%2Fivtv%2F%CC%A4%A5%B5%A5%
>DD%A1%BC%A5%C8%A5%AB%A1%BC%A5%C9%2FSONY%20ENX-26%20AOI
>
>
> Regards,
> Andy
>
> > Thanks,
> >
> > Martin



_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

On Thu, 2010-01-28 at 19:53 -0500, hamer669@aol.com wrote:
> Running Mythbuntu 9.10 with a Sony ENX-26 rev 2.0 Capture card.
>
> The metal RF portion of the card has a sticker that reads:
> btf-pa402z
>
>
> Here is the output from the ivtv driver:
>
> [ 9.724071] ivtv: Start initialization, version 1.4.1
> [ 9.724312] ivtv0: Initializing card 0
> [ 9.724331] ivtv0: Unknown card: vendor/device: [4444:0016]
> [ 9.724340] ivtv0: subsystem vendor/device:
> [104d:813d]
> [ 9.724347] ivtv0: cx23416 based
> [ 9.724352] ivtv0: Defaulting to Hauppauge WinTV PVR-150 card
>
>
Yes, this is a Sony KIKYO card IIRC. It is on my todo list. I'll try
to get to it soon. I don't quite know the paramaters for the analog
tuner, so some RF channels may not be that good when i get the patches
worked up.

Regards,
Andy
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel


_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

On Tue, 2011-01-25 at 21:04 +0100, kris.marien@kpnmail.nl wrote:
> I got this from the kern.log file:
>
> ***
> vendor/device: [4444:0016]
> subsystem vendor/device: [1179:0001]
> ***
>
> Card type:
>
> Toshiba PCI TV Tuner type W
>
> on Toshiba Qosmio F10-120 (Laptop)


> What do I do to get this card working?

The ivtv driver doesn't know about this card.

These are the cards the ivtv driver knows about:
$ modinfo ivtv
filename: /lib/modules/2.6.32.14-127.fc12.x86_64/kernel/drivers/media/video/ivtv/ivtv.ko
version: 1.4.1
[...]
parm: cardtype:Only use this option if your card is not detected properly.
Specify card type:
1 = WinTV PVR 250
2 = WinTV PVR 350
3 = WinTV PVR-150 or PVR-500
4 = AVerMedia M179
5 = YUAN MPG600/Kuroutoshikou iTVC16-STVLP
6 = YUAN MPG160/Kuroutoshikou iTVC15-STVLP
7 = YUAN PG600/DIAMONDMM PVR-550 (CX Falcon 2)
8 = Adaptec AVC-2410
9 = Adaptec AVC-2010
10 = NAGASE TRANSGEAR 5000TV
11 = AOpen VA2000MAX-STN6
12 = YUAN MPG600GR/Kuroutoshikou CX23416GYC-STVLP
13 = I/O Data GV-MVP/RX
14 = I/O Data GV-MVP/RX2E
15 = GOTVIEW PCI DVD
16 = GOTVIEW PCI DVD2 Deluxe
17 = Yuan MPC622
18 = Digital Cowboy DCT-MTVP1
19 = Yuan PG600V2/GotView PCI DVD Lite
20 = Club3D ZAP-TV1x01
21 = AverTV MCE 116 Plus
22 = ASUS Falcon2
23 = AverMedia PVR-150 Plus
24 = AverMedia EZMaker PCI Deluxe
25 = AverMedia M104 (not yet working)
26 = Buffalo PC-MV5L/PCI
27 = AVerMedia UltraTV 1500 MCE
0 = Autodetect (default)
-1 = Ignore this card
(array of int)


So you have two choices:

1. You can to try to specify a card with the "cardtype=" module
parameter.

Many of the designs from Taiwan manufacturers are the same, so I'm
guessing one of these card types will work for you:

Cards with older RF tuner assemblies (not likely in a laptop):
"Yuan PG600, Diamond PVR-550" cardtype=7
"GotView PCI DVD2 Deluxe" cardtype=16
"Yuan MPC622" cardtype=17

Cards with an XC3028/XC2028 RF tuner chip (needs xc3028.fw image):
"Yuan PG600-2, GotView PCI DVD Lite" cardtype=19
"Club3D ZAP-TV1x01" cardtype=20
"Buffalo PC-MV5L/PCI" cardtype=26

If you don't need the RF tuner, and only need CVBS or SVideo input, then
cardtype 7 is probably the safest to test with, as it doesn't try to set
any GPIO pins.


2. Add a new card entry in ivtv-cards.c and ivtv-driver.c and recompile
the ivtv module.

The new card entry will likely look very much like some existing card
entry. The hardest part is figuring out the proper GPIO pin settings
and tuner being used. Sometimes the Windows driver *.inf file has the
information, some times it doesn't.

Regards,
Andy



_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

I set the cardtype to 5 YUAN MPG600/Kuroutoshikou iTVC16-STVLP because of the output of lspci (especially the iTVC16 part):

02:09.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)

The output of dmesg | grep ivtv is now as following:

[ 23.952913] ivtv: Start initialization, version 1.4.1
[ 24.244244] ivtv0: Initializing card 0
[ 24.244251] ivtv0: User specified Yuan MPG600, Kuroutoshikou ITVC16-STVLP card (detected cx23416 based chip)
[ 24.252101] ivtv 0000:02:09.0: enabling device (0000 -> 0002)
[ 24.252112] ivtv 0000:02:09.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
[ 24.607292] tuner 0-0060: chip found @ 0xc0 (ivtv i2c driver #0)
[ 24.687177] IRQ 11/ivtv0: IRQF_DISABLED is not guaranteed on shared IRQs
[ 24.687640] ivtv0: Registered device video0 for encoder MPG (4096 kB)
[ 24.687743] ivtv0: Registered device video32 for encoder YUV (2048 kB)
[ 24.687850] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
[ 24.687948] ivtv0: Registered device video24 for encoder PCM (320 kB)
[ 24.687952] ivtv0: Initialized card: Yuan MPG600, Kuroutoshikou ITVC16-STVLP
[ 24.688987] ivtv: End initialization
[ 25.320064] ivtv 0000:02:09.0: firmware: requesting v4l-cx2341x-enc.fw
[ 25.329590] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[ 25.532176] ivtv0: Encoder revision: 0x02060039

I have no more I2C errors.

The output of dmesg | grep tuner is as following:

[ 24.607292] tuner 0-0060: chip found @ 0xc0 (ivtv i2c driver #0)
[ 24.686094] tuner-simple 0-0060: creating new instance
[ 24.686100] tuner-simple 0-0060: type set to 53 (Philips FQ1286)

I hope that these are the right settings for my tv card. What do you think?
How can I test this?

Kris




-----Oorspronkelijk bericht-----
Van: Andy Walls [mailto:awalls@md.metrocast.net]
Verzonden: za 29-1-2011 14:54
Aan: Discussion list for development of the IVTV driver
CC: kris.marien@kpnmail.nl; ivtv-users@ivtvdriver.org
Onderwerp: Re: [ivtv-devel] [UNKNOWN IVTV CARD]

On Tue, 2011-01-25 at 21:04 +0100, kris.marien@kpnmail.nl wrote:
> I got this from the kern.log file:
>
> ***
> vendor/device: [4444:0016]
> subsystem vendor/device: [1179:0001]
> ***
>
> Card type:
>
> Toshiba PCI TV Tuner type W
>
> on Toshiba Qosmio F10-120 (Laptop)


> What do I do to get this card working?

The ivtv driver doesn't know about this card.

These are the cards the ivtv driver knows about:
$ modinfo ivtv
filename: /lib/modules/2.6.32.14-127.fc12.x86_64/kernel/drivers/media/video/ivtv/ivtv.ko
version: 1.4.1
[...]
parm: cardtype:Only use this option if your card is not detected properly.
Specify card type:
1 = WinTV PVR 250
2 = WinTV PVR 350
3 = WinTV PVR-150 or PVR-500
4 = AVerMedia M179
5 = YUAN MPG600/Kuroutoshikou iTVC16-STVLP
6 = YUAN MPG160/Kuroutoshikou iTVC15-STVLP
7 = YUAN PG600/DIAMONDMM PVR-550 (CX Falcon 2)
8 = Adaptec AVC-2410
9 = Adaptec AVC-2010
10 = NAGASE TRANSGEAR 5000TV
11 = AOpen VA2000MAX-STN6
12 = YUAN MPG600GR/Kuroutoshikou CX23416GYC-STVLP
13 = I/O Data GV-MVP/RX
14 = I/O Data GV-MVP/RX2E
15 = GOTVIEW PCI DVD
16 = GOTVIEW PCI DVD2 Deluxe
17 = Yuan MPC622
18 = Digital Cowboy DCT-MTVP1
19 = Yuan PG600V2/GotView PCI DVD Lite
20 = Club3D ZAP-TV1x01
21 = AverTV MCE 116 Plus
22 = ASUS Falcon2
23 = AverMedia PVR-150 Plus
24 = AverMedia EZMaker PCI Deluxe
25 = AverMedia M104 (not yet working)
26 = Buffalo PC-MV5L/PCI
27 = AVerMedia UltraTV 1500 MCE
0 = Autodetect (default)
-1 = Ignore this card
(array of int)


So you have two choices:

1. You can to try to specify a card with the "cardtype=" module
parameter.

Many of the designs from Taiwan manufacturers are the same, so I'm
guessing one of these card types will work for you:

Cards with older RF tuner assemblies (not likely in a laptop):
"Yuan PG600, Diamond PVR-550" cardtype=7
"GotView PCI DVD2 Deluxe" cardtype=16
"Yuan MPC622" cardtype=17

Cards with an XC3028/XC2028 RF tuner chip (needs xc3028.fw image):
"Yuan PG600-2, GotView PCI DVD Lite" cardtype=19
"Club3D ZAP-TV1x01" cardtype=20
"Buffalo PC-MV5L/PCI" cardtype=26

If you don't need the RF tuner, and only need CVBS or SVideo input, then
cardtype 7 is probably the safest to test with, as it doesn't try to set
any GPIO pins.


2. Add a new card entry in ivtv-cards.c and ivtv-driver.c and recompile
the ivtv module.

The new card entry will likely look very much like some existing card
entry. The hardest part is figuring out the proper GPIO pin settings
and tuner being used. Sometimes the Windows driver *.inf file has the
information, some times it doesn't.

Regards,
Andy