I have a 16 channel DVR card that I recently purchased through eBay that
I haven't had any luck (so far) in identifying to the saa7134 module.
There is no tuner, no radio, and no eeprom.
The card is manufactured by Shenzhen Aopvision Tech, model AP-8008A and
the card info can be viewed at
I don't currently have access to a camera to take any better pictures.
This card consists of a PLX controller and eight saa7130 processors,
running two inputs each. The module sees it as eight different cards.
As this card has so many inputs I was hoping somebody here might have an
idea of what kind card= I should be using. And if not, what info I
should send along that I haven't already.
When running the XP DVR software, SAA7134_ANALG_IN_CTRL1 alternates
from 0xC0 to 0xC2, presumably to capture the two different video inputs
managed by the processor(s). All eight processors regspys look the same.
Regspy output from XP:
SAA7130 Card [7]:
Vendor ID: 0x1131
Device ID: 0x7130
Subsystem ID: 0x00001131
SAA7130 Card - Register Dump:
SAA7134_GPIGPMDE: 000e3c00 (00000000 00001110 00111100
00000000)
SAA7134_GPIGPSTATUS: 000d0000 (00000000 00001101 00000000
00000000)
SAA7134_ANALG_IN_CTRL1: c0
(11000000)
SAA7134_ANALG_ISELECT: 00
(00000000)
SAA7134_VIDEPRT_CTRL0: 0000b000 (00000000 00000000 10110000
00000000)
SAA7134_VIDEPRT_CTRL4: 00000000 (00000000 00000000 00000000
00000000)
SAA7134_VIDEPRT_CTRL8: 00
(00000000)
SAA7134_I2SUTPUT_SELECT: 00
(00000000)
SAA7134_I2SUTPUT_FRMAT: 00
(00000000)
SAA7134_I2SUTPUT_LEVEL: 00
(00000000)
SAA7134_I2S_AUDIUTPUT: 00
(00000000)
SAA7134_TS_PARALLEL: 6c
(01101100)
SAA7134_TS_PARALLEL_SERIAL: bb
(10111011)
SAA7134_TS_SERIAL0: 50
(01010000)
SAA7134_TS_SERIAL1: 01
(00000001)
SAA7134_TS_DMA0: 37
(00110111)
SAA7134_TS_DMA1: 01
(00000001)
SAA7134_TS_DMA2: 00
(00000000)
SAA7134_SPECIAL_MDE: 00
(00000000)
end of dump
lspci -v as follows:
02:08.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
Subsystem: Philips Semiconductors Unknown device 0000
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at e9000000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
02:09.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
Subsystem: Philips Semiconductors Unknown device 0000
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at e9001000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
02:0a.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
Subsystem: Philips Semiconductors Unknown device 0000
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at e9002000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
02:0b.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
Subsystem: Philips Semiconductors Unknown device 0000
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at e9003000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
02:0c.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
Subsystem: Philips Semiconductors Unknown device 0000
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at e9004000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
02:0d.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
Subsystem: Philips Semiconductors Unknown device 0000
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at e9005000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
02:0e.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
Subsystem: Philips Semiconductors Unknown device 0000
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at e9006000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
02:0f.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
Subsystem: Philips Semiconductors Unknown device 0000
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at e9007000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
dmesg as follows:
saa7130[7]: found at 0000:02:0f.0, rev: 1, irq: 11, latency: 32, mmio:
0xe9007000
saa7134: <rant>
saa7134: Congratulations! Your TV card vendor saved a few
saa7134: cents for a eeprom, thus your pci board has no
saa7134: subsystem ID and I can't identify it automatically
saa7134: </rant>
saa7134: I feel better now. , here are the good news:
saa7134: You can use the card=<nrinsmod option to specify
saa7134: which board do you have. The list:
saa7134: card=0 -UNKNWN/GENERIC
saa7134: card=1 -Proteus Pro [philips reference design] 1131:2001
1131:2001
saa7134: card=2 -LifeView FlyVIDE 5168:0138
4e42:0138
saa7134: card=3 -LifeView/Typhoon FlyVIDE 5168:0138
4e42:0138
saa7134: card=4 -EMPRESS 1131:6752
saa7134: card=5 -SKNet Monster TV 1131:4e85
saa7134: card=6 -Tevion MD 9717
saa7134: card=7 -KNC TV-Station RDS / Typhoon TV Tune 1131:fe01
1894:fe01
saa7134: card=8 -Terratec Cinergy 400 TV 153b:1142
saa7134: card=9 -Medion 5044
saa7134: card=10 -Kworld/KuroutoShikou SAA7130-TVPCI
saa7134: card=11 -Terratec Cinergy 600 TV 153b:1143
saa7134: card=12 -Medion 7134 16be:0003
saa7134: card=13 -Typhoon TV+Radio 90031
saa7134: card=14 -ELSA EX-VISIN 300TV 1048:226b
saa7134: card=15 -ELSA EX-VISIN 500TV 1048:226a
saa7134: card=16 -ASUS TV-FM 7134 1043:4842
1043:4830 1043:4840
saa7134: card=17 -APEN VA1000 PWER 1131:7133
saa7134: card=18 -BMK MPEX No Tuner
saa7134: card=19 -Compro VideoMate TV 185b:c100
saa7134: card=20 -Matrox CronosPlus 102b:48d0
saa7134: card=21 -10MNS PCI TV CAPTURE CARD 1131:2001
saa7134: card=22 -AverMedia M156 / Medion 2819 1461:a70b
saa7134: card=23 -BMK MPEX Tuner
saa7134: card=24 -KNC TV-Station DVR 1894:a006
saa7134: card=25 -ASUS TV-FM 7133 1043:4843
saa7134: card=26 -Pinnacle PCTV Stereo (saa7134) 11bd:002b
saa7134: card=27 -Manli MuchTV M-TV002/Behold TV 403 FM
saa7134: card=28 -Manli MuchTV M-TV001/Behold TV 401
saa7134: card=29 -Nagase Sangyo TransGear 3000TV 1461:050c
saa7134: card=30 -Elitegroup ECS TVP3XP FM1216 Tuner Card( 1019:4cb4
saa7134: card=31 -Elitegroup ECS TVP3XP FM1236 Tuner Card 1019:4cb5
saa7134: card=32 -AVACS SmartTV
saa7134: card=33 -AVerMedia DVD EZMaker 1461:10ff
saa7134: card=34 -Noval Prime TV 7133
saa7134: card=35 -AverMedia AverTV Studio 305 1461:2115
saa7134: card=36 -UPMST PURPLE TV 12ab:0800
saa7134: card=37 -Items MuchTV Plus / IT-005
saa7134: card=38 -Terratec Cinergy 200 TV 153b:1152
saa7134: card=39 -LifeView FlyTV Platinum Mini 5168:0212
4e42:0212
saa7134: card=40 -Compro VideoMate TV PVR/FM 185b:c100
saa7134: card=41 -Compro VideoMate TV Gold+ 185b:c100
saa7134: card=42 -Sabrent SBT-TVFM (saa7130)
saa7134: card=43 -:Zolid Xpert TV7134
saa7134: card=44 -Empire PCI TV-Radio LE
saa7134: card=45 -Avermedia AVerTV Studio 307 1461:9715
saa7134: card=46 -AVerMedia Cardbus TV/Radio (E500) 1461:d6ee
saa7134: card=47 -Terratec Cinergy 400 mobile 153b:1162
saa7134: card=48 -Terratec Cinergy 600 TV MK3 153b:1158
saa7134: card=49 -Compro VideoMate Gold+ Pal 185b:c200
saa7134: card=50 -Pinnacle PCTV 300i DVB-T + PAL 11bd:002d
saa7134: card=51 -ProVideo PV952 1540:9524
saa7134: card=52 -AverMedia AverTV/305 1461:2108
saa7134: card=53 -ASUS TV-FM 7135 1043:4845
saa7134: card=54 -LifeView FlyTV Platinum FM / Gold 5168:0214
1489:0214 5168:0304
saa7134: card=55 -LifeView FlyDVB-T DU 5168:0306
saa7134: card=56 -Avermedia AVerTV 307 1461:a70a
saa7134: card=57 -Avermedia AVerTV G 007 FM 1461:f31f
saa7134: card=58 -ADS Tech Instant TV (saa7135) 1421:0350
1421:0351 1421:0370 1421:1370
saa7134: card=59 -Kworld/Tevion V-Stream Xpert TV PVR7134
saa7134: card=60 -LifeView/Typhoon FlyDVB-T Duo Cardbus 5168:0502
4e42:0502
saa7134: card=61 -Philips TUGH DVB-T reference design 1131:2004
saa7134: card=62 -Compro VideoMate TV Gold+II
saa7134: card=63 -Kworld Xpert TV PVR7134
saa7134: card=64 -FlyTV mini Asus Digimatrix 1043:0210
saa7134: card=65 -V-Stream Studio TV Terminator
saa7134: card=66 -Yuan TUN-900 (saa7135)
saa7134: card=67 -Beholder BeholdTV 409 FM 0000:4091
saa7134: card=68 -GoTView 7135 PCI 5456:7135
saa7134: card=69 -Philips EURPA V3 reference design 1131:2004
saa7134: card=70 -Compro Videomate DVB-T300 185b:c900
saa7134: card=71 -Compro Videomate DVB-T200 185b:c901
saa7134: card=72 -RTD Embedded Technologies VFG7350 1435:7350
saa7134: card=73 -RTD Embedded Technologies VFG7330 1435:7330
saa7134: card=74 -LifeView FlyTV Platinum Mini2 14c0:1212
saa7134: card=75 -AVerMedia AVerTVHD MCE A180 1461:1044
saa7134: card=76 -SKNet MonsterTV Mobile 1131:4ee9
saa7134: card=77 -Pinnacle PCTV 40i/50i/110i (saa7133) 11bd:002e
saa7134: card=78 -ASUSTeK P7131 Dual 1043:4862
saa7134: card=79 -Sedna/MuchTV PC TV Cardbus TV/Radio (IT
saa7134: card=80 -ASUS Digimatrix TV 1043:0210
saa7134: card=81 -Philips Tiger reference design 1131:2018
saa7134: card=82 -MSI TV@Anywhere plus 1462:6231
saa7134: card=83 -Terratec Cinergy 250 PCI TV 153b:1160
saa7134: card=84 -LifeView FlyDVB Trio 5168:0319
saa7134: card=85 -AverTV DVB-T 777 1461:2c05
saa7134: card=86 -LifeView FlyDVB-T / Genius VideoWonder D 5168:0301
1489:0301
saa7134: card=87 -ADS Instant TV Duo Cardbus PTV331 0331:1421
saa7134: card=88 -Tevion/KWorld DVB-T 220RF 17de:7201
saa7134: card=89 -ELSA EX-VISIN 700TV 1048:226c
saa7134: card=90 -Kworld ATSC110 17de:7350
saa7134: card=91 -AVerMedia A169 B 1461:7360
saa7134: card=92 -AVerMedia A169 B1 1461:6360
saa7134: card=93 -Medion 7134 Bridge #2 16be:0005
saa7134: card=94 -LifeView FlyDVB-T Hybrid Cardbus 5168:3306
5168:3502
saa7130[7]: subsystem: 1131:0000, board: UNKNWN/GENERIC
[card=0,autodetected]
saa7130[7]: board init: gpio is 10000
saa7130[7]: Huh, no eeprom present (err=-5)?
saa7130[7]: registered device video7 [v4l2]
saa7130[7]: registered device vbi7

Hi Donald!

The card is manufactured by Shenzhen Aopvision Tech, model AP-8008A and
the card info can be viewed at

This card consists of a PLX controller and eight saa7130 processors,
running two inputs each. The module sees it as eight different cards.

The PLX "controller" is just a PCI-to-PCI bridge; if it were an actual
controller it wouldn't be transparent - you wouldn't see the Philips chips in
a PCI scan.

But you do - so you'll have to manage every single one of those. Now since the
card's maker didn't give them a subsystem ID, you'll still have to
say "card=xx" after support for them has been added. And we'll have to hope
that each of the eight chips is connected in the same way.

Your observations on input usage provide a starting point for making such a
card entry. Are the inputs Composite or SVideo?

regards,
Peter

I realize that the PLX chip is just a bridge. Was information I was
providing in hopes that somebody might be able to say "Hey! That's a
XXXX card, and your card=xx,xx,xx,xx,xx,xx,xx,xx!"

All 16 inputs of this card are composite.

Regspy output on each one of the saa7130s is the same when activated by
the Windows DVR software so I would think err, I mean hope, that they
are managed the same way. I can't follow the traces on the cards to the
saa7130s very well the video chips are covered by heatsinks that
overhang the chips. If it becomes necessary I'll remove the heatsinks.

Donald

Peter Missel wrote:
Hi Donald!


>The card is manufactured by Shenzhen Aopvision Tech, model AP-8008A and
>the card info can be viewed at
>
>>
>This card consists of a PLX controller and eight saa7130 processors,
>running two inputs each. The module sees it as eight different cards.
>
>
The PLX "controller" is just a PCI-to-PCI bridge; if it were an actual
controller it wouldn't be transparent - you wouldn't see the Philips chips in
a PCI scan.

But you do - so you'll have to manage every single one of those. Now since the
card's maker didn't give them a subsystem ID, you'll still have to
say "card=xx" after support for them has been added. And we'll have to hope
that each of the eight chips is connected in the same way.

Your observations on input usage provide a starting point for making such a
card entry. Are the inputs Composite or SVideo?

regards,
Peter

Hi Donald!

Sunday 12 November 2006 14:02, Donald Bailey wrote:
I realize that the PLX chip is just a bridge. Was information I was
providing in hopes that somebody might be able to say "Hey! That's a
XXXX card, and your card=xx,xx,xx,xx,xx,xx,xx,xx!"

All 16 inputs of this card are composite.

Regspy output on each one of the saa7130s is the same when activated by
the Windows DVR software so I would think err, I mean hope, that they
are managed the same way. I can't follow the traces on the cards to the
saa7130s very well the video chips are covered by heatsinks that
overhang the chips. If it becomes necessary I'll remove the heatsinks.

I don't think you'll have to. From your regspy work, we already know what
inputs it uses - and making a card entry for a unit that uses neither tuners
nor GPI pins is rather trivial.

regards,
Peter

Peter Missel wrote:
Hi Donald!

Sunday 12 November 2006 14:02, Donald Bailey wrote:

>I realize that the PLX chip is just a bridge. Was information I was
>providing in hopes that somebody might be able to say "Hey! That's a
>XXXX card, and your card=xx,xx,xx,xx,xx,xx,xx,xx!"
>>
>All 16 inputs of this card are composite.
>>
>Regspy output on each one of the saa7130s is the same when activated by
>the Windows DVR software so I would think err, I mean hope, that they
>are managed the same way. I can't follow the traces on the cards to the
>saa7130s very well the video chips are covered by heatsinks that
>overhang the chips. If it becomes necessary I'll remove the heatsinks.
>
>
I don't think you'll have to. From your regspy work, we already know what
inputs it uses - and making a card entry for a unit that uses neither tuners
nor GPI pins is rather trivial.

regards,
Peter

Does this mean that something may be forthcoming? :-)

Donald

Wednesday 15 November 2006 00:10, Donald Bailey wrote:
Peter Missel wrote:
>overhang the chips. If it becomes necessary I'll remove the heatsinks.
>
I don't think you'll have to. From your regspy work, we already know what
inputs it uses - and making a card entry for a unit that uses neither
tuners nor GPI pins is rather trivial.

regards,
Peter

Does this mean that something may be forthcoming? :-)

