[linux-dvb]%09Mantis%09VP-1027/VP-1033/VP-1034/VP-2033/VP-3033&In-Reply-To=op.tjqztsra8ok45w@imac

Manu Abraham abraham.manu at gmail.com
Sun Dec 3 04:45:25 CET 2006


Elmar Schmidt wrote:
> Hi Manu,
> I've just send you an E-Mail, but for the Rest of the Mailing List, here
> is it again with Log Outputs.
> 
>> IIRC, you have a (MB86A16) VP-1034 ?
>> can you check out whether the changes in the mantis tree fixes your
>> issues ?
> 
> Is the cu1216 an another Chip? If its so, I'm sorry. I think that the
> cu1216 only includes a few Things for the Mantis Module. So I have to
> change the mb86a16.c for the Timer Fix, right?

Hmm.. The CU 1216 is a DVB-C tuner, whereas the MB86A16 is a DVB-S/DSS
DC receiver


> I've tried the new Driver from you, but with this my dvbscan can't find
> any Channels. I have added the mantis_dma.c Patch from Marko Ristola and
> now he scans. Dvbscan finds more Channels then before, but there is
> another Problem: After 3 or 4 Transponder-scans with kaffeine, the
> Module shuts down or so and I get an *NO SIGNAL* Error in dmesg. Tuning
> doesn't work.

It could be that NO SIGNAL for the relevant frequency what scan is
requesting to tune to.
I didn't follow what you meant by module shuts down.

I think all you need is a proper initial frequency list. If your
frequency list has invalid frequencies, you will see NO SIGNAL 's in the
logs. :-)

> If i try to reload the Module, then the Error is still there and I only
> can start a new Scan after a completely reboot (not Linux like - but I
> don't know wheres the Problem).


I don't understand the problem. I can rmmod mb86a16 and do a modprobe
mb86a16 without any tuning issues.


> @@ -231,7 +232,7 @@ void mantis_dma_xfer(unsigned long data)
>          dprintk(verbose, MANTIS_DEBUG, 1, "last block=[%d] finished 
> block=[%d]",
>              mantis->last_block, mantis->finished_block);
>  
> -        (mantis->ts_size ? dvb_dmx_swfilter_204: dvb_dmx_swfilter)
> +        (mantis->ts_size ? dvb_dmx_swfilter: dvb_dmx_swfilter_204)
>          (&mantis->demux, &mantis->buf_cpu[mantis->last_block * 
> MANTIS_BLOCK_BYTES], MANTIS_BLOCK_BYTES);
>          mantis->last_block = (mantis->last_block + 1) %
> MANTIS_BLOCK_COUNT;
>      }
> --------------------------------------------------------------------------------
> 


You wouldn't need this change, it is asking the DMA to use the software
filter for a 188 byte stream whereas you have a 204 byte long stream.
Wouldn't hurt much , except that you will get a garbled stream.


> 
> And mb86a16.c
> --------------------------------------------------------------------------------
> static int cu1216_get_tune_settings(struct dvb_frontend* fe, struct
> dvb_frontend_tune_settings* settings)
> {
>      settings->min_delay_ms = 50;
>      settings->step_size = 0; /* FE_QAM: zero */
>      settings->max_drift = 0; /* FE_QAM: zero */
>      return 0;
> }

You wouldn't need this change for the MB86A16, wouldn't help at all.

> ...
> ...
> dvb_frontend_ops...
> ...
> .get_tune_settings            = cu1216_get_tune_settings,
> ...
> --------------------------------------------------------------------------------
> 
> This damn Card drives me very crazy. I think about the Technotrend
> S2-3200, but there are also Alpha Drivers from you available, no
> officials. I don't know if they are better :(
> 

You need to have a bit of patience. :-)

I wouldn't want to recommend any hardware, whichever one it is. The
Mantis drivers that what you are using will be the official Linux
drivers from the vendor (Azurewave (a new fledgling company part of the
ASUS group), formerly known as Twinhan). :-)


Regards,
Manu



More information about the linux-dvb mailing list