Gunar Schorcht

@MrKevinWeiss Since we are now using the ESP-IDF SPI HAL/LL for ESP32, ESP32 has its own `periph/spi` implementation which should be covered by this PR. Even though `cpu/esp32/periph/spi.c` already uses...

@MrKevinWeiss I committed the changes for ESP32 to your branch.

@MrKevinWeiss The test failed due to a syntax error. Murdock is idle, so it's good time to do some tests now.

@benpicco Do you know who has Apple macOS and could test it?

> I'd recommend changing the first if-statement in `install_qemu` to something like > > ``` > if [[ ${OS} != "linux-amd64" && ${OS} != "macos" ]]; then > echo "error:...

> (Please note that I'm not familiar with bash scripting) It's not Bash syntax. Used interpreter is just `bin/sh`, the Bourne Shell. Even though `bin/sh` is linked to the Dash...

@leandrolanzieri Again a question about Kconfig: This PR adds the ESP32-S3-DevKit board for which 10 different versions are available. All have exactly the same peripheral configuration and differ only by...

> > but it doesn't work since the BOARD_VERSION variable in boards/esp32s3-devkit/Makefile.features is set to default if not defined at command line before Kconfig is used. > > Do you...

> Kconfig does not require the features from `Makefile.features`, can we check for `TEST_KCONFIG` and not assign a value then? If it is OK to check for `TEST_KCONFIG` in `Makefile.features`,...

> > Kconfig does not require the features from `Makefile.features`, can we check for `TEST_KCONFIG` and not assign a value then? > > If it is OK to check for...