osmocom-sdr March 2024

osmocom-sdr@lists.osmocom.org

5 participants
2 discussions

Release major version number change causing upgrade problems

by Carl Laufer

Hi, I just saw that the major version number was recently bumped on the osmocom rtl-sdr. Unfortunately this seems to be causing upgrade problems because if a user updates the drivers to the new major version number (eg to get Blog V4 support), the soname is now different, and this means that all previously installed software that uses librtlsdr will need to be recompiled from scratch, and software from the package manager will simply be broken. I'm not sure if the recent changes warrant a major version change and the problems that come with it? Regards, Carl

1 year, 2 months

[PATCH] lib/xtrx: honouring/using the loglevel parameter

by Gwenhael Goavec-Merou

loglevel parameter is never used and let loglevel to DEBUG, with an annoying flood of message in terminal. This patch adds a call to xtrx_log_setlevel() at xtrx constructor level. Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou(a)trabucayre.com> --- lib/xtrx/xtrx_obj.cc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/lib/xtrx/xtrx_obj.cc b/lib/xtrx/xtrx_obj.cc index 016b420..ab32a7f 100644 --- a/lib/xtrx/xtrx_obj.cc +++ b/lib/xtrx/xtrx_obj.cc @@ -68,6 +68,8 @@ xtrx_obj::xtrx_obj(const std::string &path, unsigned loglevel, bool lmsreset) unsigned xtrxflag = (loglevel & XTRX_O_LOGLVL_MASK) | ((lmsreset) ? XTRX_O_RESET : 0); std::cerr << "xtrx_obj::xtrx_obj = " << xtrxflag << std::endl; + xtrx_log_setlevel(loglevel, NULL); + int res = xtrx_open_string(path.c_str(), &_obj); if (res < 0) { std::stringstream message; -- 2.40.1

1 year, 3 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-sdr March 2024