aboutsummaryrefslogtreecommitdiffstats
path: root/util/scan/dvb-t/fi-Mantta
blob: 98a821ba57ea9f04b809445adccf32dc7a79c209 (plain)
1
2
3
4
5
# automatically generated from http://www.digitv.fi/sivu.asp?path=1;8224;9519
# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
T 658000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
T 722000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
T 594000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
class="c">\" Process this file with .\" groff -man -Tascii dhex.1 .\" .Dd January 28, 2011 .Os .Dt DHEX_SEARCHLOG 5 .Sh NAME .Nm dhex_searchlog .Nd search log file for dhex .Sh DESCRIPTION Searchlogs for .Xr dhex 1 are stored in searchlog files. This manpage describes the format of those files. .Ss EXAMPLE A typical searchlog file looks like this: .br .Ql #DHEX SEARCHLOG .br .Ql #VERSION 0 .br .Ql #Search was for d0 0f af fe .br .Ql #lines are all in hex .br .br .Ql 0000000000002385 .br .Ql 0000000000002e21 .br .Ql 0000000000006acb .br .Ql 0000000000006b8b .br .Ql 000000000000cd27 .br .Sh OPTIONS In the example above, the file has two sections: A comment section, and an offset section. .Ss Comments Comments are indicated with a '#' character. Everything afterwards in a line is being ignored when parsing the file .Ss Offset section Offsets are 64 bit addresses presented as hexadecimal values. It is the offset where the searchstring occurred as result when the searchlog was written. And it is also where the next search is being conducted when reading the searchlog. .Sh BUGS Report bugs to .An Aq dettus@dettus.net . Make sure to include DHEX somewhere in the subject. .Sh AUTHOR Written by .An Thomas Dettbarn .Sh SEE ALSO .Xr dhex 1 , .Xr dhexrc 5 , .Xr dhex_markers 5 .