diff options
| author | Gregory Nutt <gnutt@nuttx.org> | 2015-03-23 19:03:51 -0600 |
|---|---|---|
| committer | Gregory Nutt <gnutt@nuttx.org> | 2015-03-23 19:03:51 -0600 |
| commit | 72a289c4ce6d44f9aaafbec546599cb3a72f5525 (patch) | |
| tree | ba151d53fc0d705334a05823d032b671739286fb /apps/examples/touchscreen | |
| parent | 59a132f2a5e7e41d1bb68c7429ca810706702190 (diff) | |
| download | px4-nuttx-72a289c4ce6d44f9aaafbec546599cb3a72f5525.tar.gz px4-nuttx-72a289c4ce6d44f9aaafbec546599cb3a72f5525.tar.bz2 px4-nuttx-72a289c4ce6d44f9aaafbec546599cb3a72f5525.zip | |
Make sure that FPU test, HID keyboard example, and touchscreen options are only available in the FLAT build
Diffstat (limited to 'apps/examples/touchscreen')
| -rw-r--r-- | apps/examples/touchscreen/Kconfig | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/apps/examples/touchscreen/Kconfig b/apps/examples/touchscreen/Kconfig index b75546c8b..e266972b6 100644 --- a/apps/examples/touchscreen/Kconfig +++ b/apps/examples/touchscreen/Kconfig @@ -46,6 +46,7 @@ config EXAMPLES_TOUCHSCREEN_MOUSE config EXAMPLES_TOUCHSCREEN_ARCHINIT bool "Architecture-specific initialization" default y + depends on !BUILD_PROTECTED && !BUILD_KERNEL ---help--- By default, the touchscreen example will call arch_tcinitialize() to register the touchscreen device before it attempts to open it. @@ -54,7 +55,7 @@ config EXAMPLES_TOUCHSCREEN_ARCHINIT This works well for the typical touchscreen controller but there are other devices that cannot be initialized and uninitialized in this - fashion. Consider a USB mouse, fo example. The USB mouse will be + fashion. Consider a USB mouse, for example. The USB mouse will be registered when the mouse is connected and unregistered when the mouse is disconnected. @@ -64,4 +65,12 @@ config EXAMPLES_TOUCHSCREEN_ARCHINIT de-selected, then the arch_tcinitialize() and arch_tcuninitialize() will never be called. + NOTE also that the functions arch_tcinitialize() and + arch_tcuninitialize() are effective non-standard operating system + calls. This is cheap shortcut and a violation of the OS interface. + You can get away with this in the flat build (CONFIG_BUILD_FLAT), + but not in the protected or kernel builds (CONFIG_BUILD_PROTECTED + or CONFIG)BUILD_KERNEL). In those cases, you will need to perform + one-time touchscreen initialization in board_initialize(). + endif |