Hi,
> In my opinion a protocol running logically directly above the link-layer,
> such as IP (adaptation layers like 6LoWPAN may exist in between) will
> typically require information about the interface that received the
packet.
> (The same is true for other layers, e.g. UDP cannot work without
Hi Jianwen,
thread_msg does a context switch between p3 and p1 because p1 does not have
a message queue.
The second message from p3 causes p3 to go into a blocked state and give up
control otherwise the previous message will be lost.
if in p1 a msg_queue is defined:
void *thread1(void *arg)
{
Dear rustling IOTlers,
since Kaspar cannot attend today's meeting, but would be strongly interested
in the topic about the purpose of the repository, we decided to postpone this
discussion (it's not urgent anyway and with the upcoming release we have other
things to do, I guess). Since this was
Dear resolving IOTlers,
in several lengthy discussions on Github we (mostly Martine and me) discussed
if the netif header in GNRC should be mandatory. As a context: the netif
header in GNRC is a pseudo-header that contains (optional) link-layer
information such as the source and destination
