mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2025-01-17 00:32:44 +01:00
ee6b6b9c38
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.
|
||
|---|---|---|
| .. | ||
| tests | ||
| main.c | ||
| Makefile | ||
| README.md | ||
Overview
This folder contains a test application for RIOT's sock-based DNS client.
How to test with native
Setup up a tap interface:
$ sudo ip tuntap add dev tap0 mode tap user $(id -u -n)
$ sudo ip a a 2001:db8::1/64 dev tap0
$ sudo ip link set up dev tap0
Start dnsmasq (in another console):
$ sudo dnsmasq -d -2 -z -i tap0 -q --no-resolv \
--dhcp-range=::1,constructor:tap0,ra-only \
--host-record=example.org,10.0.0.1,2001:db8::1
(NetworkManager is known to start an interfering dnsmasq instance. It needs to be stopped before this test.)
Then run the test application
$ make term
Now use the RIOT shell to configure the DNS server and request example.org
from it
> dns server 2001:db8::1
> dns server
DNS server: [2001:db8::1]:53
> dns request example.org
example.org resolves to 2001:db8::1