46 lines
1.6 KiB
Diff
46 lines
1.6 KiB
Diff
|
From 30632d97d9d68c8202e562f34afae8f8d6e9c377 Mon Sep 17 00:00:00 2001
|
||
|
|
From: Kay Sievers <kay@vrfy.org>
|
||
|
|
Date: Tue, 15 Jul 2014 17:35:53 +0200
|
||
|
|
Subject: [PATCH] rules: uaccess - add ID_SOFTWARE_RADIO
|
||
|
|
|
||
|
|
On Tue, Jul 15, 2014 at 1:52 PM, Alick Zhao <alick9188@gmail.com> 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 is.
|
||
|
|
>>
|
||
|
|
>> What exactly is the device or subsystem you want to make accessible to
|
||
|
|
>> locally logged-in users only?
|
||
|
|
>
|
||
|
|
> Initially it is bladeRF, but many more are of interest: USRP, rtl-sdr,
|
||
|
|
> HackRF, ... [1]
|
||
|
|
>
|
||
|
|
> I agree an administrator might not know what SDR is, since it is
|
||
|
|
> currently still not widely known, and makes sense only for amateurs
|
||
|
|
> and researchers. But as a SDR fan, I see many new SDR peripherals
|
||
|
|
> are created recently, and expect to see more. So a generic ID seems
|
||
|
|
> reasonable to me.
|
||
|
|
>
|
||
|
|
> [1] http://en.wikipedia.org/wiki/List_of_software-defined_radios
|
||
|
|
---
|
||
|
|
src/login/70-uaccess.rules | 3 +++
|
||
|
|
1 file changed, 3 insertions(+)
|
||
|
|
|
||
|
|
diff --git src/login/70-uaccess.rules src/login/70-uaccess.rules
|
||
|
|
index 57f619d..694df2c 100644
|
||
|
|
--- src/login/70-uaccess.rules
|
||
|
|
+++ src/login/70-uaccess.rules
|
||
|
|
@@ -72,4 +72,7 @@ ENV{DDC_DEVICE}=="?*", TAG+="uaccess"
|
||
|
|
# media player raw devices (for user-mode drivers, Android SDK, etc.)
|
||
|
|
SUBSYSTEM=="usb", ENV{ID_MEDIA_PLAYER}=="?*", TAG+="uaccess"
|
||
|
|
|
||
|
|
+# software-defined radio communication devices
|
||
|
|
+ENV{ID_SOFTWARE_RADIO}=="?*", TAG+="uaccess"
|
||
|
|
+
|
||
|
|
LABEL="uaccess_end"
|
||
|
|
--
|
||
|
|
1.7.9.2
|
||
|
|
|