Re: [PATCH] [RFC] dib8000: return an error if the TMCC is not locked

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

 



On Tuesday 17 January 2012 19:45:28 you wrote:
> On ISDB-T, a few carriers are reserved for TMCC decoding
> (1 to 20 carriers, depending on the mode). Those carriers
> use the DBPSK modulation, and contain the information about
> each of the three layers of carriers (modulation, partial
> reception, inner code, interleaving, and number of segments).
> 
> If the TMCC carrier was not locked and decoded, no information
> would be provided by get_frontend(). So, instead of returning
> false values, return -EAGAIN.
> 
> Another alternative for this patch would be to add a flag to
> fe_status (FE_HAS_GET_FRONTEND?), to indicate that the ISDB-T
> TMCC carriers (and DVB-T TPS?), required for get_frontend
> to work, are locked.
> 
> Comments?

I think it changes the behaviour of get_frontend too much and in fact 
transmission parameter signaling (TPS for DVB-T, TMCC for ISDB-T) locks 
are already or should be if not integrated to the status locks.

Also those parameters can change over time and signal a 
"reconfiguration" of the transmission.

So, for me I would vote against this kind of implementation in favor a 
better one. Unfortunately I don't have a much better idea at hand right 
now.

--
Patrick Boettcher

Kernel Labs Inc.
http://www.kernellabs.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux