Antti Palosaari wrote:
> >> I guess I need to check the tuner writes too.
> >
> >>From dvbsky:
> >
> > TUNER_write(10, [0a])
> > TUNER_write(11, [40])
> >
> > and from your driver:
> >
> > TUNER_write(10, [0b40])
> >
> > That would appear to be some sort of tuner frequency setting?
>
Antti Palosaari wrote:
> > But you don't give me the option of _not_ setting it. The dvbsky driver
> > sets it to 0x35 in its init_tab[] - as does yours - and then leaves it
> > alone.
>
> So what? Do you understand meaning of init tables?
Yes. You misunderstand what I'm saying. You uncondit
David Howells wrote:
> > I guess I need to check the tuner writes too.
>
> From dvbsky:
>
> TUNER_write(10, [0a])
> TUNER_write(11, [40])
>
> and from your driver:
>
> TUNER_write(10, [0b40])
>
> That would appear to be some sort of tuner frequency setting?
Setting it to 0
On 15.11.2013 15:56, David Howells wrote:
David Howells wrote:
I guess I need to check the tuner writes too.
From dvbsky:
TUNER_write(10, [0a])
TUNER_write(11, [40])
and from your driver:
TUNER_write(10, [0b40])
That would appear to be some sort of tuner frequen
David Howells wrote:
> I guess I need to check the tuner writes too.
>From dvbsky:
TUNER_write(10, [0a])
TUNER_write(11, [40])
and from your driver:
TUNER_write(10, [0b40])
That would appear to be some sort of tuner frequency setting?
David
--
To unsubscribe from thi
On 15.11.2013 15:32, David Howells wrote:
Antti Palosaari wrote:
demod_write(33, [00]) YES
That is config option already. Did you set value? If yes, then there is driver
bug. If not, then add value.
But you don't give me the option of _not_ setting it. The dvbsky
On Fri, Nov 15, 2013 at 8:32 AM, David Howells wrote:
> Whilst that may be so, something clears it between one call to
> m88ds3103_set_frontend() and the next, so you probably need to unconditionally
> reload the program init table.
Check your GPIO config for the specific board in the cx23885 dri
Antti Palosaari wrote:
> > demod_write(33, [00]) YES
>
> That is config option already. Did you set value? If yes, then there is driver
> bug. If not, then add value.
But you don't give me the option of _not_ setting it. The dvbsky driver sets
it to 0x35 in its in
On 15.11.2013 13:33, David Howells wrote:
I think I've isolated the significant part of the demod register setup.
Discarding the reads and sorting them in address order, I see
ANTTI DVBSKY DIFFER?
=== === ===
demod_wr
I think I've isolated the significant part of the demod register setup.
Discarding the reads and sorting them in address order, I see
ANTTI DVBSKY DIFFER?
=== === ===
demod_write(22, [ac]) demod_write(22, [ac]) no
David Howells wrote:
> Here are four logs from doing:
>
> scandvb -a1 ./e.1
>
> where the contents of file e.1 are:
>
> S 11919000 V 2750 3/4
>
> which is probing a region on the Eutelsat-9A satellite broadcast.
Here's a script for turning the logs from:
I2C cx23885[
Hello
You have to identify situation where it does not work, optimally single
known channel. Then switch to working driver and tune that same channel
and take sniffs. Then generate code from sniffs, copy paste that to
non-working driver until it starts working. Then it is quite trivial to
find
12 matches
Mail list logo
