On 09/24/2011 06:46 AM, Werner Almesberger wrote:
From how I so far understand how things work, it shouldn't be
necessary to require BOOTP to complete before bringing up FN. I
hear that there's a TFTP boot mode that may depend on it,
It's not BOOTP but DHCP. It is enabled by default because that's what is
typically needed to connect the M1 to internet. You can remove this
delay by entering the FN "System Settings" dialog and disabling DHCP.
All those issues come in fact from RTEMS:
1) they implemented the DHCP client as a drop-in callback for BOOTP, and
they kept the BOOTP name
2) RTEMS does not boot until that BOOTP callback has returned
3) the DHCP client seems generally slightly buggy and not well tested
(see https://www.rtems.org/bugzilla/show_bug.cgi?id=1841 for example)
The boot delay could be solved by not using the BOOTP callback and
spawning a background task (as the FN GUI does when you click the button
to enable DHCP) and/or having MDIO support in the ethernet driver to
abort DHCP attempts when the cable is not connected.
(MDIO would also enable restarting the DHCP client when the cable is
reconnected, which RTEMS doesn't do atm)
Sébastien
_______________________________________________
http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org
IRC: #milkymist@Freenode
