All posix arch boards are required to provide the same tracing/print API. So, instead of having a different driver for native_posix and the bsim boards, let's have a common one which uses this API. This in turn results in the printk strings being printed in the same underlaying backend as before with individual drivers. A part from this, the native_posix console driver was a full backend for the now long gone Zephyr console shell (named legacy_shell from527256501funtil it was retired infd0b7f7767). The whole input handling in this driver was dead code (since140a8d0c8a) Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
25 lines
579 B
Plaintext
25 lines
579 B
Plaintext
# Copyright (c) 2022 Nordic Semiconductor
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
# Current the use of X86 is for consistency with old testsuite/ztest which
|
|
# defined CONFIG_X86 manually. To consider, is NATIVE_POSIX a better choice?
|
|
config X86
|
|
bool
|
|
default y
|
|
help
|
|
The unit_testing architecture identifies itself as X86 for basic
|
|
ztest and kernel support.
|
|
|
|
if CONSOLE
|
|
|
|
config POSIX_ARCH_CONSOLE
|
|
bool
|
|
default y
|
|
select CONSOLE_HAS_DRIVER
|
|
help
|
|
The unit testing architecture is expected to always have access to a
|
|
standard terminal for printing.
|
|
|
|
endif # CONSOLE
|