Hi Jason!

We already had such questions regarding upstream Debian four years ago
in 2014. I'm still waiting for your answers.

And you moved my project page

https://beagleboard.org/p/tjfr-wordpress-com/libpruio-0-2-fast-and-easy-d-a-i-o-b9f5c8

from wordpress.com to hackster.io, without asking for my agreement.
More than six month I tried to get back access to my own webside,
before I gave up. I'm still not able to update the informations on that
page.

So why should I answer your questions now? OK, other readers may be
interested in that topics as well and I wont operate at your level:

Am Donnerstag, 20. September 2018 18:14:53 UTC+2 schrieb Jason Kridner:
>
> Few feature queries:
>
> Does the current version support remote proc? 
>

Does rproc support libpruio requirements? rproc is designed for
entertainment: for playing music or for simple data logging tasks. In
contrast libpruio targets hard realtime requirements for closed loop
controllers. The rpmsg methods are simply too slow for libpruio.


> Does it require superuser/root execution?
>

Please read the descriptions again. It depends on the need for
pinmuxing and the system configuration. No pinmuxing -> no root
execution. In case of pinmuxing several methods are supported:
config-pin, universal device trees or LKM. The device tree solutions
(including config-pin) need root privileges. In contrast the new LKM
solution provides single source pinmuxing access from user space for
all members of system user group 'pruio'.

>
> Is it in the main rcn-ee package feeds? 
>
> Thought about getting into upstream Debian?
>

libpruio is a hardware driver for AM335[89] CPUs, so we're talking
about Beaglebone Debian. Four years ago I asked for your help. Today I
found my own solution and do not care any longer about that issue. The
project is open source, so feel free to download the source tree and
build your packages for upstream Debian. Or just copy the already built
packages. The users would appreciate that, but they can handle Arend
Lammertinks PPA solution as well.

At least the LKM in upstream Debian would be a great help for the
users, since in case of PPA it needs dkms re-compilation for each
kernel update (and > 30 MB linux-headers in order to re-compile 4 kB
code to a binary that doesn't change). 

>
>
> On Sep 20, 2018, at 6:24 AM, TJF <[email protected] <javascript:>> 
> wrote:
>
>
>
>> <http://www.google.com/url?q=http%3A%2F%2Fusers.freebasic-portal.de%2Ftjf%2FProjekte%2Flibpruio%2Fdoc%2Fhtml%2Fpruio_logo.png&sa=D&sntz=1&usg=AFQjCNGRecvlbz-UcGB92KG6AqZz9Za8Lg>
>>
>
> Major highlights:
>
>    - PRUSS functions exported now
>    - New examples pruss_add (interaction between ARM and PRU) 
>    
> <http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ChaExamples.html#sSecExaPruAdd>
>    - New example pruss_toggle (up to 100 MHz pin toggling) 
>    
> <http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ChaExamples.html#sSecExaPruToggle>
>
> Find
>
>    - more info in the docs, 
>    
> <http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ChaChangelog.html>
>    - the source tree on GitHub <https://github.com/DTJF/libpruio>, and
>    - the install instructions (debian package 
>    
> <http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ChaPreparation.html#SecDebPac>
>  
>    or self-compiled from source tree. 
>    
> <http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ChaPreparation.html#SecSourceTree>
>    ).
>
> -- 
> 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 [email protected] <javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/40e7169e-cd77-4180-9f9f-057ad534e10f%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/beagleboard/40e7169e-cd77-4180-9f9f-057ad534e10f%40googlegroups.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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/76724c23-79da-45cf-8247-3b4c6f3026c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to