Hi Sam,
2017-01-12 14:06 GMT+01:00 Sam Kumar :
> Hi Martine,
> I will work on testing it with sock and PR #6004, but it may take some
> time since I might need to port the interface from conn to sock.
> It seems to me that conn is deprecated and that sock is its replacement
> moving forward. Am I
Hi Martine,
I will work on testing it with sock and PR #6004, but it may take some time
since I might need to port the interface from conn to sock.
It seems to me that conn is deprecated and that sock is its replacement
moving forward. Am I correct? And what is the motivation for moving away
from c
Hi Sam,
can you try with PR #6004 which ports POSIX sockets from conn to sock?
There are still some kinks in this PR, but I plan to fix them until the
release. On another note: the conn implementation of sockets was never
tested with TCP (since there was no TCP implementation then), but feel free
t
Hi,
@Baptiste: How did the CC1350 get into this round :-)? Is it similar to
the other mentioned radios? In any way, I would be pretty happy to see
support for that radio in RIOT. It would enhance the current SensorTag
support significantly.
@Anon: I have no idea about the differences between CC1
Hello,
I've been doing some work with the conn API for a TCP stack that I've been
developing. I noticed that on line 238 of posix_sockets.c (
https://github.com/RIOT-OS/RIOT/blame/master/sys/posix/
sockets/posix_sockets.c#L238), in the socket_close() function, the
comparison to test whether a socke