RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

2010-02-18 Chris Johns <chrisj@rtems.org>

Browse Source 
* networking/networkapp.t: Updated the BOOTP/DHCP to document the
        default behaviour of looping forever.
This commit is contained in:
Chris Johns
2010-02-18 00:42:41 +00:00
parent a9fa9b765d
commit 3c0654db96
2 changed files with 29 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/ChangeLog
View File

@@ -1,3 +1,8 @@
2010-02-18 Chris Johns <chrisj@rtems.org>
* networking/networkapp.t: Updated the BOOTP/DHCP to document the
default behaviour of looping forever.
2010-01-11 Marc Pignat <marc.pignat@hevs.ch>
PR 1490/doc

30
doc/networking/networkapp.t
View File

@@ -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