Not from my end, sorry - I have absolutely zero time at the moment.

But maybe the regular maintainer of the saa713x driver feels inclined to add
the few lines of code that this requires?

Peter

Donald Bailey wrote:
Peter Missel wrote:
>Hi Donald!
>>
>Sunday 12 November 2006 14:02, Donald Bailey wrote:
>
I realize that the PLX chip is just a bridge. Was information I was
providing in hopes that somebody might be able to say "Hey! That's a
XXXX card, and your card=xx,xx,xx,xx,xx,xx,xx,xx!"

All 16 inputs of this card are composite.

Regspy output on each one of the saa7130s is the same when activated by
the Windows DVR software so I would think err, I mean hope, that
they
are managed the same way. I can't follow the traces on the cards to
the
saa7130s very well the video chips are covered by heatsinks that
overhang the chips. If it becomes necessary I'll remove the heatsinks.

>>
>I don't think you'll have to. From your regspy work, we already know
>what inputs it uses - and making a card entry for a unit that uses
>neither tuners nor GPI pins is rather trivial.
>>
>regards,
>Peter
>>
>
Does this mean that something may be forthcoming? :-)

Donald

Sunday 19 November 2006 15:43, Donald Bailey wrote:
Donald Bailey wrote:
Peter Missel wrote:
>Hi Donald!
>>
This card has two composite inputs on each saa7130. input is active
when SAA7134_ANALG_IN_CTRL1 is 0xC0, and the other is active when
SAA7134_ANALG_IN_CTRL1 IS 0XC2. Based on the following RegSpy output,
would the code that follows that be even remotely close to functional
for me?
[SAA7134_BARD_AP_8008A_16_PRT] = {
.name = "APVision AP-8008A 16CH/240fps
Capture Card",
.audio_clock = 0x00187de7,
.tuner_type = TUNER_ABSENT,
.radio_type = UNSET,
.tuner_addr = ADDR_UNSET,
.radio_addr = ADDR_UNSET,
.inputs = {{
.name = name_comp1,
.gpio = 0xe3c00,
.vmux = 0,
},{
.name = name_comp2,
.gpio = 0xe3c00,
.vmux = 2,
}},
},

