<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Am 26.08.2015 um 20:13 schrieb Bert
Freudenberg:<br>
</div>
<blockquote
cite="mid:EA1FCEDA-0D0C-4A20-9C0A-C674E939C1F3@freudenbergs.de"
type="cite">
<pre wrap=""> </pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">On 26.08.2015, at 19:54, tim Rowledge <a class="moz-txt-link-rfc2396E" href="mailto:tim@rowledge.org"><tim@rowledge.org></a> wrote:
On 26-08-2015, at 10:37 AM, Bert Freudenberg <a class="moz-txt-link-rfc2396E" href="mailto:bert@freudenbergs.de"><bert@freudenbergs.de></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Otherwise I’d go for a lightweight plugin solution using direct IO:
<a class="moz-txt-link-freetext" href="http://elinux.org/RPi_GPIO_Code_Samples#Direct_register_access">http://elinux.org/RPi_GPIO_Code_Samples#Direct_register_access</a>
Advantage (besides being most efficient) is that there are no dependencies at all, and it does look pretty trivial.
</pre>
</blockquote>
<pre wrap="">
I’m not 100% sure but I think that approach requires sudo etc.
</pre>
</blockquote>
<pre wrap="">
How does WiringPi get around that?</pre>
</blockquote>
If it accesses the registers directly via mem-mapped access to I/O
space, it has to run as root, there's no way around it.<br>
A socket-based solution is probably cleanest as it keeps the
critical code that runs with elevated privs reasonably small.<br>
Any other IPC mechanism might do just as well (Don't know whether
there is a significant difference, though).<br>
<br>
Cheers,<br>
Hans-Martin<br>
</body>
</html>