Compile error saa7134 - compro videomate S350

Compile error saa7134 - compro videomate S350

[Dominic Fernandes]

Hi,

I need help to compile v4l-dvb drivers for saa7134 modules. 
I'm new to v4l-dvb not sure how to get past the errors concerning
undefined declarations found in saa7134-inputs.c file for the videomate
S350 board, saying ir_codes, mask_keycodes, mask_keydown as undeclared:

snip:-

make[2]: Entering directory `/usr/src/linux-headers-2.6.31-14-generic'
  CC [M]  /home/tvbox/v4l-dvb/v4l/saa7134-input.o
/home/tvbox/v4l-dvb/v4l/saa7134-input.c: In function 'build_key':
/home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: 'ir_codes' undeclared (first use in this function)
/home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: (Each undeclared identifier is reported only once
/home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: for each function it appears in.)
/home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: 'ir_codes_videomate_s350' undeclared (first use in this function)
/home/tvbox/v4l-dvb/v4l/saa7134-input.c:91: error: 'mask_keycode' undeclared (first use in this function)
/home/tvbox/v4l-dvb/v4l/saa7134-input.c:92: error: 'mask_keydown' undeclared (first use in this function)
make[3]: *** [/home/tvbox/v4l-dvb/v4l/saa7134-input.o] Error 1
make[2]: *** [_module_/home/tvbox/v4l-dvb/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/tvbox/v4l-dvb/v4l'
make: *** [all] Error 2

background:
Justbought last week a new compro videomate s350 (dvb-s) card after seeing
some positive feedback on forumes saying it is working.  But the card I
got has a newer chip set incorporating a saa7135 device and after some
searching found someone else also had the same issue back in June but
managed to fix it with a few changes.  I trying to re-produce the
actions (see link below) and re-build the drivers but I'm stuck at the
compile stage (make all). 

http://osdir.com/ml/linux-media/2009-06/msg01256.html

Can someone advise me on how get past the make error?

Thanks,
Dominic



      

Re: Compile error saa7134 - compro videomate S350

[hermann pitton]

Hi Dominic,

Am Montag, den 23.11.2009, 10:01 -0800 schrieb Dominic Fernandes:
> Hi,
> 
> I need help to compile v4l-dvb drivers for saa7134 modules. 
> I'm new to v4l-dvb not sure how to get past the errors concerning
> undefined declarations found in saa7134-inputs.c file for the videomate
> S350 board, saying ir_codes, mask_keycodes, mask_keydown as undeclared:
> 
> snip:-
> 
> make[2]: Entering directory `/usr/src/linux-headers-2.6.31-14-generic'
>   CC [M]  /home/tvbox/v4l-dvb/v4l/saa7134-input.o
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c: In function 'build_key':
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: 'ir_codes' undeclared (first use in this function)
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: (Each undeclared identifier is reported only once
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: for each function it appears in.)
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: 'ir_codes_videomate_s350' undeclared (first use in this function)
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c:91: error: 'mask_keycode' undeclared (first use in this function)
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c:92: error: 'mask_keydown' undeclared (first use in this function)
> make[3]: *** [/home/tvbox/v4l-dvb/v4l/saa7134-input.o] Error 1
> make[2]: *** [_module_/home/tvbox/v4l-dvb/v4l] Error 2
> make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic'
> make[1]: *** [default] Error 2
> make[1]: Leaving directory `/home/tvbox/v4l-dvb/v4l'
> make: *** [all] Error 2
> 
> background:
> Justbought last week a new compro videomate s350 (dvb-s) card after seeing
> some positive feedback on forumes saying it is working.  But the card I
> got has a newer chip set incorporating a saa7135 device and after some
> searching found someone else also had the same issue back in June but
> managed to fix it with a few changes.  I trying to re-produce the
> actions (see link below) and re-build the drivers but I'm stuck at the
> compile stage (make all). 
> 
> http://osdir.com/ml/linux-media/2009-06/msg01256.html
> 
> Can someone advise me on how get past the make error?
> 
> Thanks,
> Dominic
> 

hm, likely you are on some older/other stuff.

Igor had some merge conflict previously for the S350.

Can't see it with current linuxtv.org mercurial v4l-dvb.

Please try with that.

Cheers,
Hermann

Re: Compile error saa7134 - compro videomate S350

[Dominic Fernandes]

Hi Hermann,

Thanks for responding. I managed to do the compile and install this time without errors on a fresh copy of the v4l-dvb drivers.
 
However, from the thread (link) it said  Changing the PCI Vendor
ID to 0x7133 in the S350 patch, - which file and location would specify this?

At the moment the dvb-s card is recognised as the compro T750 card (I made the other mod of changing the gpio to xc000 in saa7134-cards):

   6.008121] saa7130/34: v4l2 driver version 0.2.15 loaded
[    6.008173] saa7134 0000:03:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    6.008180] saa7133[0]: found at 0000:03:01.0, rev: 209, irq: 17, latency: 64, mmio: 0xcfcff000
[    6.008186] saa7133[0]: subsystem: 185b:c900, board: Compro VideoMate T750 [card=139,autodetected]
[    6.008200] saa7133[0]: board init: gpio is 843f00
[    6.008205] IRQ 17/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[    6.160030] saa7133[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
[    6.160052] saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff
[    6.160071] saa7133[0]: i2c eeprom 20: 01 40 01 02 02 01 03 01 08 ff 00 87 ff ff ff ff
[    6.160091] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    6.160109] saa7133[0]: i2c eeprom 40: ff d6 00 c0 86 1c 02 01 02 ff ff ff ff ff ff ff
[    6.160133] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb
[    6.160144] saa7133[0]: i2c eeprom 60: 35 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    6.160156] saa7133[0]: i2c eeprom 70: 00 00 00 01 4e c1 ff ff ff ff ff ff ff ff ff ff
[    6.160167] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    6.160178] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    6.160190] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    6.160201] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    6.160212] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    6.160223] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    6.160235] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    6.160246] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[    6.313949] saa7133[0]: registered device video0 [v4l2]
[    6.313978] saa7133[0]: registered device vbi0
[    6.314003] saa7133[0]: registered device radio0

thanks,
Dominic





----- Original Message ----
From: hermann pitton <hermann-pitton@arcor.de>
To: Dominic Fernandes <dalf198@yahoo.com>
Cc: linux-media@vger.kernel.org
Sent: Tue, November 24, 2009 1:12:54 AM
Subject: Re: Compile error saa7134 - compro videomate S350

Hi Dominic,

Am Montag, den 23.11.2009, 10:01 -0800 schrieb Dominic Fernandes:
> Hi,
> 
> I need help to compile v4l-dvb drivers for saa7134 modules. 
> I'm new to v4l-dvb not sure how to get past the errors concerning
> undefined declarations found in saa7134-inputs.c file for the videomate
> S350 board, saying ir_codes, mask_keycodes, mask_keydown as undeclared:
> 
> snip:-
> 
> make[2]: Entering directory `/usr/src/linux-headers-2.6.31-14-generic'
>   CC [M]  /home/tvbox/v4l-dvb/v4l/saa7134-input.o
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c: In function 'build_key':
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: 'ir_codes' undeclared (first use in this function)
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: (Each undeclared identifier is reported only once
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: for each function it appears in.)
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: 'ir_codes_videomate_s350' undeclared (first use in this function)
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c:91: error: 'mask_keycode' undeclared (first use in this function)
> /home/tvbox/v4l-dvb/v4l/saa7134-input.c:92: error: 'mask_keydown' undeclared (first use in this function)
> make[3]: *** [/home/tvbox/v4l-dvb/v4l/saa7134-input.o] Error 1
> make[2]: *** [_module_/home/tvbox/v4l-dvb/v4l] Error 2
> make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic'
> make[1]: *** [default] Error 2
> make[1]: Leaving directory `/home/tvbox/v4l-dvb/v4l'
> make: *** [all] Error 2
> 
> background:
> Justbought last week a new compro videomate s350 (dvb-s) card after seeing
> some positive feedback on forumes saying it is working.  But the card I
> got has a newer chip set incorporating a saa7135 device and after some
> searching found someone else also had the same issue back in June but
> managed to fix it with a few changes.  I trying to re-produce the
> actions (see link below) and re-build the drivers but I'm stuck at the
> compile stage (make all). 
> 
> http://osdir.com/ml/linux-media/2009-06/msg01256.html
> 
> Can someone advise me on how get past the make error?
> 
> Thanks,
> Dominic
> 

hm, likely you are on some older/other stuff.

Igor had some merge conflict previously for the S350.

Can't see it with current linuxtv.org mercurial v4l-dvb.

Please try with that.

Cheers,
Hermann


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html



      

Re: Compile error saa7134 - compro videomate S350

[hermann pitton]

Hi Dominic,

Am Dienstag, den 24.11.2009, 10:01 -0800 schrieb Dominic Fernandes:
> Hi Hermann,
> 
> Thanks for responding. I managed to do the compile and install this time without errors on a fresh copy of the v4l-dvb drivers.

Good. On a short look.
 
> However, from the thread (link) it said  Changing the PCI Vendor
> ID to 0x7133 in the S350 patch, - which file and location would specify this?

That won't work, since the T750 has already the same PCI subsystem with
some saa7133. (can be saa7133, 7135 or saa7131e, no way to detect)

Also Jan declared for sure to have a saa7130. Detection is correct so
far, but now we must either kick out the T750 or try with some eeprom
detection. Known problem for Compro, we try to guess on tuner types
then, but I don't like it much and they should care themselves or
provide the eeprom tables for card types..

> At the moment the dvb-s card is recognised as the compro T750 card (I made the other mod of changing the gpio to xc000 in saa7134-cards):

Can't tell much without any such device, but if OK, to force card=169
should work then for you with that change?

In that case, we still would create a new card entry for your saa7135
device.

Cheers,
Hermann

>    6.008121] saa7130/34: v4l2 driver version 0.2.15 loaded
> [    6.008173] saa7134 0000:03:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> [    6.008180] saa7133[0]: found at 0000:03:01.0, rev: 209, irq: 17, latency: 64, mmio: 0xcfcff000
> [    6.008186] saa7133[0]: subsystem: 185b:c900, board: Compro VideoMate T750 [card=139,autodetected]
> [    6.008200] saa7133[0]: board init: gpio is 843f00
> [    6.008205] IRQ 17/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
> [    6.160030] saa7133[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
> [    6.160052] saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff
> [    6.160071] saa7133[0]: i2c eeprom 20: 01 40 01 02 02 01 03 01 08 ff 00 87 ff ff ff ff
> [    6.160091] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160109] saa7133[0]: i2c eeprom 40: ff d6 00 c0 86 1c 02 01 02 ff ff ff ff ff ff ff
> [    6.160133] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb
> [    6.160144] saa7133[0]: i2c eeprom 60: 35 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160156] saa7133[0]: i2c eeprom 70: 00 00 00 01 4e c1 ff ff ff ff ff ff ff ff ff ff
> [    6.160167] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160178] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160190] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160201] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160212] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160223] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160235] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160246] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.313949] saa7133[0]: registered device video0 [v4l2]
> [    6.313978] saa7133[0]: registered device vbi0
> [    6.314003] saa7133[0]: registered device radio0
> 
> thanks,
> Dominic
> 
> 
> 
> 
> 
> ----- Original Message ----
> From: hermann pitton <hermann-pitton@arcor.de>
> To: Dominic Fernandes <dalf198@yahoo.com>
> Cc: linux-media@vger.kernel.org
> Sent: Tue, November 24, 2009 1:12:54 AM
> Subject: Re: Compile error saa7134 - compro videomate S350
> 
> Hi Dominic,
> 
> Am Montag, den 23.11.2009, 10:01 -0800 schrieb Dominic Fernandes:
> > Hi,
> > 
> > I need help to compile v4l-dvb drivers for saa7134 modules. 
> > I'm new to v4l-dvb not sure how to get past the errors concerning
> > undefined declarations found in saa7134-inputs.c file for the videomate
> > S350 board, saying ir_codes, mask_keycodes, mask_keydown as undeclared:
> > 
> > snip:-
> > 
> > make[2]: Entering directory `/usr/src/linux-headers-2.6.31-14-generic'
> >   CC [M]  /home/tvbox/v4l-dvb/v4l/saa7134-input.o
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c: In function 'build_key':
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: 'ir_codes' undeclared (first use in this function)
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: (Each undeclared identifier is reported only once
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: for each function it appears in.)
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: 'ir_codes_videomate_s350' undeclared (first use in this function)
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c:91: error: 'mask_keycode' undeclared (first use in this function)
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c:92: error: 'mask_keydown' undeclared (first use in this function)
> > make[3]: *** [/home/tvbox/v4l-dvb/v4l/saa7134-input.o] Error 1
> > make[2]: *** [_module_/home/tvbox/v4l-dvb/v4l] Error 2
> > make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic'
> > make[1]: *** [default] Error 2
> > make[1]: Leaving directory `/home/tvbox/v4l-dvb/v4l'
> > make: *** [all] Error 2
> > 
> > background:
> > Justbought last week a new compro videomate s350 (dvb-s) card after seeing
> > some positive feedback on forumes saying it is working.  But the card I
> > got has a newer chip set incorporating a saa7135 device and after some
> > searching found someone else also had the same issue back in June but
> > managed to fix it with a few changes.  I trying to re-produce the
> > actions (see link below) and re-build the drivers but I'm stuck at the
> > compile stage (make all). 
> > 
> > http://osdir.com/ml/linux-media/2009-06/msg01256.html
> > 
> > Can someone advise me on how get past the make error?
> > 
> > Thanks,
> > Dominic
> > 
> 
> hm, likely you are on some older/other stuff.
> 
> Igor had some merge conflict previously for the S350.
> 
> Can't see it with current linuxtv.org mercurial v4l-dvb.
> 
> Please try with that.
> 
> Cheers,
> Hermann

Re: Compile error saa7134 - compro videomate S350

[Dominic Fernandes]

Hi Hermann,

Thanks for your reply.  I'm a little lost in what to do next.

How do I force the card to be recongised as card 169 (the compro videomate S350) instead of card 139?

Thanks,
Dominic





----- Original Message ----
From: hermann pitton <hermann-pitton@arcor.de>
To: Dominic Fernandes <dalf198@yahoo.com>
Cc: linux-media@vger.kernel.org
Sent: Wed, November 25, 2009 12:08:18 AM
Subject: Re: Compile error saa7134 - compro videomate S350

Hi Dominic,

Am Dienstag, den 24.11.2009, 10:01 -0800 schrieb Dominic Fernandes:
> Hi Hermann,
> 
> Thanks for responding. I managed to do the compile and install this time without errors on a fresh copy of the v4l-dvb drivers.

Good. On a short look.

> However, from the thread (link) it said  Changing the PCI Vendor
> ID to 0x7133 in the S350 patch, - which file and location would specify this?

That won't work, since the T750 has already the same PCI subsystem with
some saa7133. (can be saa7133, 7135 or saa7131e, no way to detect)

Also Jan declared for sure to have a saa7130. Detection is correct so
far, but now we must either kick out the T750 or try with some eeprom
detection. Known problem for Compro, we try to guess on tuner types
then, but I don't like it much and they should care themselves or
provide the eeprom tables for card types..

> At the moment the dvb-s card is recognised as the compro T750 card (I made the other mod of changing the gpio to xc000 in saa7134-cards):

Can't tell much without any such device, but if OK, to force card=169
should work then for you with that change?

In that case, we still would create a new card entry for your saa7135
device.

Cheers,
Hermann

>    6.008121] saa7130/34: v4l2 driver version 0.2.15 loaded
> [    6.008173] saa7134 0000:03:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> [    6.008180] saa7133[0]: found at 0000:03:01.0, rev: 209, irq: 17, latency: 64, mmio: 0xcfcff000
> [    6.008186] saa7133[0]: subsystem: 185b:c900, board: Compro VideoMate T750 [card=139,autodetected]
> [    6.008200] saa7133[0]: board init: gpio is 843f00
> [    6.008205] IRQ 17/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
> [    6.160030] saa7133[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
> [    6.160052] saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff
> [    6.160071] saa7133[0]: i2c eeprom 20: 01 40 01 02 02 01 03 01 08 ff 00 87 ff ff ff ff
> [    6.160091] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160109] saa7133[0]: i2c eeprom 40: ff d6 00 c0 86 1c 02 01 02 ff ff ff ff ff ff ff
> [    6.160133] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb
> [    6.160144] saa7133[0]: i2c eeprom 60: 35 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160156] saa7133[0]: i2c eeprom 70: 00 00 00 01 4e c1 ff ff ff ff ff ff ff ff ff ff
> [    6.160167] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160178] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160190] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160201] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160212] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160223] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160235] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.160246] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    6.313949] saa7133[0]: registered device video0 [v4l2]
> [    6.313978] saa7133[0]: registered device vbi0
> [    6.314003] saa7133[0]: registered device radio0
> 
> thanks,
> Dominic
> 
> 
> 
> 
> 
> ----- Original Message ----
> From: hermann pitton <hermann-pitton@arcor.de>
> To: Dominic Fernandes <dalf198@yahoo.com>
> Cc: linux-media@vger.kernel.org
> Sent: Tue, November 24, 2009 1:12:54 AM
> Subject: Re: Compile error saa7134 - compro videomate S350
> 
> Hi Dominic,
> 
> Am Montag, den 23.11.2009, 10:01 -0800 schrieb Dominic Fernandes:
> > Hi,
> > 
> > I need help to compile v4l-dvb drivers for saa7134 modules. 
> > I'm new to v4l-dvb not sure how to get past the errors concerning
> > undefined declarations found in saa7134-inputs.c file for the videomate
> > S350 board, saying ir_codes, mask_keycodes, mask_keydown as undeclared:
> > 
> > snip:-
> > 
> > make[2]: Entering directory `/usr/src/linux-headers-2.6.31-14-generic'
> >   CC [M]  /home/tvbox/v4l-dvb/v4l/saa7134-input.o
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c: In function 'build_key':
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: 'ir_codes' undeclared (first use in this function)
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: (Each undeclared identifier is reported only once
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: for each function it appears in.)
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c:90: error: 'ir_codes_videomate_s350' undeclared (first use in this function)
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c:91: error: 'mask_keycode' undeclared (first use in this function)
> > /home/tvbox/v4l-dvb/v4l/saa7134-input.c:92: error: 'mask_keydown' undeclared (first use in this function)
> > make[3]: *** [/home/tvbox/v4l-dvb/v4l/saa7134-input.o] Error 1
> > make[2]: *** [_module_/home/tvbox/v4l-dvb/v4l] Error 2
> > make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic'
> > make[1]: *** [default] Error 2
> > make[1]: Leaving directory `/home/tvbox/v4l-dvb/v4l'
> > make: *** [all] Error 2
> > 
> > background:
> > Justbought last week a new compro videomate s350 (dvb-s) card after seeing
> > some positive feedback on forumes saying it is working.  But the card I
> > got has a newer chip set incorporating a saa7135 device and after some
> > searching found someone else also had the same issue back in June but
> > managed to fix it with a few changes.  I trying to re-produce the
> > actions (see link below) and re-build the drivers but I'm stuck at the
> > compile stage (make all). 
> > 
> > http://osdir.com/ml/linux-media/2009-06/msg01256.html
> > 
> > Can someone advise me on how get past the make error?
> > 
> > Thanks,
> > Dominic
> > 
> 
> hm, likely you are on some older/other stuff.
> 
> Igor had some merge conflict previously for the S350.
> 
> Can't see it with current linuxtv.org mercurial v4l-dvb.
> 
> Please try with that.
> 
> Cheers,
> Hermann


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html



      

Re: Compile error saa7134 - compro videomate S350

[hermann pitton]

Hi Dominic,

Am Mittwoch, den 25.11.2009, 08:31 -0800 schrieb Dominic Fernandes:
> Hi Hermann,
> 
> Thanks for your reply.  I'm a little lost in what to do next.
> 
> How do I force the card to be recongised as card 169 (the compro videomate S350) instead of card 139?

unload the driver with "modprobe -vr saa7134-alsa saa7134-dvb".

You might have to close mixers using saa7134-alsa previously.
With "modinfo saa7134" you get available options.

With "modprobe -v saa7134 card=169" you can force that card then.

If we disable the T750 auto detection in saa7134-cards.c, both have to
force the correct card number.

Cheers,
Hermann

Re: Compile error saa7134 - compro videomate S350

[Dominic Fernandes]

Hi Hermann,

> unload the driver with "modprobe -vr saa7134-alsa saa7134-dvb".

When I tried this I got the message "FATAL: saa7134-alsa is in use" (or something like that).

>You might have to close mixers using saa7134-alsa previously.
> With "modinfo saa7134" you get available options.

I wasn't sure what to look for here, there was a lot of info. being displayed.

I carried on with "modprobe -v saa7134 card=169" command.  I ran dmesg to see the status of the card.  It did get the card id 169 but the board decription came up as unknown instead of the name of the videomate S350.  Is this expected?

The modification of the GPIO address "Instead of 0x8000 used in Jan's patch, use 0xC000 for GPIO setup" I'm not sure what I changed was the correct value.  Looking at the code lines I found relate to the Remote that I had changed (saa7134-cards.c):


+	case SAA7134_BOARD_VIDEOMATE_S350:
+		dev->has_remote = SAA7134_REMOTE_GPIO;
+		saa_andorl(SAA7134_GPIO_GPMODE0 >> 2,   0x00008000, 0x00008000);
+		saa_andorl(SAA7134_GPIO_GPSTATUS0 >> 2, 0x00008000, 0x00008000);
+		break;

Which leads to the question where the GPIO address of 0x8000 is currently specified?


Thanks,
Dominic




----- Original Message ----
From: hermann pitton <hermann-pitton@arcor.de>
To: Dominic Fernandes <dalf198@yahoo.com>
Cc: linux-media@vger.kernel.org
Sent: Wed, November 25, 2009 6:14:27 PM
Subject: Re: Compile error saa7134 - compro videomate S350

Hi Dominic,

Am Mittwoch, den 25.11.2009, 08:31 -0800 schrieb Dominic Fernandes:
> Hi Hermann,
> 
> Thanks for your reply.  I'm a little lost in what to do next.
> 
> How do I force the card to be recongised as card 169 (the compro videomate S350) instead of card 139?

unload the driver with "modprobe -vr saa7134-alsa saa7134-dvb".

You might have to close mixers using saa7134-alsa previously.
With "modinfo saa7134" you get available options.

With "modprobe -v saa7134 card=169" you can force that card then.

If we disable the T750 auto detection in saa7134-cards.c, both have to
force the correct card number.

Cheers,
Hermann


      

Re: Compile error saa7134 - compro videomate S350

[hermann pitton]

Hi,

Am Freitag, den 27.11.2009, 02:12 -0800 schrieb Dominic Fernandes:
> Hi Hermann,
> 
> > unload the driver with "modprobe -vr saa7134-alsa saa7134-dvb".
> 
> When I tried this I got the message "FATAL: saa7134-alsa is in use" (or something like that).

that are mixers and such using saa7134-alsa. They prevent you from
unloading saa7134 too. With "options saa7134 alsa=0" the alsa device is
not created.

> >You might have to close mixers using saa7134-alsa previously.
> > With "modinfo saa7134" you get available options.
> 
> I wasn't sure what to look for here, there was a lot of info. being displayed.

I just tried to tell that you can force a card=number.

> I carried on with "modprobe -v saa7134 card=169" command.  I ran dmesg to see the status of the card.  It did get the card id 169 but the board decription came up as unknown instead of the name of the videomate S350.  Is this expected?

No, "modprobe -v saa7134" should show if something in etc/modules.d
or /etc/modprobe.conf overrides your card=169 command line.

If I force a card=96 to card=169 it looks like that.

saa7130/34: v4l2 driver version 0.2.15 loaded
saa7133[0]: setting pci latency timer to 64
saa7133[0]: found at 0000:04:01.0, rev: 209, irq: 22, latency: 64, mmio: 0xfebff800
saa7133[0]: subsystem: 16be:0008, board: Compro VideoMate S350/S300 [card=169,insmod option]
saa7133[0]: board init: gpio is 0
saa7133[0]: gpio: mode=0x0008000 in=0x0000000 out=0x0008000 [pre-init]
input: saa7134 IR (Compro VideoMate S3 as /class/input/input6
IRQ 22/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[0]: i2c eeprom 00: be 16 08 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff 00 01 50 32 79 01 3c ca 50
saa7133[0]: i2c eeprom 20: 01 40 01 02 02 03 01 0f 0f ff 00 3c 02 51 96 2b
saa7133[0]: i2c eeprom 30: a7 58 7a 1f 03 8e 84 5e da 7a 04 b3 05 87 b2 3c
saa7133[0]: i2c eeprom 40: ff 28 00 c0 96 10 03 01 c0 1c fd 79 44 9f c2 8f
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
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[1]: setting pci latency timer to 64
saa7133[1]: found at 0000:04:02.0, rev: 209, irq: 20, latency: 64, mmio: 0xfebff000
saa7133[1]: subsystem: 16be:0007, board: Medion Md8800 Quadro [card=96,autodetected]
saa7133[1]: board init: gpio is 0
saa7133[1]: gpio: mode=0x0000000 in=0x0000000 out=0x0000000 [pre-init]
IRQ 20/saa7133[1]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[1]: i2c eeprom 00: be 16 07 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[1]: i2c eeprom 10: 00 ff 86 0f ff 20 ff 00 01 50 32 79 01 3c ca 50
saa7133[1]: i2c eeprom 20: 01 40 01 02 02 03 01 00 06 ff 00 23 02 51 96 2b
saa7133[1]: i2c eeprom 30: a7 58 7a 1f 03 8e 84 5e da 7a 04 b3 05 87 b2 3c
saa7133[1]: i2c eeprom 40: ff 28 00 c0 96 10 03 00 c0 1c fd 79 44 9f c2 8f

Note, saa7134 gpio_tracking=1 is enabled.
saa7133[0]: gpio: mode=0x0008000 in=0x0000000 out=0x0008000 [pre-init]

Means gpio 15 is set to 1, output.


> The modification of the GPIO address "Instead of 0x8000 used in Jan's patch, use 0xC000 for GPIO setup" I'm not sure what I changed was the correct value.  Looking at the code lines I found relate to the Remote that I had changed (saa7134-cards.c):
> 
> 
> +	case SAA7134_BOARD_VIDEOMATE_S350:
> +		dev->has_remote = SAA7134_REMOTE_GPIO;
> +		saa_andorl(SAA7134_GPIO_GPMODE0 >> 2,   0x00008000, 0x00008000);
> +		saa_andorl(SAA7134_GPIO_GPSTATUS0 >> 2, 0x00008000, 0x00008000);
> +		break;
> 
> Which leads to the question where the GPIO address of 0x8000 is currently specified?

This is exactly caused by and only by the above, likely powering up some
chip.

If you change all to 0x0000c000, gpio 14 and 15 are set to 1, output.

Don't know what exactly is going on with your card variant, but such are
the reports.

Cheers,
Hermann

Re: Compile error saa7134 - compro videomate S350

[Dominic Fernandes]

hi,

where does  "options saa7134 alsa=0" need to be declared?  Is it in /etc/modprobe.d/options.conf ?  If so, it didn't work - "FATAL: saa7134-alsa is in use"

thanks,
Dominic



----- Original Message ----
From: hermann pitton <hermann-pitton@arcor.de>
To: Dominic Fernandes <dalf198@yahoo.com>
Cc: linux-media@vger.kernel.org
Sent: Fri, November 27, 2009 10:14:10 PM
Subject: Re: Compile error saa7134 - compro videomate S350

Hi,

Am Freitag, den 27.11.2009, 02:12 -0800 schrieb Dominic Fernandes:
> Hi Hermann,
> 
> > unload the driver with "modprobe -vr saa7134-alsa saa7134-dvb".
> 
> When I tried this I got the message "FATAL: saa7134-alsa is in use" (or something like that).

that are mixers and such using saa7134-alsa. They prevent you from
unloading saa7134 too. With "options saa7134 alsa=0" the alsa device is
not created.

> >You might have to close mixers using saa7134-alsa previously.
> > With "modinfo saa7134" you get available options.
> 
> I wasn't sure what to look for here, there was a lot of info. being displayed.

I just tried to tell that you can force a card=number.

> I carried on with "modprobe -v saa7134 card=169" command.  I ran dmesg to see the status of the card.  It did get the card id 169 but the board decription came up as unknown instead of the name of the videomate S350.  Is this expected?

No, "modprobe -v saa7134" should show if something in etc/modules.d
or /etc/modprobe.conf overrides your card=169 command line.

If I force a card=96 to card=169 it looks like that.

saa7130/34: v4l2 driver version 0.2.15 loaded
saa7133[0]: setting pci latency timer to 64
saa7133[0]: found at 0000:04:01.0, rev: 209, irq: 22, latency: 64, mmio: 0xfebff800
saa7133[0]: subsystem: 16be:0008, board: Compro VideoMate S350/S300 [card=169,insmod option]
saa7133[0]: board init: gpio is 0
saa7133[0]: gpio: mode=0x0008000 in=0x0000000 out=0x0008000 [pre-init]
input: saa7134 IR (Compro VideoMate S3 as /class/input/input6
IRQ 22/saa7133[0]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[0]: i2c eeprom 00: be 16 08 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff 00 01 50 32 79 01 3c ca 50
saa7133[0]: i2c eeprom 20: 01 40 01 02 02 03 01 0f 0f ff 00 3c 02 51 96 2b
saa7133[0]: i2c eeprom 30: a7 58 7a 1f 03 8e 84 5e da 7a 04 b3 05 87 b2 3c
saa7133[0]: i2c eeprom 40: ff 28 00 c0 96 10 03 01 c0 1c fd 79 44 9f c2 8f
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
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[1]: setting pci latency timer to 64
saa7133[1]: found at 0000:04:02.0, rev: 209, irq: 20, latency: 64, mmio: 0xfebff000
saa7133[1]: subsystem: 16be:0007, board: Medion Md8800 Quadro [card=96,autodetected]
saa7133[1]: board init: gpio is 0
saa7133[1]: gpio: mode=0x0000000 in=0x0000000 out=0x0000000 [pre-init]
IRQ 20/saa7133[1]: IRQF_DISABLED is not guaranteed on shared IRQs
saa7133[1]: i2c eeprom 00: be 16 07 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[1]: i2c eeprom 10: 00 ff 86 0f ff 20 ff 00 01 50 32 79 01 3c ca 50
saa7133[1]: i2c eeprom 20: 01 40 01 02 02 03 01 00 06 ff 00 23 02 51 96 2b
saa7133[1]: i2c eeprom 30: a7 58 7a 1f 03 8e 84 5e da 7a 04 b3 05 87 b2 3c
saa7133[1]: i2c eeprom 40: ff 28 00 c0 96 10 03 00 c0 1c fd 79 44 9f c2 8f

Note, saa7134 gpio_tracking=1 is enabled.
saa7133[0]: gpio: mode=0x0008000 in=0x0000000 out=0x0008000 [pre-init]

Means gpio 15 is set to 1, output.


> The modification of the GPIO address "Instead of 0x8000 used in Jan's patch, use 0xC000 for GPIO setup" I'm not sure what I changed was the correct value.  Looking at the code lines I found relate to the Remote that I had changed (saa7134-cards.c):
> 
> 
> +    case SAA7134_BOARD_VIDEOMATE_S350:
> +        dev->has_remote = SAA7134_REMOTE_GPIO;
> +        saa_andorl(SAA7134_GPIO_GPMODE0 >> 2,   0x00008000, 0x00008000);
> +        saa_andorl(SAA7134_GPIO_GPSTATUS0 >> 2, 0x00008000, 0x00008000);
> +        break;
> 
> Which leads to the question where the GPIO address of 0x8000 is currently specified?

This is exactly caused by and only by the above, likely powering up some
chip.

If you change all to 0x0000c000, gpio 14 and 15 are set to 1, output.

Don't know what exactly is going on with your card variant, but such are
the reports.

Cheers,
Hermann


      

Re: Compile error saa7134 - compro videomate S350

[hermann pitton]

Hi Dominic,

Am Freitag, den 27.11.2009, 14:59 -0800 schrieb Dominic Fernandes:
> hi,
> 
> where does  "options saa7134 alsa=0" need to be declared?  Is it in /etc/modprobe.d/options.conf ?  If so, it didn't work - "FATAL: saa7134-alsa is in use"

yes, you can only unload saa7134-alsa after you close all apps using it.

It is very distribution depending and I'm not aware of all, where to put
options.

If it doesn't work for options.conf, it should still work with a
recently deprecated declared /etc/modprobe.conf file you have to create
as a work around for all distros.

You must issue a "depmod -a" after that and reboot, if you don't know
how to unload saa7134-alsa by closing all apps using it.

A "modprobe -vr saa7134-alsa saa7134-dvb" and then load it with
"modprobe -v saa7134 card=169 gpio_tracking=1" should still reveal
something configured in the system overriding your command line with
card=169.

I'm not on latest here ...

Cheers,
Hermann

Re: Compile error saa7134 - compro videomate S350

[Dominic Fernandes]

Hi Hermann,

I'm getting closer!!! 

I'm using ubuntu 9.10, unloading saa7134 alsa wasn't working for me so I put it into the blacklist which prevented it from loading and then I was able to do the "modprobe -vr saa7134-alsa saa7134-dvb" and "modprobe -v saa7134 card=16". 

And now the card recongnised correctly as the S350 and the dvb frontend loads.  

So, now I've plugged in the cable to the SAT dish which is pointing to Astra 19.2 and want to tune into some channels.
I installed dvb-apps and use the command below to create a channels.conf to use later:-

scan -x0 /usr/share/dvb/dvb-s/Astra-19.2E | tee channels.conf

but this soon concludes with tunning finished with no channels found.  I get a warning >>> tuning failed.

So, I tried both the modification of the GPIO address of xc0000 and what it 
was originally x8000 which gave the same tuning failed message.

Are there some other commands to test the DVB Frontend?

Thanks,
Dominic









----- Original Message ----
From: hermann pitton <hermann-pitton@arcor.de>
To: Dominic Fernandes <dalf198@yahoo.com>
Cc: linux-media@vger.kernel.org
Sent: Fri, November 27, 2009 11:14:47 PM
Subject: Re: Compile error saa7134 - compro videomate S350

Hi Dominic,

Am Freitag, den 27.11.2009, 14:59 -0800 schrieb Dominic Fernandes:
> hi,
> 
> where does  "options saa7134 alsa=0" need to be declared?  Is it in /etc/modprobe.d/options.conf ?  If so, it didn't work - "FATAL: saa7134-alsa is in use"

yes, you can only unload saa7134-alsa after you close all apps using it.

It is very distribution depending and I'm not aware of all, where to put
options.

If it doesn't work for options.conf, it should still work with a
recently deprecated declared /etc/modprobe.conf file you have to create
as a work around for all distros.

You must issue a "depmod -a" after that and reboot, if you don't know
how to unload saa7134-alsa by closing all apps using it.

A "modprobe -vr saa7134-alsa saa7134-dvb" and then load it with
"modprobe -v saa7134 card=169 gpio_tracking=1" should still reveal
something configured in the system overriding your command line with
card=169.

I'm not on latest here ...

Cheers,
Hermann


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html



      

Re: Compile error saa7134 - compro videomate S350

[hermann pitton]

Hi Dominic,

Am Samstag, den 28.11.2009, 17:30 -0800 schrieb Dominic Fernandes: 
> Hi Hermann,
> 
> I'm getting closer!!! 
> 
> I'm using ubuntu 9.10, unloading saa7134 alsa wasn't working for me so I put it into the blacklist which prevented it from loading and then I was able to do the "modprobe -vr saa7134-alsa saa7134-dvb" and "modprobe -v saa7134 card=16". 
> 
> And now the card recongnised correctly as the S350 and the dvb frontend loads.  
> 
> So, now I've plugged in the cable to the SAT dish which is pointing to Astra 19.2 and want to tune into some channels.
> I installed dvb-apps and use the command below to create a channels.conf to use later:-
> 
> scan -x0 /usr/share/dvb/dvb-s/Astra-19.2E | tee channels.conf
> 
> but this soon concludes with tunning finished with no channels found.  I get a warning >>> tuning failed.
> 
> So, I tried both the modification of the GPIO address of xc0000 and what it 
> was originally x8000 which gave the same tuning failed message.
> 
> Are there some other commands to test the DVB Frontend?

if Astra-19.2E is unchanged in dvb-apps, it has not much.

# Astra 19.2E SDT info service transponder
# freq pol sr fec
S 12551500 V 22000000 5/6

We don't even know if 13 and 18 Volts to the LNB work both for sure with
that variant, IIRC. The report says just somehow works.

I think I would try with some peace of copper from a LNB cable into the
RF connector and a Voltmeter, if there is any sign of life first, either
using kaffeine with better files for scanning or the "setvoltage" tool
in /test.

You might want to set dvb_powerdown_on_sleep=0 for dvb_core.

For the other saa7134 driver cards currently is hacked on,

For Dominic with the Leadtek on the saa7134 driver, Terry, me or anyone
else interested should provide some test patches.

Why that AverMedia analog only in the Ukraine doesn't have sound even on
PAL around there, is beyond my imagination, except it would not have
ever been tested for TV sound, also beyond what I can imagine.

Any log for obviously failing sound carrier detection is still missing.

Cheers,
Hermann

Re: Compile error saa7134 - compro videomate S350

[Dominic Fernandes]

Hi Hermann,

There is a sign of life coming from the card (I connected my SAT finder and got a loud tone from it).

> You might want to set dvb_powerdown_on_sleep=0 for dvb_core.

How do you specify this and which file (saa7134-dvb.c or saa7134-core.c or some other file)?

I tried Kaffeine, to scan Astra 19.2 but no luck, at first I can see the signal meters light up and then stop.  The output from dmesg at this point shows:
 
[   72.944834] DVB: registering adapter 0 frontend 0 (Zarlink ZL10313 DVB-S)...
[ 2183.208025] DVB: adapter 0 frontend 0 frequency 7401500 out of range (950000..2150000)
[ 2191.756534] DVB: adapter 0 frontend 0 frequency 7401500 out of range (950000..2150000)
[ 2195.908528] DVB: adapter 0 frontend 0 frequency 7401500 out of range (950000..2150000)


Not sure what this means.

Thanks,
Dominic





----- Original Message ----
From: hermann pitton <hermann-pitton@arcor.de>
To: Dominic Fernandes <dalf198@yahoo.com>
Cc: linux-media@vger.kernel.org
Sent: Mon, November 30, 2009 1:29:25 AM
Subject: Re: Compile error saa7134 - compro videomate S350

Hi Dominic,

Am Samstag, den 28.11.2009, 17:30 -0800 schrieb Dominic Fernandes: 
> Hi Hermann,
> 
> I'm getting closer!!! 
> 
> I'm using ubuntu 9.10, unloading saa7134 alsa wasn't working for me so I put it into the blacklist which prevented it from loading and then I was able to do the "modprobe -vr saa7134-alsa saa7134-dvb" and "modprobe -v saa7134 card=16". 
> 
> And now the card recongnised correctly as the S350 and the dvb frontend loads.  
> 
> So, now I've plugged in the cable to the SAT dish which is pointing to Astra 19.2 and want to tune into some channels.
> I installed dvb-apps and use the command below to create a channels.conf to use later:-
> 
> scan -x0 /usr/share/dvb/dvb-s/Astra-19.2E | tee channels.conf
> 
> but this soon concludes with tunning finished with no channels found.  I get a warning >>> tuning failed.
> 
> So, I tried both the modification of the GPIO address of xc0000 and what it 
> was originally x8000 which gave the same tuning failed message.
> 
> Are there some other commands to test the DVB Frontend?

if Astra-19.2E is unchanged in dvb-apps, it has not much.

# Astra 19.2E SDT info service transponder
# freq pol sr fec
S 12551500 V 22000000 5/6

We don't even know if 13 and 18 Volts to the LNB work both for sure with
that variant, IIRC. The report says just somehow works.

I think I would try with some peace of copper from a LNB cable into the
RF connector and a Voltmeter, if there is any sign of life first, either
using kaffeine with better files for scanning or the "setvoltage" tool
in /test.

You might want to set dvb_powerdown_on_sleep=0 for dvb_core.

For the other saa7134 driver cards currently is hacked on,

For Dominic with the Leadtek on the saa7134 driver, Terry, me or anyone
else interested should provide some test patches.

Why that AverMedia analog only in the Ukraine doesn't have sound even on
PAL around there, is beyond my imagination, except it would not have
ever been tested for TV sound, also beyond what I can imagine.

Any log for obviously failing sound carrier detection is still missing.

Cheers,
Hermann


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html



      

Re: Compile error saa7134 - compro videomate S350

[hermann pitton]

Hi,

Am Montag, den 30.11.2009, 14:35 -0800 schrieb Dominic Fernandes:
> Hi Hermann,
> 
> There is a sign of life coming from the card (I connected my SAT finder and got a loud tone from it).
> 
> > You might want to set dvb_powerdown_on_sleep=0 for dvb_core.
> 
> How do you specify this and which file (saa7134-dvb.c or saa7134-core.c or some other file)?

as said above, you set it for dvb_core.

> I tried Kaffeine, to scan Astra 19.2 but no luck, at first I can see the signal meters light up and then stop.  The output from dmesg at this point shows:
>  
> [   72.944834] DVB: registering adapter 0 frontend 0 (Zarlink ZL10313 DVB-S)...
> [ 2183.208025] DVB: adapter 0 frontend 0 frequency 7401500 out of range (950000..2150000)
> [ 2191.756534] DVB: adapter 0 frontend 0 frequency 7401500 out of range (950000..2150000)
> [ 2195.908528] DVB: adapter 0 frontend 0 frequency 7401500 out of range (950000..2150000)
> 
> 
> Not sure what this means.

Nothing good at all. Likely there is some breakage in the maths across devices/modules,
often caused by different xtals/oscillators not sufficiently covered
yet.

For sure enough to get you out of the game for now.

If Richard's card still works with latest v4l-dvb and his patch, likely
you have slightly different hardware covered by the same driver too,
including to hit a freq calculation bug exclusively.

Can't tell from your input. The eeproms of yours and Richard's card
differ in byte 0x74 and 0x75. Don't know what that means.

Cheers,
Hermann