On Tue, Jul 15, 2014 at 5:09 AM, Alick Zhao alick9...@gmail.com wrote:
On 07/15/2014 08:03 AM, Kay Sievers wrote:
So is it possible to add ID_SDR_HW in the 70-uaccess.rules file?
It could be done. Whether systemd is the best place to keep the rules
for SDR depends on whether there's a
On 07/15/2014 04:10 PM, Kay Sievers wrote:
On Tue, Jul 15, 2014 at 5:09 AM, Alick Zhao alick9...@gmail.com wrote:
On 07/15/2014 08:03 AM, Kay Sievers wrote:
So is it possible to add ID_SDR_HW in the 70-uaccess.rules file?
It could be done. Whether systemd is the best place to keep the rules
On Tue, Jul 15, 2014 at 1:52 PM, Alick Zhao alick9...@gmail.com wrote:
On 07/15/2014 04:10 PM, Kay Sievers wrote:
So maybe ID_SOFTWARE_RADIO ?
Hmm, SDR is more a term for a generic technology than for a device
class. To me it does not really sound like an administrator would know
what this
Hi all,
I am recently playing with software
defined radio (SDR) hardwares (USRP, bladeRF, etc.),
and come across the plugdev group issue. It seems the best way is to
write a local rule
saying something like: [1]
SUBSYSTEM==usb, ENV{DEVTYPE}==usb_device, \
ATTRS{idVendor}==,
On Mon, Jul 14, 2014 at 07:40:10PM +0800, Alick Zhao wrote:
Hi all,
I am recently playing with software
defined radio (SDR) hardwares (USRP, bladeRF, etc.),
and come across the plugdev group issue. It seems the best way is to
write a local rule
saying something like: [1]
On Tue, Jul 15, 2014 at 1:50 AM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Mon, Jul 14, 2014 at 07:40:10PM +0800, Alick Zhao wrote:
Hi all,
I am recently playing with software
defined radio (SDR) hardwares (USRP, bladeRF, etc.),
and come across the plugdev group issue. It seems
On 07/15/2014 08:03 AM, Kay Sievers wrote:
So is it possible to add ID_SDR_HW in the 70-uaccess.rules file?
It could be done. Whether systemd is the best place to keep the rules
for SDR depends on whether there's a better project, like sane for
scanners,
etc.
You may suggest a
