Re: DiB3000MC rewritten and MT2060 is ready to go into main

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Matthieu,

On 30 Jul, matthieu castet wrote:
> Hi Klaus,
> 
> Klaus Frahm wrote:
>> On 30 Jul, matthieu castet wrote:
> 
>> 
>> 
>> I also see that the signal strength is reduced with the new driver, only
> Do you have a mt2060 ?

To be honest I am not sure. I have an AverTV A800 which certainly
depends on DiB3000MC. Furthermore with the new driver the module for
mt2060 is also automatically loaded when I plug in the usb-device. 
The command lsmod of the dvb-modules gives:

Module                  Size  Used by
dvb_usb_a800           23940  0 
dvb_usb_dibusb_common    26756  1 dvb_usb_a800
mt2060                 22148  1 dvb_usb_dibusb_common
dib3000mc              29444  1 dvb_usb_dibusb_common
dibx000_common         20868  1 dib3000mc
dvb_usb                39944  2 dvb_usb_a800,dvb_usb_dibusb_common
dvb_core              101168  1 dvb_usb
firmware_class         27904  1 dvb_usb
dvb_pll                32644  2 dvb_usb_dibusb_common,dvb_usb


> 
>> in my case I still have a good reception, on the contrary this may even have
>> participated to avoid another problem (described my other answer of this
>> thread). With the new driver the tzap commands gives me:
>> 
> 
>> tuning to 714167000 Hz
>> video pid 0x0078, audio pid 0x0082
>> status 03 | signal bb17 | snr 0000 | ber 001fffff | unc 0000ffff | 
>> status 1f | signal ba37 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
>> status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
>> status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
>> status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
>> 
>> and I think the signal "0000" is in reality 100% and I am convinced that my
>> reception is indeed 100% (an external amplified antenna) despite the fact 
>> that I use a T-peace in the antenna connection (which is normally not very good). 
> The old driver signal strenght is broken, you need to apply this patch 
> to get something usefull [1].

I have tested your patch (on the old driver in the linux kernel
2.6.18-rc3 and tzap now gives):

tuning to 714167000 Hz
video pid 0x0078, audio pid 0x0082
status 03 | signal 7135 | snr 0000 | ber 001fffff | unc 0000ffff | 
status 1f | signal 715a | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 7161 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 717d | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 71ac | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 7173 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 716c | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK

The TV reception works fine but with this patch I still have the problem
that I need a 2nd lock immediately after the 1st one, the problem which
is solved in the new driver. Maybe this is related to snr which is 0000
with the new driver. 

Greetings, Klaus.


_______________________________________________

linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[Index of Archives]     [Linux Media]     [Video 4 Linux]     [Asterisk]     [Samba]     [Xorg]     [Xfree86]     [Linux USB]

  Powered by Linux