From: Hartmut Hackmann <hartmut.hackmann@t-online.de>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: video4linux-list@redhat.com, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] saa7134: Asus Tiger revision 1.0, subsys 1043:4857 improvements
Date: Thu, 06 Mar 2008 22:40:02 +0100 [thread overview]
Message-ID: <47D064B2.6010803@t-online.de> (raw)
In-Reply-To: <1204753679.6717.29.camel@pc08.localdom.local>
Hi, Hermann
hermann pitton schrieb:
> Hi, Harmut,
>
> was able to purchase such a device recently.
>
> For me it looks like they have been on OEM stuff only previously.
> The panel for the internal connectors is soldered, the analog audio out
> is there too and fine.
>
> For all what I could look up, it had never support for the PC-39 remote
> we added for revision 2.0, since all seen so far comes up with gpio init
> 0, the remote IRQ to sample from is never active.
>
> Folks, please report if it comes with that RC5 style remote too.
>
> It has a firmware eeprom.
>
> It turns out, and some previous reports pointed to it without to become
> speficic, but contradictions on what the ms driver does on antenna input
> switching, that this one has only a male FM connector and a female RF
> connector.
>
> So, currently we force people with that card to put the DVB-T antenna
> input on the male FM-connector, which might be quit inconvenient ...
>
indeed ;-)
> If nobody disagrees, and also my thesis of the not ever delivered remote
> is right, we should change the auto detection to use card=81, the
> Philips Tiger reference design you developed on.
>
> Cheers,
> Hermann
>
>
> Stuff currently in that machine. We have also one byte different in the
> eeprom here.
>
> Linux video capture interface: v2.00
> saa7130/34: v4l2 driver version 0.2.14 loaded
> saa7133[0]: found at 0000:01:07.0, rev: 208, irq: 17, latency: 32, mmio: 0xe8000000
> saa7133[0]: subsystem: 1043:4857, board: Philips Tiger reference design [card=81,insmod option]
> saa7133[0]: board init: gpio is 0
> saa7133[0]: i2c eeprom 00: 43 10 57 48 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
> saa7133[0]: i2c eeprom 10: 00 01 20 00 ff 20 ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff 00 cb ff ff ff ff
> ^^
<snip>
> tuner' 2-004b: chip found @ 0x96 (saa7133[0])
> tda829x 2-004b: setting tuner address to 61
> tda829x 2-004b: type set to tda8290+75a
> saa7133[0]: registered device video0 [v4l2]
> saa7133[0]: registered device vbi0
> saa7133[0]: registered device radio0
> saa7133[1]: found at 0000:01:08.0, rev: 208, irq: 19, latency: 32, mmio: 0xe8001000
> saa7133[1]: subsystem: 1043:4862, board: ASUSTeK P7131 Dual [card=78,autodetected]
> saa7133[1]: board init: gpio is 0 <------ remote sensor is broken, else 0x40000
> input: saa7134 IR (ASUSTeK P7131 Dual) as /class/input/input6
> tuner' 3-004b: chip found @ 0x96 (saa7133[1])
> tda829x 3-004b: setting tuner address to 61
> tda829x 3-004b: type set to tda8290+75a
> saa7133[1]: i2c eeprom 00: 43 10 62 48 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
> saa7133[1]: i2c eeprom 10: 00 01 20 00 ff 20 ff ff ff ff ff ff ff ff ff ff
> saa7133[1]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff 00 d6 ff ff ff ff
> ^^
<snip>
I guess you checked the entire eepron content ;-)
According to the documentation i have, there is no config byte describing the
assignment of antenna sockets. The document says that this byte is a checksum!!!
I will try to get some information.
I found one discrepancy:
The Tiger uses LINE1 for the audio baseband inputs while the ASUS uses LINE2.
Can you cross check this?
Best regards
Hartmut
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-03-06 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 21:47 saa7134: Asus Tiger revision 1.0, subsys 1043:4857 improvements hermann pitton
2008-03-06 21:40 ` Hartmut Hackmann [this message]
2008-03-06 23:21 ` [linux-dvb] " hermann pitton
2008-03-08 0:17 ` hermann pitton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47D064B2.6010803@t-online.de \
--to=hartmut.hackmann@t-online.de \
--cc=hermann-pitton@arcor.de \
--cc=linux-dvb@linuxtv.org \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.