Looks quite good. My comments:

* You need to define SAA7134_BARD_AP_8008A_16_PRT (using the next available
number).
* .gpio members are not needed if you don't actually change any GPI

And then, if it does something, then it's good :)

regards,
Peter

Peter Missel wrote:
Sunday 19 November 2006 15:43, Donald Bailey wrote:

>Donald Bailey wrote:
>
Peter Missel wrote:

Hi Donald!


>This card has two composite inputs on each saa7130. input is active
>when SAA7134_ANALG_IN_CTRL1 is 0xC0, and the other is active when
>SAA7134_ANALG_IN_CTRL1 IS 0XC2. Based on the following RegSpy output,
>would the code that follows that be even remotely close to functional
>for me?
>[SAA7134_BARD_AP_8008A_16_PRT] = {
>.name = "APVision AP-8008A 16CH/240fps
>Capture Card",
>.audio_clock = 0x00187de7,
>.tuner_type = TUNER_ABSENT,
>.radio_type = UNSET,
>.tuner_addr = ADDR_UNSET,
>.radio_addr = ADDR_UNSET,
>.inputs = {{
>.name = name_comp1,
>.gpio = 0xe3c00,
>.vmux = 0,
>},{
>.name = name_comp2,
>.gpio = 0xe3c00,
>.vmux = 2,
>}},
>},
>
>
Looks quite good. My comments:

