On Mon, 16 Jun 2008 19:42:56 +0200
SG <SiestaGomez@xxxxxx> wrote:
> On Mon, 16 Jun 2008 16:33:52 +0200
> Sigmund Augdal <sigmund@xxxxxxx> wrote:
>
> > On Mon, 2008-06-16 at 16:26 +0200, siestagomez@xxxxxx wrote:
> > > Sigmund Augdal schrieb:
> > >
> > > > On Mon, 2008-06-16 at 08:14 +0300, Arthur Konovalov wrote:
> > > >> SG wrote:
> > > >> > The patch works quite well and nearly all channels seem to work.
> > > >> >
> > > >> > But when tuning to some radio channels I'll get this kernel message:
> > > >> >
> > > >> > saa7146 (0) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer
> > > >> >
> > > >> > Also I'm not able to tune to 'transponder 386000000 6900000 0 3' which works
> > > >> > smoothly when using Win32.
> > > >> >
> > > >> > initial transponder 386000000 6900000 0 3
> > > >> > >>> tune to: 386:M64:C:6900:
> > > >> > WARNING: >>> tuning failed!!!
> > > >> > >>> tune to: 386:M64:C:6900: (tuning failed)
> > > >> > WARNING: >>> tuning failed!!!
> > > >> > ERROR: initial tuning failed
> > > >> > dumping lists (0 services)
> > > >> > Done.
> > > >>
> > > >> Yes, I discovered too that tuning to frequency 386MHz has no lock.
> > > >> VDR channels.conf: TV3:386000:C0M64:C:6875:703:803:0:0:1003:16:1:0
> > > >>
> > > >> At same time, 394MHz (and others) works.
> > > > Hi.
> > > >
> > > > Both transponders reported to not tune here has different symbolrates
> > > > from what I used for my testing. Maybe this is relevant in some way.
> > > > Could you please compare this with the channels that did tune to see if
> > > > there is a pattern?
> > > >
> > > > About the i2c message, I get that every now and then here as well, but I
> > > > have not seen any ill effect from it. I also see that on some other TT
> > > > cards so I think that might be unrelated to the demod/tuner.
> > > >
> > > > Regards
> > > >
> > > > Sigmund Augdal
> > >
> > > The symbolrate is the same on all other working channels.
> > >
> > > Regarding the i2c message when watching video I'll get this only once but
> > > when tuning to a radio channel my log gets flooded and it seems to hangup.
> > How does radio or not make a difference? As far as I know the card is
> > DVB only and should not care whether the tuned transponder contains
> > radio or video or whatever. Could you send a list of transponders that
> > work (with tuning parameters) and ones that doesn't?
> >
>
> Odd today no problem with radio and kernel log.
> Anyway here are a few entries from transponder.ini which I use for dvbscan:
> C 362000000 6900000 NONE QAM64 OK
> C 370000000 6900000 NONE QAM64 OK
> C 378000000 6900000 NONE QAM64 OK
> C 386000000 6900000 NONE QAM64 NOT OK
> C 394000000 6900000 NONE QAM64 OK
> C 402000000 6900000 NONE QAM256 NOT OK
> C 410000000 6900000 NONE QAM64 OK
> C 426000000 6900000 NONE QAM64 OK
>
> I noticed when using Win32 the signal strenght is very poor on the non working transponders for linux-dvb.
> Perhaps it's enough for Win32 but not for the linux driver.
>
> Regards
> Martin
>
Hi
I just added a line to get the bundled IR-remote to work using lirc.
--- a/linux/drivers/media/dvb/ttpci/budget-ci.c 2008-06-16 19:58:04.000000000 +0200
+++ b/linux/drivers/media/dvb/ttpci/budget-ci.c 2008-06-08 17:19:39.000000000 +0200
@@ -237,6 +237,7 @@
break;
case 0x1010:
case 0x1017:
+ case 0x101a:
/* for the Technotrend 1500 bundled remote */
ir_input_init(input_dev, &budget_ci->ir.state,
IR_TYPE_RC5, ir_codes_tt_1500);
Regards
Martin
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
