| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
| |
I've decided to provide a separate pointer for a raw buffer in case the
library user comes up with a non-RGB332 use case that avoids byte
rearrangement (and copying should be replaced with pulling from the
user's pointer in this case)
|
|
|
|
|
|
|
| |
Some people on the mailing list reported that with older kernels
setting interface 0 altsetting 1 does not work, fall back to the
old behavior in this case for now, while still investigating the
root cause of this problem.
|
|
|
|
|
|
|
|
|
| |
This makes osmo-fl2k work again with Linux 5.5.0-rc6 or later,
as the FL2000 shares the endpoints for interface 0 and 1, which
is forbidden by the USB spec and the Kernel will not ignore this
anymore.
See: https://marc.info/?l=linux-usb&m=157944230213296&w=2
|
|
|
|
| |
Otherwise newer versions of CMake are throwing a warning.
|
|
|
|
|
|
|
|
|
| |
warning: absolute value function ‘fabsf’ given an argument of
type ‘double’ but has parameter of type ‘float’ which may cause
truncation of value
warning: ‘__builtin_strncpy’ specified bound 64 equals destination
size
|
|
|
|
|
| |
This sometimes caused a segfault when terminating
fl2k_tcp.
|
| |
|
|
|
|
|
|
|
| |
This fixes a segfault when exiting, as sometimes it occured that
the USB worker thread completed before the sample worker thread,
and the buffers the latter was still accessing had already been
freed.
|
|
|
|
|
| |
In case of a FIFO that has been closed or a 0 byte file this
will otherwise lead to an endless loop.
|
|
|
|
|
| |
Otherwise the linker will complain when building with
-DCMAKE_BUILD_TYPE=Debug
|
|
|
|
|
|
| |
Related: OS#3203
Signed-off-by: Oliver Smith <osmith@sysmocom.de>
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Linux Kernel has a bug on ARM/ARM64 systems where the USB CMA
memory is incorrectly mapped to userspace, breaking zerocopy.
When the Kernel allocates the memory, it clears it with memset().
If the mapping worked correctly, we should have zeroed out buffers,
if it doesn't, we get random Kernel memory. We now check for this,
and fall back to buffers in userspace if that's the case.
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
|
|
|
| |
Note that the FL2000 only supports I2C transfers with
a fixed length of 4 bytes.
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
|
|
|
|
|
|
| |
according to https://wiki.debian.org/Autoreconf:
...
dh-autoreconf is enabled by default since debhelper compatibility level
10 (and the debhelper package Depends on dh-autoreconf since version
9.20160402). For lower compatibility levels:
* Build-Depend on dh-autoreconf
...
|
|
|
|
| |
... so we can build on anything except unstable + ubuntu 18.04
|
|
|
|
|
|
| |
This allows (among others) to build rtl-sdr nightly packages
for a variety of distributions as part of the network:osmocom:nightly
builds.
|
|
|
|
| |
This patch is taken from the osmo-fl2k debian package.
|
|
|
|
|
|
|
|
|
|
|
| |
This avoids the following compiler warnings when using more recent
versions of libusb:
src/libosmo-fl2k.c:384:2: warning: ‘libusb_set_debug’ is deprecated: Use libusb_set_option instead [-Wdeprecated-declarations]
libusb_set_debug(dev->ctx, 3);
^~~~~~~~~~~~~~~~
Details can be found at https://github.com/libusb/libusb/commit/539f22e2fd916558d11ab9a66f10f461c5593168
|
|
|
|
|
|
| |
Thanks to Ted Yapo for reporting.
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
|
|
| |
Thanks to mot for reporting.
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
|
|
| |
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|
|
Signed-off-by: Steve Markgraf <steve@steve-m.de>
|