Johannes Stezenbach wrote:
IMHO:
MODCOD as it is defined in the spec is a field which
is part of the physical layer signalling. It is a lowlevel
encoding used to saved a bit in the PLHEADER, and
not what you should use in the tuning API.
Ok.
And we might provide MATYPE for informational purposes,
but decoding it is left to the application. You could
put the code to decode it into dvb-apps/lib/ somewhere.
Not yet reached there. Will do some utils as soon as it is finished.
Yeah, here I mixed up MATYPE (from BBHEADER) with MODCODE
(from PLSCODE). So assuming that the demo hw will give
you the MODCOD from PLSCODE in a register and you want
to query it via FE_GET_PARAMS, we should keep
decode_dvbs2_modcod() in dvb_frontend.
FE_GET_PARAMS will then return fec and modulation
instead of modcod.
Ok, ignore my just previous post.
We will need the SIS/MIS flag as well.
SIS/MIS (1 bit): describes whether there is a single input stream or
multiple input streams. If SIS/
MIS = multiple input stream, then the second byte is the input stream
identifier (ISI)
So we will need the Input Stream Identifier as well.
Manu
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
