Changeset 202d54e in rtems

Timestamp:

04/19/99 14:58:16 (24 years ago)

Author:

Joel Sherrill <joel.sherrill@…>

Branches:

4.10, 4.11, 4.8, 4.9, 5, master

Children:

7cdf7fc1

Parents:

5409453

Message:

Comments from Eric Norum taken into account.

File:

• doc/networking/driver.t (modified) (3 diffs)

doc/networking/driver.t

@@ -114 +114 @@
 
 Network drivers are considered part of the BSD network package and as such
-are to be compiled with the appropriate flags.
+are to be compiled with the appropriate flags.  This can be accomplished by 
+adding @code{-D__INSIDE_RTEMS_BSD_TCPIP_STACK__} to the @code{command line}.
+If the driver is inside the RTEMS source tree or is built using the
+RTEMS application Makefiles, then adding the following line accomplishes
+this:
+
+@example
+DEFINES += -D__INSIDE_RTEMS_BSD_TCPIP_STACK__
+@end example
+
+This is equivalent to the following list of definitions.  Early versions
+of the RTEMS BSD network stack required that all of these be defined.
 
 @example
@@ -135 +146 @@
 
 @b{Application level} code including network servers such as the FTP
-daemon are @b{not} part of the BSD network package and should not be
+daemon are @b{not} part of the BSD kernel network code and should not be
 compiled with the BSD network flags.  They should include
 @code{<stdlib.h>} and not define the network stack visibility
@@ -141 +152 @@
 
 @section Write the Driver Attach Function
+
 The driver attach function is responsible for configuring the driver
 and making the connection between the network stack