nuttx

accept.c

net_startmonitor.c always returned zero. In the case where a socket has already been closed, it correctly handled the disconnetion event but still returned OK. Returning OK causes the callers of net_startmonitor to assume that the connection was okay, undoing the good things that net_startmonitor did and causing the socket to be marked as connected. This behavior was noted by Pelle Windestam.

2015-05-28 08:23:51 -06:00

bind.c

Unix domain: Add options to build in stream or datagram support separately

2015-01-31 07:58:51 -06:00

connect.c

net_startmonitor.c always returned zero. In the case where a socket has already been closed, it correctly handled the disconnetion event but still returned OK. Returning OK causes the callers of net_startmonitor to assume that the connection was okay, undoing the good things that net_startmonitor did and causing the socket to be marked as connected. This behavior was noted by Pelle Windestam.

2015-05-28 08:23:51 -06:00

getsockname.c

…

getsockopt.c

Suffer the consequences of moving struct timeval to its correct location

2015-02-15 15:18:35 -06:00

Kconfig

…

listen.c

…

Make.defs

Unix domain: Add options to build in stream or datagram support separately

2015-01-31 07:58:51 -06:00

net_checksd.c

…

net_clone.c

…

net_close.c

net_startmonitor.c always returned zero. In the case where a socket has already been closed, it correctly handled the disconnetion event but still returned OK. Returning OK causes the callers of net_startmonitor to assume that the connection was okay, undoing the good things that net_startmonitor did and causing the socket to be marked as connected. This behavior was noted by Pelle Windestam.

2015-05-28 08:23:51 -06:00

net_dupsd2.c

…

net_dupsd.c

socket: net_dupsd: Do not call sockfd_socket() twice. From Juha Niskanen

2015-03-12 08:11:08 -06:00

net_monitor.c

net_startmonitor.c always returned zero. In the case where a socket has already been closed, it correctly handled the disconnetion event but still returned OK. Returning OK causes the callers of net_startmonitor to assume that the connection was okay, undoing the good things that net_startmonitor did and causing the socket to be marked as connected. This behavior was noted by Pelle Windestam.

2015-05-28 08:23:51 -06:00

net_poll.c

Networking: Separate TCP poll logic out of net/sockets/net_poll.c and move it into the new net/tcp/tcp_netpoll.c.

2015-01-30 07:25:01 -06:00

net_sendfile.c

net/: Lots of build problems introduced into multiple NIC support. Many places where conditional logic based on CONFIG_NETDEV_MULTINIC is confused with CONFIG_NET_MULTILINK. Lots of code changed with IPv6 that was never compiled with MULTINIC enabled. Still some problem with parameter passing.

2015-02-09 18:15:34 -06:00

net_sockets.c

Add function headers to prototypes in net/socket/socket.h

2015-05-28 07:26:03 -06:00

net_timeo.c

…

net_vfcntl.c

Unix domain: Add options to build in stream or datagram support separately

2015-01-31 07:58:51 -06:00

recv.c

…

recvfrom.c

Fix missing file and some compilation errors from the last UDP committ

2015-05-29 10:45:41 -06:00

send.c

Unix domain: Add options to build in stream or datagram support separately

2015-01-31 07:58:51 -06:00

sendto.c

UDP Networking: Misc fixes to get the last changes working + cleanup

2015-05-29 14:32:56 -06:00

setsockopt.c

Networking: setsockopt() fails when setting timeouts to values less that an 100 msec. That is because the timeout is limited to stops of 1 decisecond and because the conversion of structure timeval was truncating the microsecond remainder. The utility net_timeval2dsec now accespts and option to determin how it handles the remainder: truncate, discarding the remainder, use the remainder to round to the closed decisecond value, or use any non-zero remainder to the next larger whole decisecond value.

2015-05-29 07:17:15 -06:00

socket.c

Networking: Fix a compilation error recently introduced into the raw packet logic

2015-02-11 09:30:30 -06:00

socket.h

net_startmonitor.c always returned zero. In the case where a socket has already been closed, it correctly handled the disconnetion event but still returned OK. Returning OK causes the callers of net_startmonitor to assume that the connection was okay, undoing the good things that net_startmonitor did and causing the socket to be marked as connected. This behavior was noted by Pelle Windestam.

2015-05-28 08:23:51 -06:00