aboutsummaryrefslogtreecommitdiffstats
path: root/README.Drivers
blob: 98628ecb3432f6b769d2e877e3b0ac9b1492a614 (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
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
0x00 KEY_0
0x01 KEY_1
0x02 KEY_2
0x03 KEY_3
0x04 KEY_4
0x05 KEY_5
0x06 KEY_6
0x07 KEY_7
0x08 KEY_8
0x09 KEY_9
0x0C KEY_POWER
0x0D KEY_MUTE
0x0E KEY_OK
0x0F KEY_DIGITS
0x10 KEY_RIGHT
0x11 KEY_LEFT
0x1E KEY_STOP
0x20 KEY_UP
0x21 KEY_DOWN
0x23 KEY_AB
0x24 KEY_RECORD
0x25 KEY_SUBTITLE
0x26 KEY_INFO
0x29 KEY_PLAY
0x2A KEY_FORWARD
0x2B KEY_PAUSE
0x2C KEY_REWIND
0x2D KEY_F4
0x2E KEY_F3
0x32 KEY_YELLOW
0x34 KEY_BLUE
0x36 KEY_GREEN
0x37 KEY_RED
0x38 KEY_AUX
0x3C KEY_F2
0x3D KEY_SCREEN
0x3F KEY_F1
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.