summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2022-05-23 11:25:08 +0200
committerSebastian Huber <sebastian.huber@embedded-brains.de>2022-05-25 08:06:57 +0200
commit0283481dab29581d74a621a3bce254fe943adf69 (patch)
tree57f4e09cd71623556c21b655d25cdddb0c436e9f
parentlibbsd.txt: Move features (diff)
downloadrtems-libbsd-0283481dab29581d74a621a3bce254fe943adf69.tar.bz2
libbsd.txt: Move network interface driver hints
-rw-r--r--CONTRIBUTING.rst14
1 files changed, 14 insertions, 0 deletions
diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
index a1c711af..af072efe 100644
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -493,3 +493,17 @@ within interrupt context is not allowed, so the Board Support Package (BSP)
should support the
`Interrupt Manager <https://docs.rtems.org/branches/master/c-user/interrupt/directives.html#rtems-interrupt-server-handler-install>`_
in general.
+
+Network Interface Drivers Hints
+===============================
+
+Link Up/Down Events
+-------------------
+
+You can notifiy the application space of link up/down events in your network
+interface driver via the
+``if_link_state_change(LINK_STATE_UP/LINK_STATE_DOWN)`` function. The
+DHCPCD(8) client is a consumer of these events for example. Make sure that the
+interface flag ``IFF_UP`` and the interface driver flag ``IFF_DRV_RUNNING`` is
+set in case the link is up, otherwise ``ether_output()`` will return the error
+status ``ENETDOWN``.