| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
So far the loader-app used to do the init on its
own, which brought a lot of problems for board-
specific initialization.
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
|
|
Now we're printing the application name on all apps
that initialize the display (again).
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
|
|
libosmocore has prefixed the timer functions with omso_* already
in May 2011 (0b21c1c8850d7f33f55d9399d14055a7cdda3614), and we follow
suit here for API consistency reasons.
|
|
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
revision
|
|
|
|
The keys are correctly detected and debounced. There is no delay_ms in the
interrupt handler anymore.
When a key is pressed, the columns of the keypad are polled and debounced
via timer interrupt. If no key is pressed, the timer interrupt is ignored
again.
|
|
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
Instead of calling board_init() from every main() function explicitly,
we simply mark it as a constructor and have it called automagically
|
|
|
|
|
|
* introduce display_driver layer
* port st7558 and ssd1783 drivers to display_driver
* allow for run-time selection of display driver from board/init.c
* replace st7558_puts() calls with display_puts() calls
|
|
|
|
We now support arbitrary timers by means of 'struct timer_list'.
Any part of the program can register such a callback by means
of schedule_timer() on a millisecond-granularity. However, there
is no guarantee on the timer precision. It will not execute before
the timer expires - but it might expire quite a bit later than we
have asked it for, depending on how busy the cpu is with other work.
The timer code is in the 'comm/' directory, as it is intended to be
migrated into libosmocore soon.
Furthermore, as we currently don't yet have a scheduler or tasks,
the main() routine explicitly has to call update_timers() to check
for any expired timers and run them.
|
|
|