* You need to define SAA7134_BARD_AP_8008A_16_PRT (using the next available
number).
* .gpio members are not needed if you don't actually change any GPI

And then, if it does something, then it's good :)

regards,
Peter

And if I get nothing?

Donnie

Sunday 19 November 2006 16:14, Donald Bailey wrote:
Peter Missel wrote:
And then, if it does something, then it's good :)

And if I get nothing?

Then first of all make sure (1) that you've loaded eight instances of the
driver, all with the correct card=n parameter, and (2) that you've actually
picked the one you're feeding your test signal into ;)

regards,
Peter

Peter Missel wrote:
Sunday 19 November 2006 16:14, Donald Bailey wrote:

>Peter Missel wrote:
>
And then, if it does something, then it's good :)


>And if I get nothing?
>>
>
>
Then first of all make sure (1) that you've loaded eight instances of the
driver, all with the correct card=n parameter, and (2) that you've actually
picked the one you're feeding your test signal into ;)

regards,
Peter

I added #define SAA7134_BARD_AP_8008A_16_PRT 100 to saa7134.h.

I've set the card=100,100,100,100,100,100,100,100 and checked all 16
inputs with xawtv. I do have the option to pick Composite1/2, and chose
NTSC. After putting a camera on all 16 inputs I only get a black
screen. Would this be caused by an incorrect GPI?

