u-boot/test/common/Makefile

# SPDX-License-Identifier: GPL-2.0+
obj-y += cmd_ut_common.o
obj-$(CONFIG_AUTOBOOT) += test_autoboot.o
obj-$(CONFIG_CYCLIC) += cyclic.o
obj-$(CONFIG_EVENT) += event.o
obj-y += cread.o
test: add first autoboot unit tests This adds tests for the crypt-based and plain SHA256-based password hashing algorithms in the autoboot flow. Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de> Reviewed-by: Simon Glass <sjg@chromium.org> 2021-07-08 13:57:40 +00:00			`# SPDX-License-Identifier: GPL-2.0+`
			`obj-y += cmd_ut_common.o`
			`obj-$(CONFIG_AUTOBOOT) += test_autoboot.o`
cyclic: Add a simple test Add a test for cyclic function registration and activation. Signed-off-by: Stefan Roese <sr@denx.de> Reviewed-by: Simon Glass <sjg@chromium.org> 2022-09-02 11:57:54 +00:00			`obj-$(CONFIG_CYCLIC) += cyclic.o`
event: Add a simple test Add a test for event registration and activation. Signed-off-by: Simon Glass <sjg@chromium.org> 2022-03-04 15:43:01 +00:00			`obj-$(CONFIG_EVENT) += event.o`
cli: Correct several bugs in cli_getch() This function does not behave as expected when unknown escape sequences are sent to it: - it fails to store (and thus echo) the last character of the invalid sequence - it fails to set esc_len to 0 when it finishes emitting the invalid sequence, meaning that the following character will appear to be part of a new escape sequence - it processes the first character of the rejected sequence as a valid character, just starting the sequence all over again The last two bugs conspire to produce an "impossible condition #876" message which is the main symptom of this behaviour. Fix these bugs and add a test to verify the behaviour. Signed-off-by: Simon Glass <sjg@chromium.org> Reported-by: Heinrich Schuchardt <xypron.glpk@gmx.de> 2023-03-27 19:34:13 +00:00			`obj-y += cread.o`