summaryrefslogtreecommitdiffstats
path: root/cpukit/libnetworking (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to make libnetworkingJoel Sherrill1999-10-041-2/+2
| | | | a top level more independently configured package.
* Patch from Eric Norum <eric@cls.usask.ca>. Comments follow:Joel Sherrill1999-10-042-3/+5
| | | | | | The old system would panic when the loopback interface was included as part of the network initialation structures. With the printf you get an message, but the interface is still properly initialized.
* Applied patch rtems-rc-19990820-6.diff.gz fromJoel Sherrill1999-09-071-0/+24
| | | | | Ralf Corsepius <corsepiu@faw.uni-ulm.de> which converted many Makefile.in's to Makefile.am's. This added a lot of files.
* Comment cleanup from Eric Norum <eric@cls.usask.ca>.Joel Sherrill1999-08-261-5/+0
|
* Patch from Eric Norum <eric@cls.usask.ca> to readd the behavior whereJoel Sherrill1999-08-231-30/+6
| | | | the minor number indicated the port number to try.
* Patch from Eric Norum <eric@cls.usask.ca>:Joel Sherrill1999-07-121-20/+15
| | | | | | | | | | | | | | I get the following warning when compiling the latest snapshot. I had a quick look at the source -- it certainly looks to me like this is a real bug. ../../../../src/rtems-19990709/c/src/lib/libc/mount.c:97: warning: `options' might be used uninitialized in this function Also, I changed the TFTP test program and TFTP driver to reflect the changes in the way paths are passed to the TFTP driver. The TFTP driver now needs a proper `dotted-decimal' hostname as the second component of the path name.
* After comments D. V. Henkel-Wallace <gumby@zembu.com>, the interface toJoel Sherrill1999-06-151-1/+1
| | | | mount() was changed to avoid the use of a string as the options.
* Patch from Ian Lance Taylor <ian@airs.com>:Joel Sherrill1999-06-114-2/+64
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The select function is not particularly efficient when dealing with a large number of sockets. The application has to build a big set of bits and pass it in. RTEMS has to look through all those bits and see what is ready. Then the application has to look through all the bits again. On the other hand, when using RTEMS, the select function is needed exactly when you have a large number of sockets, because that is when it becomes prohibitive to use a separate thread for each socket. I think it would make more sense for RTEMS to support callback functions which could be invoked when there is data available to read from a socket, or when there is space available to write to a socket. Accordingly, I implemented them. This patch adds two new SOL_SOCKET options to setsockopt and getsockopt: SO_SNDWAKEUP and SO_RCVWAKEUP. They take arguments of type struct sockwakeup: struct sockwakeup { void (*sw_pfn) __P((struct socket *, caddr_t)); caddr_t sw_arg; }; They are used to add or remove a function which will be called when something happens for the socket. Getting a callback doesn't imply that a read or write will succeed, but it does imply that it is worth trying. This adds functionality to RTEMS which is somewhat like interrupt driven socket I/O on Unix. After the patch to RTEMS, I have appended a patch to netdemos-19990407/select/test.c to test the new functionality and demonstrate one way it might be used. To run the new test instead of the select test, change doSocket to call echoServer2 instead of echoServer.
* Patch from Eric Norum <eric@cls.usask.ca> to fix bug reported byJoel Sherrill1999-06-111-0/+2
| | | | | | | | | | | | | | | | | | Ian Lance Taylor <ian@airs.com>: Ian Lance Taylor wrote: > > In rtems-19990528, sbwait sets SB_WAIT in sb_flags. sowakeup checks > it. Why doesn't socket_select set it? > > I don't know that this is a bug--I haven't tried to create a test > case. However, it certainly looks odd. > > Ian Yes, there's a bug there. Sorry about that. It was introduced when I did some cleanup on the sleep/wakeup handling in rtems_glue.c.
* Changes from Eric Norum to add a loop and limit on the length of timeJoel Sherrill1999-05-281-22/+32
| | | | the stack will wait for mbufs.
* Alignment corrected per Eric Norum's suggestion.Joel Sherrill1999-05-281-1/+2
|
* Patch from Eric Norum <eric@pollux.usask.ca> to eliminate a panic when theJoel Sherrill1999-05-273-147/+88
| | | | network stack runs out of mbufs.
* Removed all post 4.0 changes.Joel Sherrill1999-05-201-81/+78
|
* Patch from D. V. Henkel-Wallace <gumby@zembu.com> to remove compilerJoel Sherrill1999-05-173-4/+4
| | | | warnings.
* Error reporting fixed by Jennifer.Joel Sherrill1999-05-071-15/+15
|
* Patch from Eric Norum <eric@cls.usask.ca> to corrent a miscount in lengthJoel Sherrill1999-04-271-1/+1
| | | | that results in an error in parsing network unit names/numbers.
* Changed ioctl() prototype to be more like Linux/POSIX than BSD to easeJoel Sherrill1999-04-191-1/+1
| | | | porting of ACE to RTEMS.
* After discussion with Eric Norum <eric@skatter.usask.ca>,Joel Sherrill1999-04-191-0/+22
| | | | | I added __INSIDE_RTEMS_BSD_TCPIP_STACK__ that trips all the needed macro definitions for a network driver.
* Moved sparc specific version of in_cksum_hdr to an inline routine likeJoel Sherrill1999-04-012-31/+43
| | | | | the reset of the CPU specific implementations after comment from Eric Norum.
* Patch from Eric Norum <eric@skatter.usask.ca> which changed the exitJoel Sherrill1999-03-311-2/+1
| | | | sequence.
* Removed warning for `#ifdef' argument starts with punctuation.Joel Sherrill1999-03-301-1/+1
|
* Patch to add shutdown() routine from Tony R. Ambardar <tonya@ece.ubc.ca>.Joel Sherrill1999-03-301-0/+25
|
* SPARC optimized version of IP checksum header routine. SubmittedJoel Sherrill1999-03-231-0/+32
| | | | by Jiri Gaisler <jgais@ws.estec.esa.nl>.
* Patch from Eric Norum <eric@skatter.usask.ca> to improve parsing ofJoel Sherrill1999-03-232-0/+45
| | | | | network interface names. This change does not introduce any compatibility problems.
* Patch from Eric Norum <eric@skatter.usask.ca> that adds externalJoel Sherrill1999-03-191-4/+30
| | | | fcntl support and an external fcntl handler for sockets.
* Patch from Eric Norum <eric@skatter.usask.ca> to eliminate externalJoel Sherrill1999-03-014-23/+35
| | | | | IO handlers scheme that was implemented originally just to support sockets. The file system IO switch is more general and works fine.
* Patch from Eric Norum to correct bug induced by select() patch.Joel Sherrill1999-02-052-5/+11
|
* Added printf()'s that can be uncommented to trace MBUF operations. ThisJoel Sherrill1999-02-041-0/+3
| | | | is very useful when debugging a device driver.
* Modifed to reflect transition from device driver to file system.Joel Sherrill1999-02-041-41/+4
|
* Added debug printf()'s that are commented out. Uncommenting theseJoel Sherrill1999-02-041-0/+3
| | | | | | allows one to trace the enqueueing and dequeueing of messages. This can be used to insure that packets are getting to the boundary between the network stack and the device driver.
* Added PowerPC specific header checksum code.Joel Sherrill1999-02-042-68/+10
|
* Added PowerPC specific header checksum code.Joel Sherrill1999-02-041-4/+61
| | | | Added volatile to i386 assembly statements in header checksum code.
* Debugged and now works except for handling of minor number.Joel Sherrill1999-02-041-313/+429
|
* Modified to include comments on how to get TCPDEBUG turned on andJoel Sherrill1999-02-042-1/+11
| | | | printing messages.
* Added debug #define and commented it out.Joel Sherrill1999-02-021-0/+1
|
* Added PowerPC specific in_cksum file.Joel Sherrill1999-02-021-0/+4
|
* New file. Based on the i386 version.Joel Sherrill1999-02-022-0/+404
|
* Prepended macro variables with "_" to avoid name conflicts in expansions.Joel Sherrill1999-01-311-78/+78
|
* Patch from Eric Norum <eric@skatter.usask.ca> to avoid dereferencing aJoel Sherrill1999-01-281-1/+4
| | | | NULL pointer.
* Changed prototype of rtems_bsdnet_makeFdForSocket to (void *) pointerJoel Sherrill1999-01-261-1/+1
| | | | so that the libc code did not have to know about (struct socket).
* Switched from printf() to puts().Joel Sherrill1999-01-261-1/+1
|
* Made to compile after hacking tftp driver into beginnings of a mini-filesystem.Joel Sherrill1999-01-215-39/+299
|
* Added comments for changing to a filesystemJoel Sherrill1999-01-191-0/+4
|
* Patch from D. V. Henkel-Wallace <gumby@zembu.com> to use puts and have ↵Joel Sherrill1999-01-042-2/+6
| | | | prototype.
* Patch from D. V. Henkel-Wallace <gumby@zembu.com> to fix braces nesting problem.Joel Sherrill1999-01-041-1/+2
|
* Patch from D. V. Henkel-Wallace <gumby@zembu.com> to make macro nest ↵Joel Sherrill1999-01-041-3/+5
| | | | properly in conditionals
* Merged Eric Norum's select patch that was based on 4.0 and resolvedJoel Sherrill1998-12-102-119/+20
| | | | all conflicts.
* Patch from Ian Lance Taylor <ian@airs.com>:Joel Sherrill1998-12-103-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From: Eric Norum <eric@skatter.usask.ca> Date: Sat, 5 Dec 98 13:20:51 -0600 What do you think of this patch? It implements your `tap' suggestion in a way that adds support for all ethernet devices with no driver modifications. I also added a return value from the tap function. If the return value is zero, the packet will be passed up the chain as usual. If the return value is non-zero the mbuf holding the packet will be freed and the packet will be dropped. If you like it, please submit it to Joel. I guess there needs to be an addition to the network documentation describing the additional ioctl's -- and a big warning that the tap function is called from a context that holds the network semaphore. Here is Eric's patch. I've tested it a bit, and made a couple of trivial changes. This is certainly better than mine: it should work for all Ethernet drivers. ================================================== The only concern I have about this patch is that the tap function may want to fiddle with the mbuf, calling functions like m_pullup and the like. If those force the networking code to rearrange the mbuf structure, then the caller's call to m_freem may crash. I don't know if this is a realistic concern--I don't know enough about the mbuf layer.
* Patch from Ian Lance Taylor <ian@airs.com>:Joel Sherrill1998-12-073-5/+12
| | | | | | | | | | | | | RTEMS permits using the SO_SNDTIMEO and SO_RCVTIMEO socket options to set a timeout for most socket I/O operations. However, in RTEMS 4.0.0, those options do not affect connect or accept. I don't know of any way to put a timeout on those calls in RTEMS 4.0.0; can anybody point to one. Since it is frequently useful to have a timeout on accept, and sometimes useful to have a timeout on connect shorter than the BSD system default of 75 seconds, the following patch causes SO_RCVTIMEO to affect connect and accept.
* Patch from Eric Norum <eric@skatter.usask.ca>:Joel Sherrill1998-11-195-174/+220
| | | | | | | | | | | | | | | 1) Socket timeout field changed from `short' to `long'. This makes longer timeouts possible. With a 1 kHz system clock the old system allowed timeouts only up to a little over 30 seconds! This change is a slightly cleaned-up version of the patch proposed by Ian Lance Taylor. 2) Major changes to BOOTP/DHCP reply handling. Now supports much of RFC2132. These changes were done at the request of, and with the assistance of, Erik Ivanenko. If you're making changes, you might want to change the network supplement Essentially just do a global search and replace of BOOTP with BOOTP/DHCP.
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-04 23:09:43 +0000