summaryrefslogtreecommitdiffstats
path: root/isdb-t/br-pb-BaiaDaTraicao
blob: 0f796641a77058d9d42804529e5e5b8115119182 (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
26
27
28
29
30
31
32
# Channel table for Baía da Traição - PB - Brazil
# Source: http://www.portalbsd.com.br/terrestres_channels.php?channels=2638

# Physical channel 19
[TV Cabo Branco]
	DELIVERY_SYSTEM = ISDBT
	BANDWIDTH_HZ = 6000000
	FREQUENCY = 503142857
	INVERSION = AUTO
	GUARD_INTERVAL = AUTO
	TRANSMISSION_MODE = AUTO
	INVERSION = AUTO
	GUARD_INTERVAL = AUTO
	TRANSMISSION_MODE = AUTO
	ISDBT_LAYER_ENABLED = 7
	ISDBT_SOUND_BROADCASTING = 0
	ISDBT_SB_SUBCHANNEL_ID = 0
	ISDBT_SB_SEGMENT_IDX = 0
	ISDBT_SB_SEGMENT_COUNT = 0
	ISDBT_LAYERA_FEC = AUTO
	ISDBT_LAYERA_MODULATION = QAM/AUTO
	ISDBT_LAYERA_SEGMENT_COUNT = 0
	ISDBT_LAYERA_TIME_INTERLEAVING = 0
	ISDBT_LAYERB_FEC = AUTO
	ISDBT_LAYERB_MODULATION = QAM/AUTO
	ISDBT_LAYERB_SEGMENT_COUNT = 0
	ISDBT_LAYERB_TIME_INTERLEAVING = 0
	ISDBT_LAYERC_FEC = AUTO
	ISDBT_LAYERC_MODULATION = QAM/AUTO
	ISDBT_LAYERC_SEGMENT_COUNT = 0
	ISDBT_LAYERC_TIME_INTERLEAVING = 0
protocol, you should specify the -a or --address parameter. If the parameter is omitted, the driver listens to all device addresses. Some examples: Listen to *any* IR transmitter with uses the RC5 protocol: # ./av7110_loadkeys hauppauge.rc5 > /proc/av7110_ir Listen to RC5 transmitter with address 2: # ./av7110_loadkeys -a 2 hauppauge.rc5 > /proc/av7110_ir If you don't know the correct value for the -a parameter, take a look on the debug output of the driver (see below). Now you can test your hardware setup using evtest # ./evtest /dev/input/eventX where eventX is the IR input event device, usually event0 if you don't use USB mice or keyboards. ------------------------------------------------------------------------ Keymaps are in format: <key> <associated input keycode> 0x00 KEY_0 0x01 KEY_1 0x42 KEY_HOME ------------------------------------------------------------------------ In order to write a new keymap you might want to see the raw key values in the kernel log. Use # insmod dvb-ttpci.o av7110_ir_debug=1 in order to enable some verbosity in the av7110_ir driver. Then watch the kernel log while pressing your remote control keys. When you don't see any messages in your kernel log you should check all electrical connections, the selected protocol (RC5 or RCMM?) and the inversion setting. You find a list of all linux input key identifiers in </usr/include/input.h> and "./input_fake.h". Please post new keymaps on the linux-dvb mailing list or send them to me <holger@convergence.de>. have fun! Holger