Re: [beagleboard] Version 0.6.2 is out now!

[TJF]

Hi Arend!

Am Samstag, 22. September 2018 09:43:13 UTC+2 schrieb Arend Lammertink:
>
> Hi all, 
>
> Great to see the progress being made on getting these packages 
> included in the beaglebone repository. The PPA works and is great to 
> begin with packaging but inclusion in the beaglebone repository is of 
> course much better.


You did a great job with your PPA. And from my point of view it's still 
important for users with older kernel versions. I'd like to keep it running 
up to date, at least for further 6 month, if you don't mind.
 
Best regards.

>
>
>
> On Sat, Sep 22, 2018 at 8:31 AM TJF > 
> wrote: 
> > 
>
> >> Side question, any reason to just not use git master vs the 1.0.5 tag 
> >> from years ago 
> > 
> > 
> > Arend made that package. AFAIK he used that source. 
> > 
>
> Yep. I think it was one of the first packages I made. It's quite a 
> steep learning curve and I only needed it to be able to compile 
> libpruio, so I didn't really care that much about keeping it up to 
> date with the latest 
>
> Best regards, 
>
> Arend. 
>

-- 
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/4f11ff18-2f6b-47c6-b454-d423cbf2a67e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Version 0.6.2 is out now!

[Arend Lammertink]

Hi all,

Great to see the progress being made on getting these packages
included in the beaglebone repository. The PPA works and is great to
begin with packaging but inclusion in the beaglebone repository is of
course much better.


On Sat, Sep 22, 2018 at 8:31 AM TJF  wrote:
>

>> Side question, any reason to just not use git master vs the 1.0.5 tag
>> from years ago
>
>
> Arend made that package. AFAIK he used that source.
>

Yep. I think it was one of the first packages I made. It's quite a
steep learning curve and I only needed it to be able to compile
libpruio, so I didn't really care that much about keeping it up to
date with the latest

Best regards,

Arend.

-- 
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/CAOYv6OPr_jMrie5srF7%3DTvwUH9GeCVL62mEMV0sRm7SnASjCXg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Version 0.6.2 is out now!

[TJF]

Good night!

Am Samstag, 22. September 2018 00:03:06 UTC+2 schrieb RobertCNelson:

> I now have freebasic 1.0.5 available in stretch, it was bootstrap 3 
> times in a standard image and now once on my deb builder.  I'll 
> probally build/bootstrap it two more times tonight (time to run home), 
> to make sure it's fully okay.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

Wow, so much progress in such a short time, awesome!

Side question, any reason to just not use git master vs the 1.0.5 tag 
> from years ago 
>

Arend made that package. AFAIK he used that source.

This is where the fun begin's in a week or two, you really won't need 
> that dkms layer.. 
>

I really don't like that layer and want to get rid of it. But currently I 
see no way to make the LKM available on older kernel versions. Perhaps two 
packages: ...-lkm and ...-lkm-dkms?

Since you're building the FreeBASIC package it seems that you aim to build 
all libpruio packages at your farm. If correct, great news. There'll come a 
pitfall at the end. For the Python binding in package python-pruio a plugin 
from fbdoc is necessary (fbdoc/src/bas/libpy_ctypes.so). This needs the 
fbdoc source tree installed at the same level as libpruio tree and 
'cmakefbc .. && make' executed, ! before ! building the libpruio package.

Regards

-- 
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/559ad95a-05e8-462f-9056-bb78f3af5d63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Version 0.6.2 is out now!

[Robert Nelson]

