Hi,
2016-08-17 19:28 GMT+02:00 Oleg Hahm :
> Hey folks,
>
> On Mon, Aug 15, 2016 at 04:11:48PM +0200, Martine Lenders wrote:
> > as promised: here is the agenda for the meeting next Wednesday:
> > http://yourpart.eu/p/netapp-api-riot
>
> thanks for the protocol, but is a bit hard to follow as a n
Hey folks,
On Mon, Aug 15, 2016 at 04:11:48PM +0200, Martine Lenders wrote:
> as promised: here is the agenda for the meeting next Wednesday:
> http://yourpart.eu/p/netapp-api-riot
thanks for the protocol, but is a bit hard to follow as a non-attendee. Could
anyone come up with a short summary an
Hey,
On 08/16/2016 09:49 PM, Sam Kumar wrote:
> If not, I want to learn if there is another structured way to
> block a thread until an event, that I should use instead.
maybe thread_flags work for your use-case.
Kaspar
___
devel mailing list
devel@rio
Hi Sam,
in its core RIOT only provides a small and efficient mutex implementation.
Condition variables are provided within the POSIX wrapper [1],
specifically in the the pthread part [2].
To get an idea how use the provided condition variables you can have a
look in our tests for it [3].
Hi,
the meeting will start at 1pm sharp (so please set-up your mumble well
before that, if you haven't yet). Those of you who like to join me at FU
Berlin: I'll be in office 105. Everyone else: the mumble server to connect
to is at riot-labs.de:64738, the password is "riot".
Regards,
Martine
201
Dear fellow TCP implementor,
The common way implement something like this in RIOT is Message
passing. Your thread simply blocks by calling msg_receive() until it
received a message from another thread. As soon as you receive a
Packet, send a message to the via msg_send() function to wake the
block
