From 29e4a1ba3c149a7462da355c16f8cd230240914f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Joakim=20Nohlg=C3=A5rd?= <joakim.nohlgard@eistec.se>
Date: Sat, 30 Jun 2018 15:30:50 +0200
Subject: [PATCH] gnrc_netif: Introduce GNRC_NETIF_HDR_FLAGS_MORE_DATA
---
sys/include/net/gnrc/netif/hdr.h | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/sys/include/net/gnrc/netif/hdr.h b/sys/include/net/gnrc/netif/hdr.h
index 3e6aef7eaa..28d871d1f5 100644
--- a/sys/include/net/gnrc/netif/hdr.h
+++ b/sys/include/net/gnrc/netif/hdr.h
@@ -70,6 +70,21 @@ extern "C" {
* this flag the same way it does @ref GNRC_NETIF_HDR_FLAGS_BROADCAST.
*/
#define GNRC_NETIF_HDR_FLAGS_MULTICAST (0x40)
+
+/**
+ * @brief More data will follow
+ *
+ * @details This flag signals that this packet is part of a burst of packets.
+ * The link layer implementation can choose to translate this flag into
+ * frame header bits to tell the remote node that more traffic will
+ * follow shortly. The most direct use case for this flag is to set it
+ * for fragmented packets in duty cycled networks to tell the remote
+ * node to keep its radio turned on after receiving the first fragment.
+ *
+ * @see The corresponding bit in the IEEE 802.15.4 frame control field,
+ * @ref IEEE802154_FCF_FRAME_PEND
+ */
+#define GNRC_NETIF_HDR_FLAGS_MORE_DATA (0x10)
/**
* @}
*/
--
GitLab