[riot-notifications] [RIOT-OS/RIOT] drivers/nrf24l01p: Netdev driver for nrf24l01p (#13743)
notifications at github.com
Mon May 4 20:47:10 CEST 2020
> hence senders must include source L2 address for IPHC,
IMO this is something that has a very strong use case in the context of a `netdev` device. In fact, I can't find a use case that uses the `netdev`-API and does not need the L2 address...
How about this: The `nrf24l01p_ng` gets tailored to meet the requirements of an IP based network stack. (For now this would mean providing only the stuff needed to run `ping6` with nRF24l01+ transceivers with the simplest implementation.) The existing `nrf24l01p` driver with its custom API does not need to fulfill the requirements of IP network stacks (such as sender's L2 address included in the frame). And on the other hand the custom API can expose unique features like multiple L2 addresses, auto-ACKs containing preloaded payloads, etc.
This way both use cases can be addressed best. And code duplication can be avoided by having e.g. an `nrf24l01p_common` module.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications