summaryrefslogtreecommitdiffstats
path: root/cpukit/libnetworking/rtems/rtems_syscall.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* 2003-05-29 Joel Sherrill <joel@OARcorp.com>Joel Sherrill2003-05-291-0/+1
| | | | * rtems/rtems_syscall.c: Removed warnings.
* 2002-11-26 Chris Johns <cjohns@cybertec.com.au>Joel Sherrill2003-01-031-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Makefile.am: Added sys/linker_set.h * kern/Makefile.am: Added kern_mib.c and kern_sysctl.c. * kern/uipc_socket.c: OID changed from KERN_SOMAXCONN to KIPC_SOMAXCONN. * kern/uipc_socket2.c: OID changed from KERN_MAXSOCKBUF to KIPC_MAXSOCKBUF. * net/if_ethersubr.c: FreeBSD 2.2.2 does not have a _net_link node while 5.0 does. * net/if_ppp.c: Removed the TEXT_SET define as these macros are now implemented. * net/rtsock.c: Enable sysctl support plus fix the bug with the lastest FreeBSD sysctl header file. * netinet/icmp_var.h: FreeBSD 2.2.2 does not have a _net_inet_icmp node while 5.0 does. * netinet/if_ether.c: FreeBSD 2.2.2 does not have a _net_link_ether node while 5.0 does. * netinet/igmp_var.h: FreeBSD 2.2.2 does not have a _net_inet_igmp node while 5.0 does. * netinet/in_pcb.c: Fixed the arguments to the sysctl call. Add inp_gencnt and ipi_count. These are used when listing connections. * netinet/in_pcb.h: Added counters to aid the listing of connections. * netinet/in_var.h: Provide the _net_inet_ip and _net_inet_raw nodes. * netinet/ip_fw.c: Disable the firewall sysctl calls. * netinet/tcp_subr.c: Merge tcp_pcblist from the lastest FreeBSD source. * netinet/tcp_var.h: Add structures needed by net-snmp to list connections. * netinet/udp_usrreq.c: Merged udp_pcblist from the lastest FreeBSD source. * netinet/udp_var.h: Added the sysctl id UDPCTL_PCBLIST. Used by net-snmp. * rtems_glue.c: Call sysctl_register_all when initialising the network stack to register all the sysctl calls. These are in the special sections and required an updated linker script. * rtems/rtems_syscall.c: Add the sysctl call. * sys/kernel.h: Use the lastest FreeBSD method of handling sysctl structures. This now held in the sys/linker_set.h file. * sys/queue.h: This is from the lastest FreeBSD code with the circular code merged back in as it is not used in the lastest FreeBSD kernel. * sys/sysctl.h: The lastest sysctl. This was needed to use with the new linker set method. The FreeBSD 2.2.2 version has asm hacks. The lastest version of the FreeBSD does not have these hacks. It uses gcc attribute directives.
* 2002-10-28 Joel Sherrill <joel@OARcorp.com>Joel Sherrill2002-10-281-2/+2
| | | | | | | | | | | | | | | | | | | | | * Pass to eliminate warnings. * kern/uipc_mbuf.c: Conditional SYSINIT() usage on __rtems__. Fix return statement without a value. * lib/ftpfs.c: read and write filesystem routines return ssize_t. * lib/syslog.c: Add include of <string.h> to eliminate warning. * lib/tftpDriver.c: read and write filesystem routines return ssize_t. * libc/gethostbydns.c: Prototype abort(). * libc/inet_ntoa.c: Prototype strcpy(). * libc/rcmd.c: Add include of <sys/select.h> * net/if_loop.c: Turn token at end of endif to comment. * net/rtsock.c, nfs/bootp_subr.c: Conditional SYSINIT() usage on __rtems__. * rtems/rtems_bootp.c: Add include of <rtems/rtems_bsdnet_internal.h>. * rtems/rtems_bsdnet_internal.h: Added prototypes for memcpy() and memset() since the BSD code tries to avoid using libc .h files since it is used to being in the kernel. * rtems/rtems_syscall.c: read and write filesystem routines return ssize_t.
* 2000-09-05 Joel Sherrill <joel@OARcorp.com>Joel Sherrill2000-09-051-1/+1
| | | | | | * rtems/rtems_syscall.c: Changed from O_NONBLOCK to internal RTEMS_LIBIO_FLAGS_NO_DELAY to avoid O_NONBLOCK/O_NDELAY confusion and to work with the converted flags.
* Merged from 4.5.0-beta3aJoel Sherrill2000-06-121-7/+10
|
* Modified to avoid conflicts on definitions of malloc. newlib 1.8.2Joel Sherrill1999-10-061-1/+1
| | | | | | | | now prototypes the malloc family in stdlib.h. This causes conflicts with the way the network stack overrides the definitions of malloc. As best I (being Joel) can tell, commenting stdlib.h out keeps the files compiling and referencing the desired malloc/free but results in more warnings.
* Patch from Eric Norum <eric@skatter.usask.ca> which changed the exitJoel Sherrill1999-03-311-2/+1
| | | | sequence.
* Patch to add shutdown() routine from Tony R. Ambardar <tonya@ece.ubc.ca>.Joel Sherrill1999-03-301-0/+25
|
* 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-011-13/+34
| | | | | 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 <eric@skatter.usask.ca> to avoid dereferencing aJoel Sherrill1999-01-281-1/+4
| | | | NULL pointer.
* Merged Eric Norum's select patch that was based on 4.0 and resolvedJoel Sherrill1998-12-101-89/+14
| | | | all conflicts.
* Patch from Ian Lance Taylor <ian@airs.com>:Joel Sherrill1998-12-071-2/+2
| | | | | | | | | | | | | 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-09-291-3/+2
| | | | | | | | | | | | | | Remember the test to see if a socket could be read and written at the same time by two different tasks? I discovered that if both tasks attempt to close the socket a panic can occur from inside the BSD code. Closing the same socket twice from two different threads is certainly an error, but a panic is not the greatest error reporting method :-) The following small change to the socket close routine should reduce the chances of the panic.
* Patches from Eric NorumJoel Sherrill1998-08-201-3/+17
|
* Added CVS IdsJoel Sherrill1998-08-201-0/+4
|
* Fixed many warnings.Joel Sherrill1998-08-201-0/+1
|
* Base filesJoel Sherrill1998-08-191-0/+743