[Lcdproc] RE: ezio100 MTB134 driver

[Howard Cai]

Hi Mihai and all:

We had a EZIO-100 LCD, I integrate the MTB134 drivers (your diffs - back
to 2004) with my ezio100 LCD together, it basically runs fine, but I
noticed there are some problems with the KEYPRESS read etc.

When I pressed the KEY on LCD (anyone), many times, the DRIVER just read
back nothing meaningful (buf[0] =3D 253, buf[1] =3D 79 - the scancode),
However, the scancode should be only 78, 77, 75 and 71 according to the
4 KEYCODE.

Sometimes it read back above keycode, but above 60% of times just return
nothing from above 4 keycodes. However, since the chance of reading
non-meaningful data is high, the LCD seems very bad responsive.

The driver just sent the READKEY command and read the response, and
unfortunately nothing meaningful is returned in many cases.=20

Have anyone tried this one and observed this problem before? The Baud
rate sounds need to be B2400 always.

Hardware problems, or communication problem between driver and LCD
hardware?

Thanks.

Howard