Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
NuttX RTOS
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
f4grx
NuttX RTOS
Commits
c5a9c367
Commit
c5a9c367
authored
16 years ago
by
patacongo
Browse files
Options
Downloads
Patches
Plain Diff
update
git-svn-id:
svn://svn.code.sf.net/p/nuttx/code/trunk@1296
42af7a65-404d-4744-a932-0658087f49c3
parent
9fe041ff
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
TODO
+7
-12
7 additions, 12 deletions
TODO
with
7 additions
and
12 deletions
TODO
+
7
−
12
View file @
c5a9c367
NuttX TODO List (Last updated November
19
, 2008)
NuttX TODO List (Last updated November
20
, 2008)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(7) Task/Scheduler (sched/)
...
...
@@ -7,7 +7,7 @@ NuttX TODO List (Last updated November 19, 2008)
(1) Signals (sched/, arch/)
(1) pthreads (sched/)
(1) C++ Support
(1
5
) Network (net/, netutils/)
(1
2
) Network (net/, netutils/)
(1) USB (drivers/usbdev)
(4) Libraries (lib/)
(6) File system/Generic drivers (fs/, drivers/)
...
...
@@ -190,22 +190,17 @@ o Network (net/, netutils/)
Priority: Low
Description: At present, there cannot be two concurrent active TCP send
operations in progress
. This is because the uIP ACK logic will
support only one transfer at a time. The
solution is simple:
A mutex will be needed to make sure that each
send that is
started is able to be the exclusive sender until all of
the
data to be sent has been ACKed.
operations in progress
using the same socket. This is because
the uIP ACK logic will
support only one transfer at a time. The
solution is simple:
A mutex will be needed to make sure that each
send that is
started is able to be the exclusive sender until all of
the
data to be sent has been ACKed.
Status: Open. There is some temporary logic to examples/nsh that does
this same fix and that temporary logic should be removed when
send() is fixed.
Priority: Medium-Low. This is an important issue for applications that
send on the same TCP socket from multiple threads.
Description: Some application-level interface to the ICMP logic is needed
to support ping from the target.
Status: Open
Priority: Low
Description: TCP supports read-ahead buffering to handle the receipt of
TCP/IP packets when there is no read() in place. Should such
capability be useful for UDP? PRO: Would reduce packet loss
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment