Anyway, if you have a device tree "compatible=uio" definition for any node
in any device tree. It seems that udev rule will hammer the crap out of the
system until the udev rule can actually do what it wants to.
On Thu, Apr 21, 2016 at 9:05 PM, William Hermans <yyrk...@gmail.com> wrote:
> @Robert,
>
> I think I found the answer to your question. From a text file based on
> something another person on these forums was discussing with me . . .
>
> # put in /etc/modprobe.d/uio.conf
> #
> # make driver match on compatible = "uio";
> options uio_pdrv_genirq of_id=uio
>
>
> # put in /etc/udev/rules.d/uio.rules
> #
> # create named symlink to locate the device easily
> # (assumes your kernel is new enough to have of_node symlinks in sysfs)
> SUBSYSTEM=="uio", SYMLINK+="uio/%s{device/of_node/uio-alias}"
> #
> # give some group access rights (adjust as needed)
> SUBSYSTEM=="uio", GROUP="users", MODE="0660"
>
> So this was in relation to setting up a UIO ADC driver, and was pasted by
> this same person as something for me to experiment with. Anyway this file I
> have was created 11-19-2015, which is a pretty good indication of the date
> when the discussion took place.
>
> On Thu, Apr 21, 2016 at 8:25 PM, Robert Nelson <robertcnel...@gmail.com>
> wrote:
>
>>
>>
>> On Thu, Apr 21, 2016 at 10:04 PM, Charles Steinkuehler <
>> char...@steinkuehler.net> wrote:
>>
>>> On 4/21/2016 9:43 PM, Charles Steinkuehler wrote:
>>> > On 4/21/2016 9:37 PM, Robert Nelson wrote:
>>> >>
>>> >> Does the uio_pruss still work if we just nuke that whole udev rule??
>>> >
>>> > Testing....
>>>
>>
>> Thanks for testing Charles!
>>
>>
>>>
>>> Commenting the first line (with SYMLINK+=):
>>> ==========
>>> No excessive CPU usage when loading a PRU device-tree overlay.
>>
>>
>>>
>>> Commenting both lines (same as not having a uio.rules file):
>>> ==========
>>> No excessive CPU usage when loading a PRU device-tree overlay
>>>
>>> /dev/uio* permissions change from 0660 to 0600
>>>
>>>
>>> In both instances, I can use the PRU as expected (Machinekit loads and
>>> moves motors).
>>>
>>> I would recommend leaving the permissions rule (the second line) but
>>> comment out the first line (the SYMLINK+ line). Honestly, IMHO there
>>> should be a udev rule that creates a device node that has "pru" or
>>> "pruss" in it somewhere, but since that's not how it was done
>>> previously... ;-)
>>>
>>
>> I'll push the first line commenting change..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYgo--FX%3DLHYob143%2BPvEHw9mid9P3zskQm1qpbAsF_4Gw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/beagleboard/CAOCHtYgo--FX%3DLHYob143%2BPvEHw9mid9P3zskQm1qpbAsF_4Gw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/CALHSORo2yNpR7dJ94gHyLW4f0-UoJ%3D4P6hFX%2BLyhwHMjakGWJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
