On Fri, 5 Apr 2013, Sebastian Cabrera wrote:
> It's the first request. Even If i fire them up directly it works on the
> second try..no matter how long i wait.
>
> I came through something else when flipping patches for UDEV on your
> mailinglist that Adam Williamson mentioned:
>
> I'll try follow up with a patch that drastically cleans up the udev
> rules file - since you can use ranges for device IDs, we should be able
> to make it, like, three lines long. Something like:
>
> SUBSYSTEM=="usb", ATTR{idVendor}=="046d", ATTR{idProduct}=="c1[1-4][0-9a-f]",
> ENV{ID_REMOTE_CONTROL}="1"
>
> plus a line for the one device with the old vendor ID. This would
> obviate the need for the 'neat trick' entirely. This is also a
> suggestion from Kay, so credit to him.
>
> I tried that and it works for me.
>
> SYSFS{idVendor}=="0400", SYSFS{idProduct}=="c359", MODE="0660",
> GROUP="dialout"
> SYSFS{idVendor}=="046d", SYSFS{idProduct}=="c1[1-4][0-9a-f]", MODE="0660",
> GROUP="dialout"
So, you're saying that with these simplified udev rules, you don't see the
problem where concordance fails to talk to the remote on the first try?
Or just that they work?
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
