Mailing List archive

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

[linux-dvb] Re: Diseqc and skystar2.



Il lun, 2003-12-01 alle 08:35, Holger Waechtler ha scritto:
> Vincenzo Di Massa wrote:
> > I was asked to try a go for full diseqc on the skystar2.
> > 
> > My question is: should I:
> > 
> > 1) Only add code to the actual driver, to let it send arbitrary bytes in
> > diseqc style?
> > 2) Remove everything from skystar2.c and place it in a different file
> > (diseqc_emulator.c ?) allowing other drivers too to register their
> > functions (tone on/off)?
> 
> Isn't the MT312 on the Skystar2 able to generate DiSEqC signals?

MT312 has the ability to send diseqc commands. But skystar2 does not use
it, it sends 22k (diseqc messages too) using the FC.
This is why I posted the tone burst patch: you can issue commands to
mt312 on the skystar2, but the chip is not wired to the antenna cable.

All this was told me by the author of the mt312 module (Andreas
Oberritter).
Read the following mail:
<Mail>
On Sat, 2003-11-08 at 04:56, Vincenzo Di Massa wrote:
> I have seen that skystar2.c driver uses its own routines to set up
> voltage and tone. Why doesn't it call mt312 routines? Should
skystar2.c
> manage tone burst in a custom way?

Yes. I wrote the driver for an mt312 evaluation board. That's why I
implemented the "unused" diseqc functions. The skystar card uses its
predecessor, the vp310, which is almost completely compatible. Up to
revision 2.3 of the card, diseqc and tone burst signals are generated by
the flexcop. Revision 2.6 and newer use the frontend for that, but they
don't have an mt312 compatible chip. They are based on the stv0299.
Unfortunately the only way to get information about how the flexcop
works is to disassemble binary drivers.

Regards,
Andreas
</Mail>


> 
> Holger
> 
-- 
Vincenzo Di Massa <hawk78_it@yahoo.it>



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.



Home | Main Index | Thread Index