On 09.08.2017 22:14, Matthias Urlichs via Owfs-developers wrote:
(b) with an additional DRIVER=="USB" condition.

This is nonsense; the "USB" needs to be lowercase and the field is named
DRIVERS. Sorry about that.

Good news everyone, it works! Marvelous, special thanks to Matthias and to Johan to solve this issue :-)

Only so much, the working rule now looks like (at the moment, might change soon ;-) ):

SUBSYSTEMS=="usb", DRIVERS=="usb", ATTRS{manufacturer}=="FTDI", ATTRS{product}=="FT232R USB UART", ATTRS{serial}=="A800bXHr", GROUP="owsrv", MODE="0664"

This rule results in a node residing in /dev/bus/usb/<n>/<m> which is read and writeable by the group owsrv , in my case it looks at the moment like

/    ls -al /dev/bus/usb/003///
//    ...//
//    crw-rw-r-- 1 root owsrv 189, 261 Aug 10 15:07 006/

owserver then accessess this node without sudo, in ftdi addressing scheme to use direct communication.

BUT more good news, and contrary to my previous statement: "One 'S' too little can make or brake the rule...", it DOES work without all the S's too!

SUBSYSTEM=="usb", DRIVER=="usb", ATTR{manufacturer}=="FTDI", ATTR{product}=="FT232R USB UART", ATTR{serial}=="A800bXHr", GROUP="owsrv", MODE="0664"

The answer for the confusion (on the net) is, that parent devices share attributes, that get the key ATTRS - I will show this in a different post in the future.

Again thanks guys, for your help! But, this isn't over ;-)


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Owfs-developers mailing list

Reply via email to