Re: [linux-dvb] saa7134: Asus Tiger revision 1.0, subsys 1043:4857 improvements

2008-03-07 Thread hermann pitton
Hi Hartmut,

Am Freitag, den 07.03.2008, 00:21 +0100 schrieb hermann pitton:
> Am Donnerstag, den 06.03.2008, 22:40 +0100 schrieb Hartmut Hackmann:

[...]
> > > 
> > 
> > 
> > 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
> > 
> 
> Hi Hartmut,
> 
> that was just some fallout in between and I`m sure to have the proper
> testings already. That checksum game is interesting, but whatsoever is
> such hidden something good for, except to cheat.
> 
> What gives me more to worry about recently is, that it is hard for me to
> "illuminate" some last working status of the saa7134-empress in some
> variant I have currently. (I'm down to bit specific operations)
> 
> If pioneers like Geert, Greg or Mans could provide me with some
> saa7134_i2c debug on _start_ last known state and setting the fmt
> successfully, might help.
> 

the mpeg encoder stuff (CTX946) I post on the video4linux-list when I
have some ground, recent ioctl2 stuff oopses on VIDIOC_QUERYCAP and also
with ext_ctrls it fails already on VIDIOC_G_STD. Analog and DVB-T
support could be already added, it behaves here like the md7134 with
FMD1216ME.

Your doubts about the analog audio input pairs on the Asus Tiger Rev.1.0
are correct, but turns out that sound is routed to both (!) from the
break out connectors. We might let it on LINE2 then, assuming this is
tested on the internal panel connection too ...

Also the composite over s-video is functional, which the Tiger seems not
to have.

Concerning the eeprom dump, thought we have now all bytes, at least
prior "eeprom" dumps did not return more. Also currently with the driver
loaded a read attempt returns -EBUSY, else there is no i2c-dev. Might
have forgotten something here, but let me know what you like to see in
case it could become useful.

Cheers,
Hermann








___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] saa7134: Asus Tiger revision 1.0, subsys 1043:4857 improvements

2008-03-06 Thread hermann pitton
Am Donnerstag, den 06.03.2008, 22:40 +0100 schrieb Hartmut Hackmann:
> 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 :01:07.0, rev: 208, irq: 17, latency: 32, mmio: 
> > 0xe800
> > 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
> > ^^
> 
> > 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 :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 
> > 0x4
> > 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
> > ^^
> 
> 
> 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
> 

Hi Hartmut,

that was just some fallout in between and I`m sure to have the proper
testings already. That checksum game is interesting, but whatsoever is
such hidden something good for, except to cheat.

What gives me more to worry about recently is, that it is hard for me to
"illuminate" some last working status of the saa7134-empress in some
variant I have currently. (I'm down to bit specific operations)

If pioneers like Geert, Greg or Mans could provide me with some
saa7134_i2c debug on _start_ last known state and setting the fmt
successfully, might help.

Cheers,
Hermann









___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] saa7134: Asus Tiger revision 1.0, subsys 1043:4857 improvements

2008-03-06 Thread Hartmut Hackmann
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 :01:07.0, rev: 208, irq: 17, latency: 32, mmio: 
> 0xe800
> 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
> ^^

> 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 :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 
> 0x4
> 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
> ^^


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



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] saa7134: Asus Tiger revision 1.0, subsys 1043:4857 improvements

2008-03-05 Thread hermann pitton
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 ...

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 :01:07.0, rev: 208, irq: 17, latency: 32, mmio: 
0xe800
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
^^
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 15 00 ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
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 :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 
0x4
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
^^
saa7133[1]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[1]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 15 00 ff ff ff ff ff ff
saa7133[1]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[1]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[1]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[1]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[1]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[1]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[1]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[1]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[1]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[1]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[1]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[1]: registered device video1 [v4l2]
saa7133[1]: registered device vbi1
saa7133[1]: registered device radio1
saa7133[2]: found at :01:09.0, rev: 209, irq: 20, latency: 32, mmio: 
0xe8002000
saa7133[2]: subsystem: 16be:0010, board: Medion/Creatix CTX953 Hybrid 
[card=134,autodetected]
saa7133[2]: board