mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
276ad5716a
A if `netdev_driver_t::confirm_send()` is provided, it provides the new netdev API. However, detecting the API at runtime and handling both API styles comes at a cost. This can be optimized in case only new or only old style netdevs are in use. To do so, this adds the pseudo modules `netdev_legacy_api` and `netdev_new_api`. As right now no netdev actually implements the new API, all netdevs pull in `netdev_legacy_api`. If `netdev_legacy_api` is in used but `netdev_new_api` is not, we can safely assume at compile time that only legacy netdevs are in use. Similar, if only `netdev_new_api` is used, only support for the new API is needed. Only when both are in use, run time checks are needed. This provides two helper function to check for a netif if the corresponding netdev implements the old or the new API. (With one being the inverse of the other.) They are suitable for constant folding when only new or only legacy devices are in use. Consequently, dead branches should be eliminated by the optimizer.
15 lines
513 B
Makefile
15 lines
513 B
Makefile
USEMODULE += netdev_eth
|
|
USEMODULE += ztimer_msec
|
|
USEMODULE += netdev_legacy_api
|
|
USEPKG += driver_atwinc15x0
|
|
FEATURES_REQUIRED += periph_gpio
|
|
FEATURES_REQUIRED += periph_gpio_irq
|
|
FEATURES_REQUIRED += periph_spi
|
|
|
|
# esp8266 and esp32 vendor code and atwinc15x0 both define conflicting
|
|
# spi_flash_{read, write} functions.
|
|
# esp8266 and esp32 already have build-in WiFi, so it's unlikely to ever
|
|
# use this driver - just blacklist the architecture.
|
|
FEATURES_BLACKLIST += arch_esp8266
|
|
FEATURES_BLACKLIST += arch_esp32
|