aboutsummaryrefslogtreecommitdiffstats
path: root/dvb-t/fr-Alençon
blob: 73747f7e5e900f839cd6f1cac0c778fc8f08a629 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
# Alençon - France (DVB-T transmitter of Alençon ( Montsd'Amain ) )
# Alençon - France (signal DVB-T transmis depuis l'émetteur de Montsd'Amain )
#
# ATTENTION ! Ce fichier a ete construit automatiquement a partir
# des frequences obtenues sur : http://www.tvnt.net/multiplex_frequences.htm
# en Avril 2006. Si vous constatez des problemes et voulez apporter des
# modifications au fichier, envoyez le fichier modifie a
# l'adresse linux-dvb@linuxtv.org (depot des fichiers d'init dvb)
# ou a l'auteur du fichier :
# Nicolas Estre <n_estre@yahoo.fr>
#
# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
#### Alençon - Montsd'Amain ####
#R1
T 618000000 8MHz AUTO NONE QAM64 8k AUTO NONE
#R2
T 826000000 8MHz AUTO NONE QAM64 8k AUTO NONE
#R3
T 698000000 8MHz AUTO NONE QAM64 8k AUTO NONE
#R4
T 634000000 8MHz AUTO NONE QAM64 8k AUTO NONE
#R5
T 602000000 8MHz AUTO NONE QAM64 8k AUTO NONE
#R6
T 770000000 8MHz AUTO NONE QAM64 8k AUTO NONE
no need for a <drivername>.h * create one (or more) unique display names (your driver will be selected by this name in the 'Display'-line of lcd4linux.conf). * include "display.h" in your driver, to get the LCD structure and various BAR_ definitions * include "cfg.h" if you need to access settings in the config file. * create a LCD table at the bottom of your driver, and fill it with the appropriate values. Take care that you specify the correct bar capabilities of your display or driver: BAR_L: horizontal bars headed left BAR_R: horizontal bars headed right BAR_H2: driver supports horizontal dual-bars BAR_U: vertical bars bottom-up BAR_D: vertical bars top-down BAR_V2: driver supports vertical dual-bars * edit display.c and create a reference to your LCD table: external LCD YourDriver[]; * extend the FAMILY table in display.c with your driver: FAMILY Driver[] = { { "Skeleton", Skeleton }, { "MatrixOrbital", MatrixOrbital }, { "YourFamily", YourDriver }, { "" } }; * write the correspondig init(), clear(), put(), bar(), quit() and flush()-functions. There's no need to use a framebuffer and display its contents with the flush()- call (as in MatrixOrbital.c), you can directly write to the display in the put()- and bar()-functions, and use an empty flush()-function. But if you have a limited number of user-defined characters, and therefore you have to do some sort of 'character reduction' or similar stuff, you will have to use a framebuffer and the flush()-call.