[linux-dvb] Re: Nebula DigiTV and nxt6000 problems

[Robert Cook]

I performed the excersice of using tzap to tune between a non existant
frequency and a known station about 20 times in succession. There were
no lockups but I have to go with Florian's call on this one and say we
do nothing on the FE_RESET

The FE_READ_SNR ioctl reinstated, altered to suit the changed function
calls and replaced the register numbers with their definitions out of
nxt6000.h. The registers do no look correct. My guess is it should be
one of the SNR_? registers.

        case FE_READ_SNR:
                {
                        s16 *snr = (s16 *) arg;
                        *snr = nxt6000_readreg(fe, RS_COR_SYNC_PARAM) <<
8;
                        *snr |= nxt6000_readreg(fe, BER_CTRL);
                        break;
                }

Same with the FE_READ_SIGNAL_STRENGTH ioctl. There is no definition for
register 0x16 in nxt6000.h. Are we accessing the correct register here?

        case FE_READ_SIGNAL_STRENGTH:
                {
                        s16 *signal = (s16 *) arg;
                        *signal = (((signed char)nxt6000_readreg(fe,
0x16)) + 128) << 8;
                        return 0;

                }

Any idea on what registers will give us the FE_READ_BER and
FE_READ_UNCORRECTED_BLOCKS values just to complete the driver?

Robert



-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Florian Schirmer
Sent: Friday, 30 January 2004 9:39 PM
To: [EMAIL PROTECTED]
Subject: [linux-dvb] Re: Nebula DigiTV and nxt6000 problems


Hi,

> Changing the code to:
>
>         case FE_INIT:
>                 nxt6000_reset(fe);
>                 nxt6000_setup(fe);
>                 break;
>
>         case FE_RESET:
>                 nxt6000_reset(fe);
>                 break;
>
> Still works for me. Is there any documentation regarding this board? I

> would like to have a crack at getting the FE_READ_BER, 
> FE_READ_SIGNAL_STRENGTH, FE_READ_SNR and FE_READ_UNCORRECTED_BLOCKS 
> ioctls running. I know the board can do this as the manufacturers 
> Windows software displays these values.

The code should be already there. I just commented it out.

I don't recommend to actually do anything during FE_RESET. I had serious

trouble with that. At the time were i wrote that piece of code the bttv
i2c 
tended to easily lockup if the i2c bus was too busy. So i avoided i2c
traffic 
as much as possible.

Situation might have changed now with the switchover to hardware
controlled 
i2c. But i still recommand to not enable it by default. (Module param?)

Try to tune to a non existant frequency or station. FE_RESET will be
called 
very often. Wait a couple of seconds and then tune to a known good
station. 
Repeat say 3-5 times. If you dont encounter any lockups it might be
save.

Regards,
    Florian


-- 
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe
linux-dvb" as subject.



-- 
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as 
subject.