If you can get me the datasheets I'll be happy to have a crack at them... but I don't have time to wade through lots of partially undocumented Linux source without knowing what it's doing! I really need datasheets.

DVB is MPEG, so no, sorry. No datasheets so I can't!

Best place to look is wikipedia for Hauppauge- there's a list of WinTV cards and which chipsets they use. You should be able to get an SD (non HD) card pretty cheap these days!
If you're using a Sam 460, you will need a 3.3V Cx2388x card, not the Brooktree chipset.

Today has seen a miracle performed. For the first time since the Dark Ages, an update to the AmigaOS 4 TV-card prorgam AmiTV has been released. This is not a full release, just a build to let people play around and give feedback.
Among the features are:
* Brooktree Bt848/Bt878 chipset support
* Conexant Cx23881/Cx23882/Cx23883 chipset support
* Video->System Memory->Workbench window support
* Video->System Memory->Picasso96 PIP (overlay) window support
* Video->Picasso96 PIP (overlay) DMA window support (may crash!)
* Resizable window
* Quit button.

Support is planned for NTSC, but currently only PAL is supported.
Using overlay can crash the system occasionally when compositing is turned on.
Using video->PIP directly uses no CPU time. Going via system memory uses substantially more CPU time. Not using overlay at all is VERY SLOW. Note that RadeonHD drivers do not have overlay support.
If you have a CX2388x card and a Bt8x8 card, use the command line parameter "NOCX2388x" to force it to use the Bt8x8 card.

If you use this program, DO save your work first.

Please send any feedback/donations/X1000s to me at "ian.gledhill@btinternit.com" (but it's a nEt not a nIt) or just post your findings here.

Planned for the future:
NTSC support
Interrupt driven video->system->PIP support (need Hyperion to tell me why the system hangs solid - waiting on an answer).
Tuner support - at least of the tuner on my TV card :P

What is not planned:
USB TV cards - there's no documentation out there, so I can't do it.
MPEG HDTV cards - ditto.
MPEG encoder chips - ditto.

What may be planned:
Philips SDTV chipset support - if I can find a card with it on (i.e. the PVR350) and enough time to do it (unlikely for the near future).

Any feedback greatly appreciated though!

Get it here:
http://www.mutant-caterpillar.co.uk/ian_stuff/AmiTV_20120207.lha

Given Adobe don't let the source out, and they're the only ones who can do it, it'd have to be a heck of a big bounty!

Yes, Franko and our favourite Barry joined forces to take over AW.net, and the server couldn't stand it and committed suicide.[1]


[1] This may, in fact, not be the case. Caveat lector.

If your card has a 3.3V compliant slot, it's a 3.3V compliant card!

That said if you do try it and everyone dies suddenly, it's not my fault. :) I'd do it without a second thought though. It is definitely supported on non-classics, is it? I presume it is.

I've not heard of a firmware on a TV card like this... I don't believe there is one here anyway.

Must be something I'm missing though. Most confusing...

It's pin A, as it should be.

I think I've tried everything I can think of now, I really don't know what to do to be honest. It just never raises the interrupt!
A shame, as I can't get this working properly without interrupts, and this card has the MPEG encoder and DVB-T decoder too...

Not sure but I'm pretty sure I tried both...

Hmmm... maybe it doesn't use a PCI bridge as such then. It's a multifunction device but the tree doesn't show a bridge in ranger.

But then why does the interrupt never trigger? Looking at the linux source, they just enable interrupts using the IRQ and it works - but I get nothing.

The two other devices have much lower IRQ numbers, in the 40s, I think it was - the 23882 has 66!

Thanks to both of your for your replies!

@Centaurz

I've not seen that page before, thanks for pointing me to it!

@Hans

(This is on my Sam 440ep)
The IRQ number is 66. The IRQ lane is 0x32.
How can I find out what the correct IRQ line is for the PCI slot? There's only one slot. I noticed the IRQ lines for the onboard bits are 0x1B and 0x1D - I tried setting the IRQ line to 0x1C and 0x1F in the PCI Config space but still didn't trigger any interrupts. I set it by using WriteConfigByte to 0x3C.

Thanks again for your help - I hope I can get this working! At the moment I have to use a busy loop to detect when the interrupt is raised manually... but it'd be very cool to have it all running at max speed.

Hello people,

Quick Question....

as some of you may know I have partially working TV card drives, but the main problem (apart from endian-ness issues) is the lack of interrupt.

On my Bt8x8 boards, the interrupts fire just fine. Actually, too fine - if the picture becomes unstable it fires off too many and crashes the VIA southbridge on my A1.

On my Cx2388x boards, I get nothing.
I think that this is because the C2388x board uses a PCI bridge, as it's a multi-function card. My understanding is that the interrupt for the CX2388x chip may be INTA# as normal, but by the time it's crossed the bridge, it could be any interrupt.

Hence my question - how can I respond to an interrupt on the other INTx# channels? The interrupt is raised correctly, but my interrupt just never gets called. Code works fine for the bt8x8.
I'm just using MapInterrupt and adding an interrupt vector from that at the moment.

Can anyone help?

Try clearing the NVRAM too - I can't remember if there's a jumper to do it, but just removing the battery for a short while will work too. Don't think it'll work but....

I presume you've read and re-read the manual to make sure it's connected, correctly. Make sure the reset switch is correctly connected especially. :)

Shouldn't be the PSU, not if it's booting (as it looks like it is). Some larger PSUs don't work with low drain boards like the Sam, but it sounds like it's working.

I would still strongly suggest connecting them up to an LCD monitor or TV via DVI, even if only to rule it out. It's not to do with the number of pins, I believe, I think there's an extra component inside the DVI->VGA adaptor that comes with Sams.

The DVI to VGA adaptor supplied with a Sam is not standard!

Use the one that came with it, and it'll work fine!

For it to run at twice the speed of an 060 on a Sam 440, though.. that's not bad. :)

Funny thing happened while trying this on my Sam440@600 (the OS3 version, just for the heck of it).

When I downloaded it, installed it, and ran it, it ran quite well. In fact, even on my little Sam, it was noticeably faster, probably twice as fast, as my 68060@50 in my 4000. It booted, I opened the !SICK window, I ran the app... and nothing. After about 3 minutes (takes about 20 seconds I think on the 4000) it opened the window, started to measure timers... and hung solid.
Tried rebooting, and it wouldn't run, just a black screen.
Have never been able to run it since. Weeeeird.

As for my 4000, it bombed out with a badly synced screen, but I think it's a hardware failure. My keyboard keeps on locking up too, so I'm going to change all the capacitors next week, as that'll probably help (and it needs doing anyway).

Right, I'm running the 68k version right now.
It's not fast. :) This on a 68060@50 on my CS-PPC.

Once it booted I ran !SICK and it's still running.

Note the basic install opened the screen on an AGA screen, not an RTG one, so make sure you have a monitor on the RGB port.

Incidentally, it fails to open audio: if your AHI preferences are wrong. I'm using a USB soundcard.

I may not have time to complete the benchmark but will try to get results at some point.

Absolutely. If Trevor were trying to convince a venture capitalist, he wouldn't have a whelk's chance in a supernova, the risks are WAY too high.

Luckily, Trevor IS the venture capitalist. :)