path: root/doc/networking/networkapp.t
diff options
authorChris Johns <>2010-02-18 00:42:41 +0000
committerChris Johns <>2010-02-18 00:42:41 +0000
commit3c0654db96b91a9e6ed6f57a19c03d8756af2436 (patch)
treea7cc493229a02d6c411b52a5fc700c3194bf7568 /doc/networking/networkapp.t
parenta9fa9b765df38cc5319ae734b5148fd47ebbfd8d (diff)
2010-02-18 Chris Johns <>
* networking/networkapp.t: Updated the BOOTP/DHCP to document the default behaviour of looping forever.
Diffstat (limited to '')
1 files changed, 25 insertions, 7 deletions
diff --git a/doc/networking/networkapp.t b/doc/networking/networkapp.t
index dc85043aa3..8a7ee4e880 100644
--- a/doc/networking/networkapp.t
+++ b/doc/networking/networkapp.t
@@ -120,14 +120,32 @@ A pointer to the first configuration structure of the first network
device. This structure is described in the following section.
You must provide a value for this entry since there is no default value for it.
@item void (*bootp)(void)
-This entry should be set to @code{rtems_bsdnet_do_bootp}
-if your application will use BOOTP/DHCP
-to obtain network configuration information.
-It should be set to @code{NULL}
-if your application does not use BOOTP/DHCP.
+This entry should be set to @code{rtems_bsdnet_do_bootp} if your
+application by default uses the BOOTP/DHCP client protocol to obtain
+network configuration information. It should be set to @code{NULL} if
+your application does not use BOOTP/DHCP.
+You can also use @code{rtems_bsdnet_do_bootp_rootfs} to have a set of
+standard files created with the information return by the BOOTP/DHCP
+protocol. The IP address is added to @file{/etc/hosts} with the host
+name and domain returned. If no host name or domain is returned
+@code{me.mydomain} is used. The BOOTP/DHCP server's address is also
+added to @file{/etc/hosts}. The domain name server listed in the
+BOOTP/DHCP information are added to @file{/etc/resolv.conf}. A
+@code{search} record is also added if a domain is returned. The files
+are created if they do not exist.
+The default @code{rtems_bsdnet_do_bootp} and
+@code{rtems_bsdnet_do_bootp_rootfs} handlers will loop for-ever
+waiting for a BOOTP/DHCP server to respond. If an error is detected
+such as not valid interface or valid hardware address the target will
+reboot allowing any hardware reset to correct itself.
+You can provide your own custom handler which allows you to perform
+an initialization that meets your specific system requirements. For
+example you could try BOOTP/DHCP then enter a configuration tool if no
+server is found allowing the user to switch to a static configuration.
@item int network_task_priority
The priority at which the network task and network device