From: Sigmund Augdal <sigmund@snap.tv>
To: Arthur Konovalov <artlov@gmail.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] experimental support for C-1501
Date: Mon, 16 Jun 2008 14:40:50 +0200 [thread overview]
Message-ID: <1213620050.6543.6.camel@pascal> (raw)
In-Reply-To: <4855F6B0.8060507@gmail.com>
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
>
> Regards,
> AK
>
>
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-06-16 12:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 17:23 [linux-dvb] [PATCH] experimental support for C-1501 SG
2008-06-16 5:14 ` Arthur Konovalov
2008-06-16 12:40 ` Sigmund Augdal [this message]
[not found] ` <20080616142616.75F9C3BC99@waldorfmail.homeip.net>
2008-06-16 14:33 ` Sigmund Augdal
2008-06-16 17:42 ` SG
2008-06-16 18:07 ` SG
2008-06-16 18:20 ` SG
2008-06-17 13:13 ` Antti Palosaari
2008-06-16 18:54 ` Arthur Konovalov
2008-07-14 2:31 ` Simon Baxter
2008-07-14 16:56 ` Arthur Konovalov
2008-07-18 9:46 ` Simon Baxter
-- strict thread matches above, loose matches on Subject: below --
2008-06-04 13:14 Sigmund Augdal
2008-06-04 13:58 ` Antti Palosaari
2008-06-04 14:37 ` Sigmund Augdal
2008-06-05 9:10 ` Sigmund Augdal
2008-06-08 15:38 ` Oliver Endriss
2008-06-09 5:21 ` Arthur Konovalov
2008-06-09 10:00 ` Sigmund Augdal
2008-06-09 10:29 ` Arthur Konovalov
2008-06-14 20:07 ` Simon Baxter
2008-06-14 22:08 ` Arthur Konovalov
2008-06-17 18:51 ` Oliver Endriss
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=1213620050.6543.6.camel@pascal \
--to=sigmund@snap.tv \
--cc=artlov@gmail.com \
--cc=linux-dvb@linuxtv.org \
/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.