Files
rtems/cpukit/libnetworking
Joel Sherrill 766ed7c0f1 Patch from Eric Norum <eric@skatter.usask.ca>:
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.
1998-09-29 12:15:08 +00:00
..
1998-08-20 22:04:22 +00:00
1998-08-20 21:47:37 +00:00
1998-08-20 21:56:40 +00:00
1998-08-21 13:04:55 +00:00
1998-08-20 21:56:40 +00:00
1998-08-20 21:47:37 +00:00
1998-08-20 21:47:37 +00:00
1998-08-20 21:56:40 +00:00
1998-08-19 21:32:28 +00:00
1998-08-20 21:56:40 +00:00
1998-08-20 21:56:40 +00:00
1998-08-19 21:32:28 +00:00
1998-08-20 21:56:40 +00:00
1998-08-20 21:56:40 +00:00
1998-08-20 21:56:40 +00:00
1998-08-19 21:32:28 +00:00
1998-08-20 21:56:40 +00:00
1998-08-19 21:32:28 +00:00
1998-08-20 21:56:40 +00:00

#
#  $Id$
#

This is a snapshot of my attempt to fit the FreeBSD networking code into
RTEMS.  Things seem to be working!

Things that need to be done:
	1) More documentation!
	2) Figure out what's still not working :-)
	3) Rationalize the include files.  Right now I have a special
	   hack in the Makefile to ensure that I pick up the FreeBSD versions
	   of the include files that are duplicated between RTEMS
	   and FreeBSD.
	   The network device driver source should move to the BSP source tree.
	4) Have a look at all the FIXME comments.
	5) Go through and make sure that all the source files are
	   free of undesired copyright restrictions.