Hi Anthony,
On 02/22/2017 05:17 PM, Anthony Merlino wrote:
> I'm trying to understand a few things. In the _setup command,
> how should I copy the default value struct into the overall params if
> the radio_params pointer member is const. Should I use memcpy? Or
> should I create a new struct on
Kaspar,
Thanks for this! Very clever to put a pointer to a second struct to keep the
flexibility without forcing the user to know it.
I'm trying to understand a few things. In the _setup command, how
should I copy the default value struct into the overall params if the
radio_params pointer me
Hi Anthony,
On 02/14/2017 03:56 PM, Anthony Merlino wrote:
> I am in the process of writing a radio driver for a device I'm working
> with. The device is highly configurable and I am trying to identify the
> best strategy for exposing some of the configuration to the user. For
> example, the dat
Just another idea here:
4. At the end of the netdev init method inside the radio driver, have a single
_user_config function that has a weak default implementation internally
(which does nothing). This way, the user can override that function and
configure any additional settings after the dev
Hello,
I am in the process of writing a radio driver for a device I'm working with.
The device is highly configurable and I am trying to identify the best strategy
for exposing some of the configuration to the user. For example, the data
rate, channel, preamble length, etc. can be changed to
