1
0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
RIOT/tests/gnrc_rpl_srh/Makefile

61 lines
1.8 KiB
Makefile
Raw Normal View History

DEVELHELP := 1
# name of your application
include ../Makefile.tests_common
BOARD_INSUFFICIENT_MEMORY := arduino-duemilanove arduino-leonardo \
arduino-mega2560 arduino-nano \
2019-06-25 19:17:36 +02:00
arduino-uno hifive1 hifive1b i-nucleo-lrwan1 mega-xplained \
msb-430 msb-430h nucleo-f030r8 nucleo-f031k6 \
nucleo-f042k6 nucleo-f070rb nucleo-f072rb \
nucleo-f303k8 nucleo-f334r8 nucleo-l031k6 \
nucleo-l053r8 saml10-xpro saml11-xpro \
stm32f0discovery stm32l0538-disco telosb thingy52 \
waspmote-pro wsn430-v1_3b wsn430-v1_4 z1
boards/mips-malta: remove board. The mips-malta board is a maintainance burden, has no working UART input and is unobtainable and thus must be removed. 1. Unobtainable board ===================== The mips-malta board is not an off-the-shelf part. A quick web search only show the MIPS website where one is told to "contact sales". I could find it on ebay, used, at €155 and from single seller. Not having access to the board means: a. We cannot maintain it. In fact it could be broken right now. b. Potential RIOT uses have not access to the board either. In other words, it is pointless to run on hardware nobody has. 2. No working UART input ======================== Not all applications need UART input, but that is no excuse for not supporting it: a. Makes development & debugging way harder. b. It is impossible to run interactive tests. b.1. Constrains the rest of the platforms by providing an incentive to not make tests interactive. c. The lack of UART is a witness to the poor quality of the port. I want to stress point (c). If something as basic as a serial port cannot work, how can we expect more complex fucntionality to work. The answer is impossible to know, because of point (1). 3. Maintainance burden ====================== The RIOT project has limited time and human resources which can be better spent. a. Compiling for mips-malta wastes CPU time. b. Blacklisting the board in the test wastes contributor's time. c. Adapting the board's makefile during build system rework takes time and makes the reworks harder. c.1. Add to that that the changes are most of the time not even tested on the board because of (1). Look at the github issues/PRs and you will see it. d. Developers usually stick to the lowest common denominator. Issue (2) sets this denominator unacceptably low. MIPS platform in general ======================== In commits I will address general issues in the MIPS platform and why it should all be removed.
2019-07-03 13:19:39 +02:00
# chronos, hamilton and ruuvitag boards don't support ethos
BOARD_BLACKLIST := chronos hamilton ruuvitag
export TAP ?= tap0
CFLAGS += -DOUTPUT=TEXT
# use Ethernet as link-layer protocol
ifeq (native,$(BOARD))
USEMODULE += netdev_tap
TERMFLAGS ?= $(TAP)
else
USEMODULE += stdio_ethos
ETHOS_BAUDRATE ?= 115200
CFLAGS += -DETHOS_BAUDRATE=$(ETHOS_BAUDRATE)
TERMDEPS += ethos
TERMPROG ?= sudo $(RIOTTOOLS)/ethos/ethos
TERMFLAGS ?= $(TAP) $(PORT) $(ETHOS_BAUDRATE)
endif
USEMODULE += auto_init_gnrc_netif
# Specify the mandatory networking modules for IPv6
USEMODULE += gnrc_ipv6_router_default
USEMODULE += gnrc_icmpv6_error
USEMODULE += gnrc_pktdump
USEMODULE += gnrc_pktbuf_cmd
# IPv6 extension headers
USEMODULE += gnrc_rpl_srh
USEMODULE += od
# Add unittest framework
USEMODULE += embunit
# Add also the shell, some shell commands
USEMODULE += shell
USEMODULE += shell_commands
USEMODULE += ps
# The test requires some setup and to be run as root
# So it cannot currently be run
TEST_ON_CI_BLACKLIST += all
.PHONY: ethos
ethos:
$(Q)env -u CC -u CFLAGS make -C $(RIOTTOOLS)/ethos
include $(RIOTBASE)/Makefile.include