summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2014-11-22 10:57:20 -0600
committerGregory Nutt <gnutt@nuttx.org>2014-11-22 10:57:20 -0600
commit48fb30026c653fa57f0ab644f9bd2ff57ab3d198 (patch)
tree7acae4f88fe17c73c2273ca0490869ee348a6eac
parent55809f0442612438a3d60f01b0c18315bf38e255 (diff)
downloadnuttx-48fb30026c653fa57f0ab644f9bd2ff57ab3d198.tar.gz
nuttx-48fb30026c653fa57f0ab644f9bd2ff57ab3d198.tar.bz2
nuttx-48fb30026c653fa57f0ab644f9bd2ff57ab3d198.zip
Update ChangeLog and TODO
-rwxr-xr-xnuttx/ChangeLog6
-rw-r--r--nuttx/TODO34
2 files changed, 6 insertions, 34 deletions
diff --git a/nuttx/ChangeLog b/nuttx/ChangeLog
index fc40f3a8e..9e43af2ba 100755
--- a/nuttx/ChangeLog
+++ b/nuttx/ChangeLog
@@ -9032,11 +9032,13 @@
is set to zero. From Pierre-Noel Bouteville (2014-11-20).
* fs/vfs/fs_poll.c: Add proper handling for sem_timedwait errnos.
From Jussi Kivilinna (2014-11-21).
- * net/udp/udp_conn.c and udp.h: Extensions to UDP "connectin" structure
+ * net/udp/udp_conn.c and udp.h: Extensions to UDP "connection" structure
for the case of multiple networks. In this case, assigned port numbers
only have to be unique with response to the IP address. So, for
example, you could have multiple port 80's, one on each network
(2014-11-21).
* net/tcp/tcp_conn.c and tcp.h: Make tcp_listener static scope; it is
not used outside of tcp_conn.c (2014-11-22).
-
+ * net/udp/tcp_conn.c and tcp.h: Extensions to TCP connection structure
+ for the case of multiple networks. See the description of the similar
+ change for UDP above (2014-11-22).
diff --git a/nuttx/TODO b/nuttx/TODO
index 71ae34116..0c2bcb794 100644
--- a/nuttx/TODO
+++ b/nuttx/TODO
@@ -1,4 +1,4 @@
-NuttX TODO List (Last updated November 21, 2014)
+NuttX TODO List (Last updated November 22, 2014)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This file summarizes known NuttX bugs, limitations, inconsistencies with
@@ -15,7 +15,7 @@ nuttx/
(8) Kernel/Protected Builds
(4) C++ Support
(6) Binary loaders (binfmt/)
- (13) Network (net/, drivers/net)
+ (12) Network (net/, drivers/net)
(4) USB (drivers/usbdev, drivers/usbhost)
(10) Libraries (libc/, )
(11) File system/Generic drivers (fs/, drivers/)
@@ -829,36 +829,6 @@ o Network (net/, drivers/net)
Priority: Medium. Important on slow applications that will not accept
connections promptly.
- Title: PER DEVICE PORT NUMBERS
- Description: TCP and UDP ports numbers are assigned as separater but global resources.
- Separate meaning that a UDP and TCP socket with the same port number are
- distinct. But global in the since that each TCP port number must be unique
- and TCP sockets. UDP port numbers must be similarly unique.
-
- This causes prorblems for the case where there multiple network devices
- configured into the system. In that case, it should be possible to assign
- the same TCP (or UDP) port number if the connection is associated with
- different network devices. For example, if there are two instances of
- a webserver, each listening for connections on a different device, each
- should be able to use port 80 to listen for connections.
-
- The solution is is move the TCP and UDP port related resources: They
- should not be global but shoud, instead, by a part of the device structure,
- struct net_drivers_s.
-
- STATUS: 2014-11-21: Fixed for the case of UDP. Added the local bound
- IP address to UDP "connection" structure. This essential extends all
- local addresses so they now only have to be unique for a give IP address +
- port number pair. It was not necessary to move global resources into
- the device structure as suggested above. Rather, the global structures
- to extended to support uniqueness. This is also really necessary to
- properly support broadcast addresses anyway.
-
- Status: Open
- Priority: Very low if you have only a single network interface. Higher if you
- have more than one. Very high if you need to have the same port numbers
- on each network served by the device.
-
Title: INTERRUPT LEVEL PROCESSING IN ETHERNET DRIVERS
Description: Too many Ethernet drivers do interrupt-level processing with the network
stack. The network stack supports either interrupt level processing or