arch/arm/src/stm32f0l0: Eliminate some warnings found in build testing.

This commit is contained in:
Gregory Nutt 2019-05-13 12:29:26 -06:00
parent 6677471ee8
commit 8905bd6fa6
4 changed files with 27 additions and 2 deletions

View File

@ -44,9 +44,10 @@
#include "chip.h" #include "chip.h"
#include "hardware/stm32_adc.h"
#include <nuttx/analog/adc.h> #include <nuttx/analog/adc.h>
#include <arch/chip/chip.h>
#include "hardware/stm32_adc.h"
/************************************************************************************ /************************************************************************************
* Pre-processor Definitions * Pre-processor Definitions

View File

@ -49,6 +49,8 @@
#include <nuttx/irq.h> #include <nuttx/irq.h>
#include <nuttx/arch.h> #include <nuttx/arch.h>
#include <arch/chip/chip.h>
#include "up_arch.h" #include "up_arch.h"
#include "up_internal.h" #include "up_internal.h"
#include "sched/sched.h" #include "sched/sched.h"

View File

@ -548,6 +548,13 @@ Configurations
terminal does not receive console input. NxTerm input is via terminal does not receive console input. NxTerm input is via
/dev/console. /dev/console.
NOTE: Since the NxTerm keyboard input comes directly from /dev/console,
it goes to whichever task has an outstanding read on the console
device. That works well if there is only a single NxTerm window.
But if there are multiple NxTerm windows, then it is anyone's guess
which will receive the keyboard input. That does not work well in
such cases.
Some known bugs yet-to-fixed. Surely there are more as will be revealed Some known bugs yet-to-fixed. Surely there are more as will be revealed
by additional testing: by additional testing:

View File

@ -423,6 +423,21 @@ config NXTERM_NXKBDIN
by window callback functions so that keyboard input *only* goes to the by window callback functions so that keyboard input *only* goes to the
top window. top window.
NOTE: nxterm_kdbin() is an internal OS API. It can be accessed by
applications via the boardctl(BOARDIOC_NXTERM) interface.
The logic path is complex in this case: (1) The keyboard input is
received by an application listener thread and injected into NX via
nx_kbdin(). NX sends (2) the keyboard input to single the NX window
that has focus. That window then (3) gives the keyboard input to the
single NxTerm associated with the window via boardctl(BOARDIOC_NXTERM).
NOTE: If CONFIG_NXTERM_NXKBDIN not defined, then NxTerm input coming
directly from /dev/console. That works well if there is only a single
NxTerm window. But if there are multiple NxTerm windows, then it is
anyone's guess which will receive the keyboard input. That does not
work well in such cases.
config NXTERM_KBDBUFSIZE config NXTERM_KBDBUFSIZE
int "Keyboard Input Buffer Size" int "Keyboard Input Buffer Size"
default 16 default 16