[riot-notifications] [RIOT-OS/RIOT] [RFC] at86rf2xx: implement radio HAL (#16535)

José Alamos notifications at github.com
Mon Jun 7 16:50:24 CEST 2021


> Just from a complexity stand-point option two seems more reasonable. From what I understand, option 1 needs (#network stacks ⨉ #network device drivers) abstraction layers and option 2 needs only #network device drivers abstraction layers. I am confused though, that you pointed this out as the drawback of option 2, so I am not sure I am seeing the whole picture.

Option 2 requires "device drivers ⨉ BH mechanisms". On one side, we are using 4 BH mechanisms (msg_t, event_thread, thread_flags, pure ISR).  Then each network stack needs to pick one of the mechanisms. On the other side, I think we should slowly try to unify the BH of the drivers to e.g thread_flags or event_thread. In order to be compliant with the IEEE 802.15.4 standard the radios need some kind of determinism, which is hard to achieve with e.g message queues.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/16535#issuecomment-856002872
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210607/117f3995/attachment.htm>


More information about the notifications mailing list