On Tue, Dec 27, 2016 at 14:03 +0100, Stefan Bruens wrote:
>
> On Dienstag, 27. Dezember 2016 13:02:21 CET Gerhard Sittig wrote:
> > OpenOCD commit a5cff3acd377 adjusted their udev rules, motivated by
> > https://lists.debian.org/debian-devel-announce/2016/11/msg00008.html
> > which recommends switching from
> >
> > MODE="664", GROUP="plugdev"
> >
> > to
> >
> > MODE="660", GROUP="plugdev", TAG+="uaccess"
>
> The openSUSE packages use the uaccess tag since ages, the rules also have
> ENV{ID_MM_DEVICE_IGNORE}="1"
Oh, you bring up (unhappy) memories of the pesky modem manager,
which won't even respect this ignore flag depending on its
version or implementation. Recently I gave up fighting and
uninstalled this stubborn and unwilling piece of software, after
running out of ideas what else to try.
Even if the modem manager finds the "recently discovered modem"
unresponsive, and releases access to the device so that other
software can access it, I still found the device unusable (dazed
and confused, not trying to continue) after the modem manager
talked to it. Unplugging and re-plugging does not help, as the
mm again insists in confusing the device. This was hopeless. :(
Or is it the "cable" provider's fault when they claim they'd be
ACM devices (modems) when they should be CDC (serial ports)? Is
this something Windows motivated(?) like the HID disguise, just
to not have to install some drivers? While generic CDC should be
there out of the box, what exactly is the problem they try to
solve?
After trying several approaches, I got tired of mass-editing many
individual lines, and used to (locally) add some extra rules with
"wider scope" (less specific) that do the MM related adjustment,
and take effect _in addition to_ the individual rules with
specific VID/PID that adjust the permissions and optionally
symlink the /dev entry.
And I have to admit that I never bothered looking into rule file
names and their ordering, except for doing every local adjustment
"late" (in the 90ies range), to not interfere with distro stuff.
I never tried to put my local mods "in between" distro provided
rule sets. So my ignorance might have contributed to the
trouble. :)
Thank you for confirming that "uaccess" TAG properties are not
unusual and should be acceptable, at least not harmful.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ask your parents or an adult to help you.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
