Hi,
i missed the UPS guy trying to deliver the PCBs today ...
And i updated the firmware and the driver a little bit. The firmware now
supports controller auto detection and will automatically determine if
there's a display with one or two controllers installed (or no display at
all). This information can be read back via USB. lcd4linux now writes
this information at startup to the console.
Furthermore i have implemented a simple echo test. This can be used
by client software to test the reliability of the USB implementation. The
driver currently tests 100 read/write cycles and writes the results to
the log. This should allow me to check if USB transfers are the problem
if any user encounters strange display output.
And there's a small routine to return the state of the two buttons.
And yes, it's possible to add two more buttons, although they are not
present on the current PCB. But there's a rs232 debug connector on the
PCB which can easily be used to add two more button inputs. This
is just a matter of firmware and just requires me to disable debugging
when the two additional buttons are to be used.
The buttons would IMHO integrate nicely into the timer concept
described in the wiki. If buttons as well as timers could be used to
switch between different display configurations, then you can e.g.
use one button to switch to a different display (e.g. a detailed network
io screen) and have the screen return to the default state after
a few seconds. Although there are plently of other things that could
be done with some buttons, this simple mechanism would IMHO
already add some cool new possibilities to lcd4linux.
Till
--
Dr.Ing. Till Harbaum <ti...@ha...>
http://www.harbaum.org/till
|