Donnie

Sunday 19 November 2006 16:32, Donald Bailey wrote:
I've set the card=100,100,100,100,100,100,100,100 and checked all 16
inputs with xawtv. I do have the option to pick Composite1/2, and chose
NTSC. After putting a camera on all 16 inputs I only get a black
screen. Would this be caused by an incorrect GPI?

Maybe this is where the real work starts. You have 7130 chips there. That
means you can measure - or even trace by looking - what GPI pins on the chip
are being used, and where they're going. That'll provide a hint on whether
there's something on the board that needs a GPI to operate.

Also, you might want to copy the GPI direction settings (in/out) from your
regspy results into a .gpiomask member of your card structure. Having .gpio
members in the input substructures does nothing before you define the pins
you're changing as outputs.

regards,
Peter

Peter Missel wrote:
Sunday 19 November 2006 16:32, Donald Bailey wrote:

>I've set the card=100,100,100,100,100,100,100,100 and checked all 16
>inputs with xawtv. I do have the option to pick Composite1/2, and chose
>NTSC. After putting a camera on all 16 inputs I only get a black
>screen. Would this be caused by an incorrect GPI?
>
>
Maybe this is where the real work starts. You have 7130 chips there. That
means you can measure - or even trace by looking - what GPI pins on the chip
are being used, and where they're going. That'll provide a hint on whether
there's something on the board that needs a GPI to operate.

