By Date: <-- -->
By Thread: <-- -->

Trying to get a Kworld-ATSC110 working

The HDTV Wonder is using the same firmware as the AverMedia card in the DVB
drivers.  I was never able to find out how to extract the firmware from the
ATI driver in Linux.  I know where it is, but it is compressed in a NSIS
install executable and I was never able to extract it on Linux.  The
firmware is different, but it seems to work.  Also, the ATI card does not
officially support QAM, but I believe the AverMedia card.  It might even be
possible that the ATI firmware does not support QAM.  I really don't know
what the difference in the firmware is, but I do know that both versions
work for ATSC.  Since I am not sure on the legality of distributing the ATI
firmware, and I know the AverMedia firmware works and is more easily
obtained, it made sense to just use it.

To "unhide" the tuner there is a sequence of i2c commands that are sent to
the NXT2004.  For the HDTV Wonder this is found around line 1461 of
cx88-cards.c.  Once this is done the tuner module is able to find it and you
should be able to tune analog channels.

Kirk

On 2/11/06, maillist <maillist (at) boilerbots.com> wrote:
>
> Michael Krufky wrote:
> > maillist wrote:
> >
> >>
> >> OK, I have to admit that I don't know exactly what I am trying to do.
> >> But I have burnt a few hours trying.
> >>
> >> I have a Kworld card which is  dual NTSC and ATSC capable. It uses
> >> the Philips TUV1236D network interface module just like the HDTV
> >> wonder and the Avermedia but for the PCI interface it uses the
> >> saa7135 chip like some other cards.
> >>
> >> I can get the composite input and sort of get the TV tuner to work
> >> but I would like to understand what is going on so that I can
> >> hopefully resolve some issues and eventually get the ATSC tuner going.
> >>
> >> So, I run the following command:
> >> modprobe saa7134 gpio_tracking=1 i2c_scan=1
> >>
> >> and this is what I get:
> >>
> >> Feb 11 05:09:58 ford kernel: Linux video capture interface: v1.00
> >> Feb 11 05:09:58 ford kernel: saa7130/34: v4l2 driver version 0.2.14
> >> loaded
> >> Feb 11 05:09:58 ford kernel: ACPI: PCI Interrupt 0000:01:06.0[A] ->
> >> Link [APC3] -> GSI 18 (level, high) -> IRQ 20
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: found at 0000:01:06.0, rev:
> >> 240, irq: 20, latency: 32, mmio: 0xea000000
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: subsystem: 17de:7350, board:
> >> KWORLD ATSC110 [card=89,autodetected]
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: board init: gpio is 10100
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: gpio: mode=0x0000000
> >> in=0x0000100 out=0x0000000 [pre-init]
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: i2c eeprom 00: de 17 50 73
> >> ff ff ff ff ff ff ff ff ff ff ff ff
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: i2c eeprom 10: ff ff ff ff
> >> ff ff ff ff ff ff ff ff ff ff ff ff
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: i2c eeprom 20: ff ff ff ff
> >> ff ff ff ff ff ff ff ff ff ff ff ff
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: i2c eeprom 30: ff ff ff ff
> >> ff ff ff ff ff ff ff ff ff ff ff ff
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: i2c eeprom 40: ff ff ff ff
> >> ff ff ff ff ff ff ff ff ff ff ff ff
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: i2c eeprom 50: ff ff ff ff
> >> ff ff ff ff ff ff ff ff ff ff ff ff
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: i2c eeprom 60: ff ff ff ff
> >> ff ff ff ff ff ff ff ff ff ff ff ff
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: i2c eeprom 70: ff ff ff ff
> >> ff ff ff ff ff ff ff ff ff ff ff ff
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: i2c scan: found device  (at)
> >> 0x14  [???]
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: i2c scan: found device  (at)
> >> 0x16  [???]
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: i2c scan: found device  (at)
> >> 0xa0  [eeprom]
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: registered device video0
> [v4l2]
> >> Feb 11 05:09:58 ford kernel: saa7133[0]: registered device vbi0
> >>
> >>
> >> You see the i2c scan found a few things but I expect more. I expect
> >> to see a tuner at 0xC0 (or somwhere around 0xCx). This is where the
> >> tuv1236 is supposed to live. So why doesn't it show up?
> >>
> >> Am I supposed to load something else first? I have loaded tuner,
> >> bttv, saa7134-dvb, dvb_core in every possible order but yet I can't
> >> get the tuner to show up. However if I put another TV card in, an
> >> Avermedia with a BrookTree device then when the Bttv module loades it
> >> finds the tuner on the Avermedia board and on this KWorld board.
> >>
> >> Anybody know what this is trying to tell me?
> >
> >
> > Try to copy the nxt200x implementation from the AVerMedia AVerTVHD
> > a180.  I programmed this card, and it is also based on saa7135 +
> > nxt2004.  This card uses an ALPS tuner, wich is different from yours,
> > but Kirk Lapray told me that the nxt200x module will "unhide" the
> > tuner's i2c address when loaded.
> >
> > Give that a try, and then see if i2c_scan looks any different.
> >
> > I hope this helps,
> >
> > Michael
> >
> Is it possible that the nxt2004 firmware is customized by each vendor to
> work with their particular configuration?
>
> I understand the ATI HDTV wonder card has the same philims tuv1236D
> module as this card. That is the metal box that contains the nxt2004
> device. Is the ATI card also using the AverMedia firmware and working in
> ATSC mode?
>
> Curt
>
> --
> video4linux-list mailing list
> Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
>
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list