There is a confusing type disagreement between the variable type and the return type of the pmt conversion function in gr-uhd/lib/usrp_block_impl.cc in the usrp_block_impl::_cmd_handler_gpio function.
I want to ask whether there was a legitimate reason for using the pmt::to_double and then implicitly casting to uint32_t? Should this not rather use pmt::to_uint64 or pmt::to_long?
What happened?
There is a confusing type disagreement between the variable type and the return type of the pmt conversion function in gr-uhd/lib/usrp_block_impl.cc in the
usrp_block_impl::_cmd_handler_gpio
function.I want to ask whether there was a legitimate reason for using the pmt::to_double and then implicitly casting to uint32_t? Should this not rather use pmt::to_uint64 or pmt::to_long?
System Information
OS: Ubuntu Focal (Windows 10 WSL) GR Installation Method: Source (via pybombs)
GNU Radio Version
3.10 (maint-3.10)
Specific Version
3.10.0.0
Steps to Reproduce the Problem
Observe the code. This may be contributing to errors attempting to control the GPIO via tagged tx_commands for an Ettus N210 device.
Relevant log output
No response