Commit Graph
17 Commits
Author SHA1 Message Date
AsciiWolf 0125be8733 hwdb: add SDRplay devices
Also remove duplicate MiriSDR device that is just a cheap SDRplay RSP1 copy
2025-09-16 09:32:35 +01:00
AsciiWolf bb4c00001d hwdb: add HydraSDR RFOne 2025-09-15 13:22:53 +09:00
AsciiWolf 56347fe7f3 hwdb: add LimeSDR XTRX devices 2025-09-12 06:46:55 +09:00
AsciiWolf 69442f94b5 hwdb: add missing Ettus Research B200 rule
https://github.com/EttusResearch/uhd/blob/master/host/utils/uhd-usrp.rules#L18

Not sure why it was missing.
2025-09-11 18:41:26 +01:00
AsciiWolf 11c58b6774 hwdb: add MiriSDR MSi2500 devices 2025-09-11 09:58:49 +09:00
AsciiWolf c61bdd79ef hwdb: add more devices
- FUNcube Dongle Pro
- Great Scott Gadgets HackRF
- Microtelecom Perseus
2025-09-11 08:44:48 +09:00
AsciiWolf 8fadcd15d3 hwdb: add Airspy devices 2025-09-11 07:27:07 +09:00
AsciiWolf e8628ddb78 hwdb: sort SDR devices by vendor name 2025-08-25 13:42:09 +01:00
Yu Watanabe c2fcfda20f hwdb: merge entries for Ettus Research B200
Follow-up for 9dad00ef94.
2025-05-24 01:57:12 +09:00
AsciiWolf f6f8c6e9fd hwdb: add RTL-SDR devices 2025-05-24 00:11:21 +09:00
AsciiWolf 9dad00ef94 hwdb: add Ettus Research SDR devices 2025-05-23 12:15:12 +01:00
AsciiWolf b2ef1818e6 hwdb: add missing PLUTO SDR vendor name 2025-05-16 19:46:11 +09:00
Yu Watanabe abbdc33bca hwdb: add PLUTO SDR (#37471)
The goal of this PR is to replace the rules in
https://github.com/analogdevicesinc/plutosdr-fw/commit/76aa80a6d86f7b3b2c0fe83cca51f351991ee852.

The original rules file have some rules for a device that is now
deprecated and so, are not part of this change. AFAIU, 'plugdev' is also
a thing of the past and we now use 'uaccess' which should be given to
all ID_SOFTWARE_RADIO devices. So yeah, hopefully what I have here is
equivalent to the orginal .rules.

The request for this was done here:
https://github.com/analogdevicesinc/plutosdr-fw/issues/101
2025-05-15 20:19:09 +09:00
Nuno Sá ab8e0c6c7c hwdb: add Analog Devices PLUTO SDR
Add hwdb entries for ADI PLUTO. Note that when in DFU (Device Firmware
mode) mode, the pid is different. Thus, the two entries.

We also want to make sure that no AT commands are sent to us and so we
set 'ID_MM_DEVICE_IGNORE=1'.
2025-05-15 09:46:16 +01:00
Zbigniew Jędrzejewski-Szmek 9282a85ed7 hwdb: say that settings can be also set to 0
We recommend that users create overriddes. This creates the problem that there
is no syntax to unset a property. Thus, the user needs to just set the property
to "something else" in the override file. But then the blurb saying that
"VAR=1" (or "VAR=0" in some cases) is the only allowed value can be confusing.
Say that both 0 and 1 can be set, since this documentation is also intended
for end users.

In our files, we generally don't want the override values anywhere. But we
have a test which checks the rvalue, which should be enough.
2025-05-14 18:08:26 +02:00
Zbigniew Jędrzejewski-Szmek 97f7b74f97 hwdb.d: update/expand boilerplate on various hwdb files
We don't want to encourage people to copy the whole files. The
boilerplate text that recommends an override file rather than a
full copy appeared first in 0213a26f65,
but was added in other places in 57bb707d48.

Directly inspired by 951e8cb060, but
the wrong boilerplate was added in other places too.
2025-05-14 18:08:26 +02:00
Ryan Thompson 951e8cb060 hwdb: add bladeRF SDR devices
Add hwdb entries for bladeRF 1.x, legacy 1.x, and 2.0 micro devices to
enable non-root access through preexisting ID_SOFTWARE_RADIO tag.

References #20561
2025-05-13 08:09:55 -05:00