On Fri, Sep 21, 2018 at 4:41 PM Robert Nelson  wrote:
>
> On Fri, Sep 21, 2018 at 3:51 PM TJF  wrote:
> >
> > Thanks Robert!
> >
> > Working here as well, but
> >
> > $ sudo apt install libpruio-modules
> > Paketlisten werden gelesen... Fertig
> > Abhängigkeitsbaum wird aufgebaut.
> > Statusinformationen werden eingelesen Fertig
> > E: Paket libpruio-modules kann nicht gefunden werden.
> >
> > doesn't work (not found). I have to specify the complete name
> >
> > $ sudo apt install libpruio-modules-4.14.69-ti-r76
> > Paketlisten werden gelesen... Fertig
> > Abhängigkeitsbaum wird aufgebaut.
> > Statusinformationen werden eingelesen Fertig
> > Die folgenden NEUEN Pakete werden installiert:
> >   libpruio-modules-4.14.69-ti-r76
> > 0 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
> > Es müssen 6.000 B an Archiven heruntergeladen werden.
> > Nach dieser Operation werden 26,6 kB Plattenplatz zusätzlich benutzt.
> > Holen:1 http://repos.rcn-ee.com/debian stretch/main armhf 
> > libpruio-modules-4.14.69-ti-r76 armhf 1stretch [6.000 B]
> > Es wurden 6.000 B in 0 s geholt (10,2 kB/s).
> > Vormals nicht ausgewähltes Paket libpruio-modules-4.14.69-ti-r76 wird 
> > gewählt.
> > (Lese Datenbank ... 159470 Dateien und Verzeichnisse sind derzeit 
> > installiert.)
> > Vorbereitung zum Entpacken von 
> > .../libpruio-modules-4.14.69-ti-r76_1stretch_armhf.deb ...
> > Entpacken von libpruio-modules-4.14.69-ti-r76 (1stretch) ...
> > libpruio-modules-4.14.69-ti-r76 (1stretch) wird eingerichtet ...
>
> That is correct, the way my build farm is setup, the module
> (libpruio.ko) is built against a specific kernel release and packaged
> against that tag..
>
> -modules-...deb
>
> > And when I install libpruio-lkm afterwards, DKMS checks first for the linux 
> > headers and then for the kernel module. I've to install linux-heders-`uname 
> > -r` first, before I get the expected result
>
> This is where the fun begin's in a week or two, you really won't need
> that dkms layer..
>
> For debian and ubuntu this repo is going to fill up pretty fast with
> kernel tag's..
>
> https://rcn-ee.net/repos/debian/pool/main/libp/
> https://rcn-ee.net/repos/ubuntu/pool/main/libp/
>
> I've also updated our kernel update script "update_kernel.sh" to be
> aware of the the module:
>
> https://github.com/RobertCNelson/boot-scripts/commit/d837f2b02f44fabe16353fd1226bb1f64e847c93
>
> This sunday's image will automatically have that module pre installed
> after this commit:
>
> https://github.com/beagleboard/image-builder/commit/37c1c4257edd3b70df0d9cefc5aa65d703e681b5
>
> Currently, i'm having fun rebuilding freebasic..
>
> Side question, any reason to just not use git master vs the 1.0.5 tag
> from years ago

I now have freebasic 1.0.5 available in stretch, it was bootstrap 3
times in a standard image and now once on my deb builder.  I'll
probally build/bootstrap it two more times tonight (time to run home),
to make sure it's fully okay..

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/CAOCHtYjGrmK1LZOTfHSebtqMQqFZy%2BqWEKP1rJJ0HqoDRWhLXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Version 0.6.2 is out now!

[Robert Nelson]

On Fri, Sep 21, 2018 at 3:51 PM TJF  wrote:
>
> Thanks Robert!
>
> Working here as well, but
>
> $ sudo apt install libpruio-modules
> Paketlisten werden gelesen... Fertig
> Abhängigkeitsbaum wird aufgebaut.
> Statusinformationen werden eingelesen Fertig
> E: Paket libpruio-modules kann nicht gefunden werden.
>
> doesn't work (not found). I have to specify the complete name
>
> $ sudo apt install libpruio-modules-4.14.69-ti-r76
> Paketlisten werden gelesen... Fertig
> Abhängigkeitsbaum wird aufgebaut.
> Statusinformationen werden eingelesen Fertig
> Die folgenden NEUEN Pakete werden installiert:
>   libpruio-modules-4.14.69-ti-r76
> 0 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
> Es müssen 6.000 B an Archiven heruntergeladen werden.
> Nach dieser Operation werden 26,6 kB Plattenplatz zusätzlich benutzt.
> Holen:1 http://repos.rcn-ee.com/debian stretch/main armhf 
> libpruio-modules-4.14.69-ti-r76 armhf 1stretch [6.000 B]
> Es wurden 6.000 B in 0 s geholt (10,2 kB/s).
> Vormals nicht ausgewähltes Paket libpruio-modules-4.14.69-ti-r76 wird gewählt.
> (Lese Datenbank ... 159470 Dateien und Verzeichnisse sind derzeit 
> installiert.)
> Vorbereitung zum Entpacken von 
> .../libpruio-modules-4.14.69-ti-r76_1stretch_armhf.deb ...
> Entpacken von libpruio-modules-4.14.69-ti-r76 (1stretch) ...
> libpruio-modules-4.14.69-ti-r76 (1stretch) wird eingerichtet ...

That is correct, the way my build farm is setup, the module
(libpruio.ko) is built against a specific kernel release and packaged
against that tag..

-modules-...deb

> And when I install libpruio-lkm afterwards, DKMS checks first for the linux 
> headers and then for the kernel module. I've to install linux-heders-`uname 
> -r` first, before I get the expected result

This is where the fun begin's in a week or two, you really won't need
that dkms layer..

For debian and ubuntu this repo is going to fill up pretty fast with
kernel tag's..

https://rcn-ee.net/repos/debian/pool/main/libp/
https://rcn-ee.net/repos/ubuntu/pool/main/libp/

I've also updated our kernel update script "update_kernel.sh" to be
aware of the the module:

https://github.com/RobertCNelson/boot-scripts/commit/d837f2b02f44fabe16353fd1226bb1f64e847c93

This sunday's image will automatically have that module pre installed
after this commit:

https://github.com/beagleboard/image-builder/commit/37c1c4257edd3b70df0d9cefc5aa65d703e681b5

Currently, i'm having fun rebuilding freebasic..

Side question, any reason to just not use git master vs the 1.0.5 tag
from years ago

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/CAOCHtYgY%3DQ-xWfZdCNic_u589uYgrOvDOpPu6NRobYoqQkX3KQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Version 0.6.2 is out now!

[TJF]

Thanks Robert!

Working here as well, but

$ sudo apt install libpruio-modules
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.   
Statusinformationen werden eingelesen Fertig
E: Paket libpruio-modules kann nicht gefunden werden.

doesn't work (not found). I have to specify the complete name

$ sudo apt install libpruio-modules-4.14.69-ti-r76 
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.   
Statusinformationen werden eingelesen Fertig
Die folgenden NEUEN Pakete werden installiert:
  libpruio-modules-4.14.69-ti-r76
0 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 6.000 B an Archiven heruntergeladen werden.
Nach dieser Operation werden 26,6 kB Plattenplatz zusätzlich benutzt.
Holen:1 http://repos.rcn-ee.com/debian stretch/main armhf 
libpruio-modules-4.14.69-ti-r76 armhf 1stretch [6.000 B]
Es wurden 6.000 B in 0 s geholt (10,2 kB/s). 
Vormals nicht ausgewähltes Paket libpruio-modules-4.14.69-ti-r76 wird gewä
hlt.
(Lese Datenbank ... 159470 Dateien und Verzeichnisse sind derzeit 
installiert.)
Vorbereitung zum Entpacken von .../libpruio-modules-4.14.69-ti-
r76_1stretch_armhf.deb ...
Entpacken von libpruio-modules-4.14.69-ti-r76 (1stretch) ...
libpruio-modules-4.14.69-ti-r76 (1stretch) wird eingerichtet ...

And when I install libpruio-lkm afterwards, DKMS checks first for the linux 
headers and then for the kernel module. I've to install linux-heders-`uname 
-r` first, before I get the expected result

~$ sudo apt install libpruio-lkm
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.   
Statusinformationen werden eingelesen Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr 
benötigt:
  libllvm5.0 libncurses5-dev libtinfo-dev libxpm-dev
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
Die folgenden NEUEN Pakete werden installiert:
  libpruio-lkm
0 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 8.142 B an Archiven heruntergeladen werden.
Nach dieser Operation werden 32,8 kB Plattenplatz zusätzlich benutzt.
Holen:1 http://beagle.tuks.nl/debian jessie/ libpruio-lkm 0.6.2a [8.142 B]
Es wurden 8.142 B in 0 s geholt (33,0 kB/s).
Vormals nicht ausgewähltes Paket libpruio-lkm wird gewählt.
(Lese Datenbank ... 159476 Dateien und Verzeichnisse sind derzeit 
installiert.)
Vorbereitung zum Entpacken von .../libpruio-lkm_0.6.2a_armhf.deb ...
Entpacken von libpruio-lkm (0.6.2a) ...
libpruio-lkm (0.6.2a) wird eingerichtet ...
addgroup: Die Gruppe »pruio« existiert bereits als Systemgruppe. 
Programmende.
Created symlink 
/etc/systemd/system/multi-user.target.wants/libpruio-lkm.service 
→ /lib/systemd/system/libpruio-lkm.service.
Loading new libpruio-lkm-0.6.2a DKMS files...
Building for 4.14.69-ti-r76 4.17.6-armv7-x7
Building initial module for 4.14.69-ti-r76
Done.

libpruio:
Running module version sanity check.

Good news! Module version 0.0 for libpruio.ko
exactly matches what is already found in kernel 4.14.69-ti-r76.
DKMS will not replace this module.
You may override by specifying --force.

depmod..

Backing up initrd.img-4.14.69-ti-r76 to /boot/initrd.img-4.14.69-ti-r76.old-
dkms
Making new initrd.img-4.14.69-ti-r76
(If next boot fails, revert to initrd.img-4.14.69-ti-r76.old-dkms image)
update-initramfs..

DKMS: install completed.
Module build for kernel 4.17.6-armv7-x7 was skipped since the
kernel headers for this kernel does not seem to be installed.

More confusing than helpful for the users :-(

Regards

Am Freitag, 21. September 2018 20:59:25 UTC+2 schrieb RobertCNelson:
>
> On Fri, Sep 21, 2018 at 10:41 AM Robert Nelson  > wrote: 
> > 
> > On Fri, Sep 21, 2018 at 10:37 AM Robert Nelson  > wrote: 
> > >> 
> > >> Frustration subsides immediately when I see some progress. Getting 
> the LKM in to https://github.com/beagleboard/repos would be a great 
> start. The folder you mentioned is related to the project tree and uses 
> variables like PROJ_NAME to fill template files. From my point of view it's 
> better to fetch the source from the libpruio-lkm package. But Robert should 
> know the best solution. The libpruio.ko driver is necessary. The file 
> libpruio-lkm.service can come from package libpruio-lkm, which also adds 
> the 'pruio' system users group. 
> > > 
> > > 
> > > The libpruio.ko module is now wired up into the build process. 
> > > 
> > > https://github.com/rcn-ee/libpruio 
> > > 
> > > I've got 4.14.69-ti-r76 almost ready to be tagged, so this will be the 
> first test shortly today.. 
> > > 
> > > If every works, It should shoot out a 
> "libpruio-modules-4.14.69-ti-r76" deb package. 
> > 
> > and just to be clear, i'm wiring it up for all the am335x kernel 
> "channels"... 
> > 
> > v4.x.y-ti 
> > v4.x.y-rt-ti 
> > v4.x.y-bone 
> > v4.x.y-bone-rt 
>
> The following NEW packages will be installed: 
>   libpruio-modules-4.14.69-ti-r76 ti-sgx-ti335x-modules-4.14.69-ti-r76 

Re: [beagleboard] Version 0.6.2 is out now!

[Robert Nelson]

On Fri, Sep 21, 2018 at 10:41 AM Robert Nelson  wrote:
>
> On Fri, Sep 21, 2018 at 10:37 AM Robert Nelson  
> wrote:
> >>
> >> Frustration subsides immediately when I see some progress. Getting the LKM 
> >> in to https://github.com/beagleboard/repos would be a great start. The 
> >> folder you mentioned is related to the project tree and uses variables 
> >> like PROJ_NAME to fill template files. From my point of view it's better 
> >> to fetch the source from the libpruio-lkm package. But Robert should know 
> >> the best solution. The libpruio.ko driver is necessary. The file 
> >> libpruio-lkm.service can come from package libpruio-lkm, which also adds 
> >> the 'pruio' system users group.
> >
> >
> > The libpruio.ko module is now wired up into the build process.
> >
> > https://github.com/rcn-ee/libpruio
> >
> > I've got 4.14.69-ti-r76 almost ready to be tagged, so this will be the 
> > first test shortly today..
> >
> > If every works, It should shoot out a "libpruio-modules-4.14.69-ti-r76" deb 
> > package.
>
> and just to be clear, i'm wiring it up for all the am335x kernel "channels"...
>
> v4.x.y-ti
> v4.x.y-rt-ti
> v4.x.y-bone
> v4.x.y-bone-rt

The following NEW packages will be installed:
  libpruio-modules-4.14.69-ti-r76 ti-sgx-ti335x-modules-4.14.69-ti-r76
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 116 kB of archives.
After this operation, 465 kB of additional disk space will be used.
Get:1 http://repos.rcn-ee.com/debian stretch/main armhf
libpruio-modules-4.14.69-ti-r76 armhf 1stretch [6,000 B]
Get:2 http://repos.rcn-ee.com/debian stretch/main armhf
ti-sgx-ti335x-modules-4.14.69-ti-r76 armhf 1stretch [110 kB]
Fetched 116 kB in 0s (276 kB/s)
Selecting previously unselected package libpruio-modules-4.14.69-ti-r76.
(Reading database ... 40952 files and directories currently installed.)
Preparing to unpack .../libpruio-modules-4.14.69-ti-r76_1stretch_armhf.deb ...
Unpacking libpruio-modules-4.14.69-ti-r76 (1stretch) ...
Selecting previously unselected package ti-sgx-ti335x-modules-4.14.69-ti-r76.
Preparing to unpack
.../ti-sgx-ti335x-modules-4.14.69-ti-r76_1stretch_armhf.deb ...
Unpacking ti-sgx-ti335x-modules-4.14.69-ti-r76 (1stretch) ...
Setting up ti-sgx-ti335x-modules-4.14.69-ti-r76 (1stretch) ...
Setting up libpruio-modules-4.14.69-ti-r76 (1stretch) ...

debian@beaglebone:~$ sudo modprobe libpruio
[sudo] password for debian:
debian@beaglebone:~$ lsmod | grep uio
libpruio   16384  0
uio_pruss  16384  0
uio_pdrv_genirq16384  0
uio20480  2 uio_pruss,uio_pdrv_genirq

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/CAOCHtYjWjhgDGeNq%2B6rCWzzzaJHOfeeuKEXGDEqVk1%3DYTemYoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Version 0.6.2 is out now!

[Robert Nelson]

On Fri, Sep 21, 2018 at 10:37 AM Robert Nelson  wrote:
>>
>> Frustration subsides immediately when I see some progress. Getting the LKM 
>> in to https://github.com/beagleboard/repos would be a great start. The 
>> folder you mentioned is related to the project tree and uses variables like 
>> PROJ_NAME to fill template files. From my point of view it's better to fetch 
>> the source from the libpruio-lkm package. But Robert should know the best 
>> solution. The libpruio.ko driver is necessary. The file libpruio-lkm.service 
>> can come from package libpruio-lkm, which also adds the 'pruio' system users 
>> group.
>
>
> The libpruio.ko module is now wired up into the build process.
>
> https://github.com/rcn-ee/libpruio
>
> I've got 4.14.69-ti-r76 almost ready to be tagged, so this will be the first 
> test shortly today..
>
> If every works, It should shoot out a "libpruio-modules-4.14.69-ti-r76" deb 
> package.

and just to be clear, i'm wiring it up for all the am335x kernel "channels"...

v4.x.y-ti
v4.x.y-rt-ti
v4.x.y-bone
v4.x.y-bone-rt

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/CAOCHtYi6ZS-ORLNjYCLpyOr7X7gNuOBEi8bfPqrM0e58QB%2Btdg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Version 0.6.2 is out now!

[Robert Nelson]

>
> Frustration subsides immediately when I see some progress. Getting the LKM
> in to https://github.com/beagleboard/repos would be a great start. The
> folder you mentioned is related to the project tree and uses variables like
> PROJ_NAME to fill template files. From my point of view it's better to
> fetch the source from the libpruio-lkm package. But Robert should know the
> best solution. The libpruio.ko driver is necessary. The file
> libpruio-lkm.service can come from package libpruio-lkm, which also adds
> the 'pruio' system users group.
>

The libpruio.ko module is now wired up into the build process.

https://github.com/rcn-ee/libpruio

I've got 4.14.69-ti-r76 almost ready to be tagged, so this will be the
first test shortly today..

If every works, It should shoot out a "libpruio-modules-4.14.69-ti-r76" deb
package.

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/CAOCHtYiyYag1kGpOQwcg7S_mZ0Uz%2BMrPRV2pAZGA9USgzUqHRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Version 0.6.2 is out now!

[TJF]

Hi Jason, thanks for your broad answer.

Now I've a reversed problem: too much text for a non-native speaker :-)

Am Freitag, 21. September 2018 09:51:47 UTC+2 schrieb Jason Kridner:
>
> On Thu, Sep 20, 2018 at 2:26 PM TJF > 
> wrote:
>
>> Hi Jason!
>>
>> We already had such questions regarding upstream Debian four years ago
>> in 2014. I'm still waiting for your answers.
>>
>
> Guess I'll search for it. Found a bit of info on your site, but I'll try 
> to go back and find the queries.
>
> Going back as far as I can, I found 
> https://groups.google.com/d/msg/beagleboard/lzJge-08T9s/HnPTZ82nLCYJ. 
> Looking newer than that, I see a lot of queries, but it seems to me Robert 
> has been pretty good at answering.
>
> If you can provide any hints that will help my search and get you answers, 
> I'd be appreciative.
>

I'm not interested in old answers. Let us focus on current questions.
 

>  
>
>>
>> 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.
>>
>
> There was a mass migration from the old project pages to hackster.io via 
> a script. The main purpose is to give a place for people to discover the 
> projects and point them to the real source for details, rather than 
> actually take the attention away.
>
> BTW, the projects were never on wordpress.com, they were on 
> beagleboard.org, and wordpress.com was simply used as one of many OpenID 
> provider options.
>
> Maintaining the editable pages on beagleboard.org itself had become a 
> logistical nightmare as quality support for OpenID has waned at all the key 
> service providers even as the technology itself had changed. My older 
> support libraries could no longer support the handful of providers that 
> still exist.
>
> I believe hackster.io has a method for offering a recourse, but, 
> fundamentally, this is your information and you just need to be able to 
> control it. Sorry for not keeping that access/control in your clear view. 
> Seems you have found recourse here and now on this forum.
>
> I'm committed to making this right. I'll take it down or replace it with 
> whatever you see fit in regards to your project.
>  
>
>> 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.
>>
>
> Sorry it was so hard to get my attention. I try to make myself available 
> via http://beagleboard.org/about and some people grab my attention at 
> times via #beagle on IRC, but e-mails frequently escape my view are are 
> closer to blind luck if I actually see them. I promise this isn't personal, 
> but I do get several hundred e-mails a day and I try to scan the subject 
> lines as best I can.
>
> This project page can be put in your name if you create a hackster.io 
> account... not sure if that is something you want to do. Again, I wanted it 
> to all be OpenID so that you could maintain your own credentials/identity, 
> but the support has become too hard for it. I will credit you and provide 
> content however you see fit in regards to your project.
>  
>
>>
>> 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:
>>
>
> That seems a bit harsh.
>

After four years of neglect and blocking my project page, what level of 
harshness do you expect?

I didn't want to create a wordpress account, but I did it to make the 
project page.

I didn't want to create a hackster account, but I did it to gain access to 
the project page. Now I get unwanted commercials from hackster, find no way 
to switch it off (it's easy to add a channel, but no way to remove one) and 
still have no access.

Your concepts and communication behavior forces me to waste my time, create 
unwanted accounts and receive commercials. Instead I want to spend my time 
in finding new solutions for the BB.

All I need to know is what to do to update the project page. I created a 
hackster account. I want to login using my GitHub.com/DTJF account. I 
prefer a solution that neither needs cookies nor JavaScript enabled. Can 
you please transfer ownership of the project page to that hackster account?
 

>
> Helping the other readers is indeed the point, so glad we are at least of 
> the same mind in that regard.
>  
>
>>
>>
>> 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.
>>
>
> rproc is really just about putting the kernel in charge of the PRUs, 
> rather than leaving it up to userspace. 

Re: [beagleboard] Version 0.6.2 is out now!

[Jason Kridner]

On Thu, Sep 20, 2018 at 2:26 PM TJF  wrote:

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

Guess I'll search for it. Found a bit of info on your site, but I'll try to
go back and find the queries.

Going back as far as I can, I found
https://groups.google.com/d/msg/beagleboard/lzJge-08T9s/HnPTZ82nLCYJ.
Looking newer than that, I see a lot of queries, but it seems to me Robert
has been pretty good at answering.

If you can provide any hints that will help my search and get you answers,
I'd be appreciative.


>
> 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.
>

There was a mass migration from the old project pages to hackster.io via a
script. The main purpose is to give a place for people to discover the
projects and point them to the real source for details, rather than
actually take the attention away.

BTW, the projects were never on wordpress.com, they were on beagleboard.org,
and wordpress.com was simply used as one of many OpenID provider options.

Maintaining the editable pages on beagleboard.org itself had become a
logistical nightmare as quality support for OpenID has waned at all the key
service providers even as the technology itself had changed. My older
support libraries could no longer support the handful of providers that
still exist.

I believe hackster.io has a method for offering a recourse, but,
fundamentally, this is your information and you just need to be able to
control it. Sorry for not keeping that access/control in your clear view.
Seems you have found recourse here and now on this forum.

I'm committed to making this right. I'll take it down or replace it with
whatever you see fit in regards to your project.


> 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.
>

Sorry it was so hard to get my attention. I try to make myself available
via http://beagleboard.org/about and some people grab my attention at times
via #beagle on IRC, but e-mails frequently escape my view are are closer to
blind luck if I actually see them. I promise this isn't personal, but I do
get several hundred e-mails a day and I try to scan the subject lines as
best I can.

This project page can be put in your name if you create a hackster.io
account... not sure if that is something you want to do. Again, I wanted it
to all be OpenID so that you could maintain your own credentials/identity,
but the support has become too hard for it. I will credit you and provide
content however you see fit in regards to your project.


>
> 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:
>

That seems a bit harsh.

Helping the other readers is indeed the point, so glad we are at least of
the same mind in that regard.


>
>
> 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.
>

rproc is really just about putting the kernel in charge of the PRUs, rather
than leaving it up to userspace. It provides an ELF parser/loader and sysfs
entries for starting/stopping the processor, among other processor
abstractions. Memory (/dev/mem) mapping of PRU shared memories is still
completely possible in an rproc environment. There is no explicit need to
utilize rpmsg. Still, the permissions issues could be a bit different. With
UIO, the memory mapping of the PRU is exposed explicitly for that
peripheral and the permissions on access can be set for just that memory
region. No one has yet created a UIO/memory driver that exposes the PRU
shared memory while running the rproc driver, though nothing should prevent
that.

The Linux upstream maintainers seem to have a preference for rproc which is
why I tend to recommend it. "Just works" is great, but "leverages
community" is also great.


>
>
>> 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 

Re: [beagleboard] Version 0.6.2 is out now!

[TJF]

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 > 
> wrote:
>
>
>
>> 
>>
>
> Major highlights:
>
>- PRUSS functions exported now
>- New examples pruss_add (interaction between ARM and PRU) 
>
> 
>- New example pruss_toggle (up to 100 MHz pin toggling) 
>
> 
>
> Find
>
>- more info in the docs, 
>
> 
>- the source tree on GitHub , and
>- the install instructions (debian package 
>
> 
>  
>or self-compiled from source tree. 
>
> 
>).
>
> -- 
> 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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/40e7169e-cd77-4180-9f9f-057ad534e10f%40googlegroups.com
>  
> 
> .
> 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/76724c23-79da-45cf-8247-3b4c6f3026c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Version 0.6.2 is out now!

[Jason Kridner]

Few feature queries:

Does the current version support remote proc? 

Does it require superuser/root execution?

Is it in the main rcn-ee package feeds? 

Thought about getting into upstream Debian?


> On Sep 20, 2018, at 6:24 AM, TJF  wrote:
> 
> 
> 
> Major highlights:
> PRUSS functions exported now
> New examples pruss_add (interaction between ARM and PRU)
> New example pruss_toggle (up to 100 MHz pin toggling)
> Find
> more info in the docs,
> the source tree on GitHub, and
> the install instructions (debian package or self-compiled from source tree.).
> -- 
> 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/40e7169e-cd77-4180-9f9f-057ad534e10f%40googlegroups.com.
> 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/84B48CED-3D48-40C3-AAF9-482502D03F68%40gmail.com.
For more options, visit https://groups.google.com/d/optout.