Changeset 3c0654d in rtems


Ignore:
Timestamp:
Feb 18, 2010, 12:42:41 AM (10 years ago)
Author:
Chris Johns <chrisj@…>
Branches:
4.10, 4.11, master
Children:
37c0822d
Parents:
a9fa9b7
Message:

2010-02-18 Chris Johns <chrisj@…>

  • networking/networkapp.t: Updated the BOOTP/DHCP to document the default behaviour of looping forever.
Location:
doc
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • doc/ChangeLog

    ra9fa9b7 r3c0654d  
     12010-02-18      Chris Johns <chrisj@rtems.org>
     2
     3        * networking/networkapp.t: Updated the BOOTP/DHCP to document the
     4        default behaviour of looping forever.
     5
    162010-01-11      Marc Pignat <marc.pignat@hevs.ch>
    27
  • doc/networking/networkapp.t

    ra9fa9b7 r3c0654d  
    121121You must provide a value for this entry since there is no default value for it.
    122122
    123 
    124123@item void (*bootp)(void)
    125 This entry should be set to @code{rtems_bsdnet_do_bootp}
    126 if your application will use BOOTP/DHCP
    127 to obtain network configuration information.
    128 It should be set to @code{NULL}
    129 if your application does not use BOOTP/DHCP.
    130 
     124This entry should be set to @code{rtems_bsdnet_do_bootp} if your
     125application by default uses the BOOTP/DHCP client protocol to obtain
     126network configuration information.  It should be set to @code{NULL} if
     127your application does not use BOOTP/DHCP.
     128
     129You can also use @code{rtems_bsdnet_do_bootp_rootfs} to have a set of
     130standard files created with the information return by the BOOTP/DHCP
     131protocol. The IP address is added to @file{/etc/hosts} with the host
     132name and domain returned. If no host name or domain is returned
     133@code{me.mydomain} is used. The BOOTP/DHCP server's address is also
     134added to @file{/etc/hosts}. The domain name server listed in the
     135BOOTP/DHCP information are added to @file{/etc/resolv.conf}. A
     136@code{search} record is also added if a domain is returned. The files
     137are created if they do not exist.
     138
     139The default @code{rtems_bsdnet_do_bootp} and
     140@code{rtems_bsdnet_do_bootp_rootfs} handlers will loop for-ever
     141waiting for a BOOTP/DHCP server to respond. If an error is detected
     142such as not valid interface or valid hardware address the target will
     143reboot allowing any hardware reset to correct itself.
     144
     145You can provide your own custom handler which allows you to perform
     146an initialization that meets your specific system requirements. For
     147example you could try BOOTP/DHCP then enter a configuration tool if no
     148server is found allowing the user to switch to a static configuration.
    131149
    132150@item int network_task_priority
Note: See TracChangeset for help on using the changeset viewer.