Hi guys,
I think some of us would like to move to redmine and start using public tickets more frequently. So in case we move there are some topics to be discussed and I would like to start with a couple of them right now.
Tickets:
Redmine has a global linear sequence of ticket numbers. If we move from many tracs to a single redmine we can either:
* not import tickets
* only import from one project
* deal with changing ticket numbers
In terms of installations the GMR trac is broken in regard to tickets, there are some for SDR that are probably not being fixed anytime soon, baseband might be relevant and OpenBSC is unlikely to be relevant. I don't think we have ever used ticket reference in OpenBSC commit messages so in terms of OpenBSC having changing ticket numbers would not be a big deal. E.g. we could add a custom field with the old trac number?
Wiki:
We have external references that should be redirected to the new place. Is there any way besides maintaining a list in the apache2/nginx configuration and making redirects as we find broken references? Can we proactively manage this? Is anybody willing to come up with a script and nginx configuration for doing this?
kind regards
holger
If would be nice to have a newer official release available; installation
using the package manager on many Linux distros gets a two year old
librtlsdr that's missing the rtlsdr_set_tuner_bandwidth function (added
about nine months ago), as well as, other nice updates and fixes.
cheers,
joe
Hello,
When I use heatmap.py with output from rtl_power I get regularly spaced
vertical lines that do not appear to be related to any signal. They
look they like repeat at the dongle bandwidth (2048000Hz in this case).
The crop option for rtl_power reduces the presence but I am not sure f
that is intended by that option. Even at -c of 70% they are still there
(see attachment).
Is this because of small bin width? If I use a larger bin (32k) they
are still there. In this case there is no frequency legend along top so
can't compare if they happen more often.
Are these lines to be expected?
John
After pulling gr-fosphor `master` today and compiling against the latest
GNURadio, I noticed that it failed when attempting to link against
libgnuradio, due to missing pmt symbols. The attached one-line patch fixes
the issue, but I imagine would break compilation against older GNURadio
releases.
If there is a better way for me to submit this patch, please let me know.
I had previously emailed one of the gr-fosphor developers with a separate
issue regarding libpng issues out of ignorance of this mailing list. I
don't want to disturb you developers any more than need be, so if there is
a better forum than this for patches/pull requests, I am more than happy to
use it.
-E
Hi there,
In debian, sdrangelove is having some build issues on mipsel [0].
At first, there was an issue regarding the '-msse2' switch.
If I delete the switch, then another build error happens:
======== 8< ========
[...]
[ 21%] Building CXX object CMakeFiles/sdrbase.dir/sdrbase/dsp/interpolator.cpp.o
/usr/bin/c++ -DQT_CORE_LIB -DQT_GUI_LIB -DQT_MULTIMEDIA_LIB
-DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB
-DUSE_FFTW -Dsdrangelove_EXPORTS -g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG
-fPIC -isystem /usr/include/mipsel-linux-gnu/qt5 -isystem
/usr/include/mipsel-linux-gnu/qt5/QtCore -isystem
/usr/lib/mipsel-linux-gnu/qt5/mkspecs/linux-g++ -isystem
/usr/include/mipsel-linux-gnu/qt5/QtWidgets -isystem
/usr/include/mipsel-linux-gnu/qt5/QtGui -isystem
/usr/include/mipsel-linux-gnu/qt5/QtOpenGL -isystem
/usr/include/mipsel-linux-gnu/qt5/QtMultimedia -isystem
/usr/include/mipsel-linux-gnu/qt5/QtNetwork
-I/tmp/buildd/sdrangelove-0.0.1.20140824/obj-mipsel-linux-gnu
-I/tmp/buildd/sdrangelove-0.0.1.20140824/include
-I/tmp/buildd/sdrangelove-0.0.1.20140824/include-gpl -fPIC -o
CMakeFiles/sdrbase.dir/sdrbase/dsp/interpolator.cpp.o -c
/tmp/buildd/sdrangelove-0.0.1.20140824/sdrbase/dsp/interpolator.cpp
In file included from
/tmp/buildd/sdrangelove-0.0.1.20140824/sdrbase/dsp/interpolator.cpp:4:0:
/tmp/buildd/sdrangelove-0.0.1.20140824/include-gpl/dsp/interpolator.h:4:23:
fatal error: immintrin.h: No such file or directory
#include <immintrin.h>
^
compilation terminated.
[...]
======== 8< ========
Do you have any hint for this?
Thanks, best regards.
PS: Please keep me in CC, i'm not subscribed.
[0] https://buildd.debian.org/status/fetch.php?pkg=sdrangelove&arch=mipsel&ver=…
--
Arturo Borrero González
Hey all,
I've been looking into a seg fault bug appearing after asynchronous reads,
and I wanted to put forward my thoughts, and a potential solution, perhaps
for the official release.
I looked into the C source code and have ultimately determined that problem
lies in the rtlsdr_read_async function in librtlsdr.c, which usually (if
not always) returns a -5. I've traced this error back to the
libusb_cancel_transfer function.
My proposed solution is to change the following condition, "if (r < 0)" to
"if (r < 0 && r != LIBUSB_ERROR_NOT_FOUND)".
Why? It's been noted that the new transfer status from the
libusb_cancel_transfer function does not propagate immediately (and to be
honest, I'm not sure when exactly it propagates). As it is now, if the
function returns successfully (r=0), the function runs through the while
loop again, and checks all the functions to see if they are cancelled. If
not, (i.e. the status hasn't propagated) the libusb_cancel_transfer
function is called again, but this time it returns LIBUSB_ERROR_NOT_FOUND,
which according to the function description in the libusb documentation
means "the transfer is not in progress, already complete, or already
cancelled" and is treated as an error. This does not sound to me like an
error, but something that can be ignored to give time for the already
"cancelled" signal to obtain the "CANCELED" status.
I've implemented the change personally, and everything seems to work fine.
I don't know if others have seen the same seg fault problem I have, but
this seems to be a working, minimal solution. Let me know if I'm
interpreting the "transfer is not in progress, already complete, or already
cancelled" wrong, since I don't want to ignore any actual problems.
Thanks,
Eric Jesse
AMDG
Hi,
I just started experimenting with rtl-fm with a DVB-T stick and a
raspberry pi 2. It's really very simple to use but I currently have a
problem by setting a frequency in NBFM mode. When I slightly shifts
the frequency of the true frequency , it appears intermodulation with
DC spike even with the dc -E parameters and offset -E ??? The problem
does not exist with automatic gain. IQ balance dont work with a fixed
gain (ex -g 30) or i made mistake in my command line ??? Have you ever
encountered this problem?
Thanks,
Arnaud
F6GNJ
somebody sending pull requests to a mirror of the official repository...
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)