Building with !MULTITHREADING is designed for bootloaders and similar minimal-functionality use cases. It's pathologically silly to combine it with MMU drivers and address space partitioning, even though on some architectures that technically works (on ARM, it seems not to). The test intent was to disable this originally, but it turns out that doesn't work. There is a TEST_USERSPACE kconfig symbol that also needs to be explicitly turned off, otherwise it will reselect USERSPACE against our wishes. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
13 lines
408 B
Plaintext
13 lines
408 B
Plaintext
CONFIG_ZTEST=y
|
|
CONFIG_MULTITHREADING=n
|
|
CONFIG_BT=n
|
|
CONFIG_USB=n
|
|
|
|
# Running without multithreading implies the lack of MMU support.
|
|
# Setting CONFIG_USERSPACE=n alone is not enough to disable userspace.
|
|
# The TEST_USERSPACE symbol (designed to enable userspace by default
|
|
# on tests platforms that support it) defaults to =y and will
|
|
# automatically select it back.
|
|
CONFIG_TEST_USERSPACE=n
|
|
CONFIG_USERSPACE=n
|