Also, you might want to copy the GPI direction settings (in/out) from your
regspy results into a .gpiomask member of your card structure. Having .gpio
members in the input substructures does nothing before you define the pins
you're changing as outputs.

regards,
Peter

Peter Missel wrote:
Sunday 19 November 2006 16:32, Donald Bailey wrote:

>I've set the card=100,100,100,100,100,100,100,100 and checked all 16
>inputs with xawtv. I do have the option to pick Composite1/2, and chose
>NTSC. After putting a camera on all 16 inputs I only get a black
>screen. Would this be caused by an incorrect GPI?
>
>
Maybe this is where the real work starts. You have 7130 chips there. That
means you can measure - or even trace by looking - what GPI pins on the chip
are being used, and where they're going. That'll provide a hint on whether
there's something on the board that needs a GPI to operate.

Also, you might want to copy the GPI direction settings (in/out) from your
regspy results into a .gpiomask member of your card structure. Having .gpio
members in the input substructures does nothing before you define the pins
you're changing as outputs.

regards,
Peter

It appears that the GPI pins aren't used for selecting video inputs.
They only seem to go to the alarm input headers on the card, used for
door/window switches, etc, as a DVR security device.

Donnie

Donald Bailey wrote:
Peter Missel wrote:
>Sunday 19 November 2006 16:32, Donald Bailey wrote:
>
I've set the card=100,100,100,100,100,100,100,100 and checked all 16
inputs with xawtv. I do have the option to pick Composite1/2, and chose
NTSC. After putting a camera on all 16 inputs I only get a black
screen. Would this be caused by an incorrect GPI?

>>
>Maybe this is where the real work starts. You have 7130 chips
>there. That means you can measure - or even trace by looking - what
>GPI pins on the chip are being used, and where they're going.
>That'll provide a hint on whether there's something on the board that
>needs a GPI to operate.
>>
>Also, you might want to copy the GPI direction settings (in/out)
>from your regspy results into a .gpiomask member of your card
>structure. Having .gpio members in the input substructures does
>nothing before you define the pins you're changing as outputs.
>>
>regards,
>Peter
>>
>
After scratching my head for a bit I plugged in a bttv tuner card
suspecting that my troubles might be xawtv. And they were.

After straightening out xawtv to get a channel tuned with the bttv card
I switched which /dev/videoN I was using to one of the saa7130s with the
snippit of code I patched in and low and behold, video.

So, now my question is, how does one submit a patch and to whom does it
go to, and whom does a request for a card number go to?

Donnie