[PATCH] Change RTEMS_API from 5.0 to 5

This fixes the legacy Makefile based build system which expects RTEMS_API to be identical to the tool chain version. Update #3220. --- aclocal/version.m4| 2 +- c/src/aclocal/version.m4 | 2 +- cpukit/aclocal/version.m4 | 2 +- testsuites/aclocal/version.m4 | 2 +- 4 files ch

Re: [PATCH 09/10] libbsd.txt: Describe current state of WLAN.

Am 10.11.2017 um 02:04 schrieb Chris Johns: > On 09/11/2017 19:17, Christian Mauderer wrote: >> Am 09.11.2017 um 09:03 schrieb Chris Johns: >>> On 09/11/2017 17:41, Christian Mauderer wrote: currently there is still no rc.conf support. I took a look at it and found out that I can't d

Re: [PATCH] Upgrade to 5.0.0

On 09/11/17 23:52, Joel Sherrill wrote: My question about the version number went unanswered. Is this the point were we are switching to two digit versions? This thread has 5.0.0 in the title (3 digits, no change in style)  but the current tools are "*-rtems5" which implies two digit release nu

Re: [rtems-tools commit] Add tools/5 patches

On 10/11/17 01:14, Chris Johns wrote: On 09/11/2017 19:16, Sebastian Huber wrote: Module:rtems-tools Branch:master Commit:2da13568ddc41fdeb6e8ddf067bd550bb8753bd8 Changeset: http://git.rtems.org/rtems-tools/commit/?id=2da13568ddc41fdeb6e8ddf067bd550bb8753bd8 Author:Sebastian Hu

Re: [PATCH 09/10] libbsd.txt: Describe current state of WLAN.

On 09/11/2017 19:17, Christian Mauderer wrote: > Am 09.11.2017 um 09:03 schrieb Chris Johns: >> On 09/11/2017 17:41, Christian Mauderer wrote: >>> >>> currently there is still no rc.conf support. I took a look at it and >>> found out that I can't do it in the scope of the project. Therefore I >>> o

Re: [rtems-tools commit] Add tools/5 patches

On 09/11/2017 19:16, Sebastian Huber wrote: > Module:rtems-tools > Branch:master > Commit:2da13568ddc41fdeb6e8ddf067bd550bb8753bd8 > Changeset: > http://git.rtems.org/rtems-tools/commit/?id=2da13568ddc41fdeb6e8ddf067bd550bb8753bd8 >> Author:Sebastian Huber > Date: Thu Nov 9

Re: [PATCH] Upgrade to 5.0.0

On Thu, Nov 9, 2017 at 4:58 PM, Chris Johns wrote: > On 10/11/2017 03:45, Joel Sherrill wrote: > > > > Just to be clear, we won't have a 5.0.0 release, will we? Are we also > going to > > the two digit release numbers? > > No. The wiki page had 'minor release dot number' which was not that clear

Re: [PATCH] Upgrade to 5.0.0

On 10/11/2017 03:45, Joel Sherrill wrote: > > Just to be clear, we won't have a 5.0.0 release, will we? Are we also going > to > the two digit release numbers? No. The wiki page had 'minor release dot number' which was not that clear. I have updated the page to have 'version dot release number'

Re: [PATCH] Upgrade to 5.0.0

On Thu, Nov 9, 2017 at 4:47 PM, Chris Johns wrote: > On 09/11/2017 17:24, Sebastian Huber wrote: > >> 2. Documentation website repo. Easy. > > > > I don't know how to do this. > > > > https://git.rtems.org/chrisj/rtems-admin.git/ > > >> 3. Release procedure repo. Easy. > > > > Do we really need a

Re: [PATCH] Upgrade to 5.0.0

On 09/11/2017 17:24, Sebastian Huber wrote: >> 2. Documentation website repo. Easy. > > I don't know how to do this. > https://git.rtems.org/chrisj/rtems-admin.git/ >> 3. Release procedure repo. Easy. > > Do we really need another repo? Could we please place this to the tools or > RTEMS. >

Re: [PATCH] Upgrade to 5.0.0

On Thu, Nov 9, 2017 at 8:01 AM, Sebastian Huber wrote: > On 09/11/17 14:58, Joel Sherrill wrote: > >> >> 5. Trac wiki. Medium(?). A wiki search of 4.12 gives 21 hits. >> >> >> This is probably the most important area to fix: >> >> https://devel.rtems.org/wiki/Release >>

Re: 3rd party package build system

Hi all, any news on this? Managed to run SOEM on qemu with some help. It was on an arm guest and successfully talked to 3 slaves. I will try to push the SOEM changes upstream as well this week. Cheers, Niko. On Tue, Sep 19, 2017 at 10:08 AM, Nicolas Tsiogkas wrote: > Hi, > > I made the req

Re: [PATCH] Upgrade to 5.0.0

On 09/11/17 14:58, Joel Sherrill wrote: 5. Trac wiki. Medium(?). A wiki search of 4.12 gives 21 hits. This is probably the most important area to fix: https://devel.rtems.org/wiki/Release I will do this today. 6. rtems.

Re: [PATCH] Upgrade to 5.0.0

On Nov 9, 2017 12:24 AM, "Sebastian Huber" < sebastian.hu...@embedded-brains.de> wrote: On 09/11/17 05:58, Chris Johns wrote: > On 08/11/2017 23:29, Sebastian Huber wrote: > >> I can build RTEMS with the updated RTEMS tools and RSB (patches sent >> today). I >> plan to commit this tomorrow. With

[PATCH] rtemsbsd: Remove arc4random support functions.

From: Christian Mauderer These are now provided by the BSP. --- rtemsbsd/rtems/rtems-kernel-init.c | 12 1 file changed, 12 deletions(-) diff --git a/rtemsbsd/rtems/rtems-kernel-init.c b/rtemsbsd/rtems/rtems-kernel-init.c index 8432d5db4dd..1336e598ac4 100644 --- a/rtemsbsd/rtems/

[PATCH 2/4] getentropy: Add cpu counter based implementation.

From: Christian Mauderer --- c/src/lib/libbsp/arm/altera-cyclone-v/Makefile.am | 1 + c/src/lib/libbsp/arm/atsam/Makefile.am | 1 + c/src/lib/libbsp/arm/beagle/Makefile.am| 1 + c/src/lib/libbsp/arm/csb336/Makefile.am| 1 + c/src/lib/libbsp/arm/csb337/Mak

Move arc4random support functions from libbsd to RTEMS

Moving the getentropy() and _arc4random_getentropy_fail() from libbsd to RTEMS makes it easier to implement hardware specific entropy sources. Beneath that it allows to use arc4random without libbsd. Note that this consists of two patch sets: One for RTEMS and one for libbsd. Kind regards Christ

[PATCH 4/4] bsp/atsam: Use TRNG for getentropy.

From: Christian Mauderer --- c/src/lib/libbsp/arm/atsam/Makefile.am | 4 +- .../libbsp/arm/atsam/entropy/getentropy_atsam.c| 61 ++ 2 files changed, 64 insertions(+), 1 deletion(-) create mode 100644 c/src/lib/libbsp/arm/atsam/entropy/getentropy_atsam.c dif

[PATCH 1/4] cpukit: Add _arc4random_getentropy_fail.

From: Christian Mauderer Add a default implementation of _arc4random_getentropy_fail with an internal error. --- cpukit/libcsupport/Makefile.am | 3 ++- cpukit/libcsupport/src/arc4random_getentropy_fail.c | 21 + cpukit/sapi/src/interrtext.c

[PATCH 3/4] getentropy: Add test.

From: Christian Mauderer --- testsuites/libtests/Makefile.am | 1 + testsuites/libtests/configure.ac | 1 + testsuites/libtests/random01/Makefile.am | 19 ++ testsuites/libtests/random01/init.c | 105 ++ testsuites/libtests/random01/

Re: New "RTEMS Contributor Guide"

On Nov 9, 2017 4:00 AM, "Sebastian Huber" < sebastian.hu...@embedded-brains.de> wrote: On 09/11/17 05:48, Chris Johns wrote: > On 08/11/2017 20:33, Sebastian Huber wrote: > >> Hello, >> >> I would like to merge the "RTEMS BSP and Driver Guide", the "RTEMS Porting >> Guide", parts of the "RTEMS CP

Re: New "RTEMS Contributor Guide"

On 09/11/17 05:48, Chris Johns wrote: On 08/11/2017 20:33, Sebastian Huber wrote: Hello, I would like to merge the "RTEMS BSP and Driver Guide", the "RTEMS Porting Guide", parts of the "RTEMS CPU Architecture Supplement", the https://devel.rtems.org/wiki/Developer/Coding/Conventions and the ht

Re: [PATCH 09/10] libbsd.txt: Describe current state of WLAN.

Am 09.11.2017 um 09:17 schrieb Christian Mauderer: > Am 09.11.2017 um 09:03 schrieb Chris Johns: >> On 09/11/2017 17:41, Christian Mauderer wrote: >>> >>> currently there is still no rc.conf support. I took a look at it and >>> found out that I can't do it in the scope of the project. Therefore I >

Re: [PATCH] Upgrade to 5.0.0

I updated everything that I know of and I have permission to change. Open is: https://devel.rtems.org/ticket/3220 5. Documentation website repo. Easy. 6. Release procedure repo. Easy. 9.rtems.org website. That needs Joel. 10. Make announcement on the devel and user mailing list Something el

Re: [PATCH 09/10] libbsd.txt: Describe current state of WLAN.

Am 09.11.2017 um 09:03 schrieb Chris Johns: > On 09/11/2017 17:41, Christian Mauderer wrote: >> >> currently there is still no rc.conf support. I took a look at it and >> found out that I can't do it in the scope of the project. Therefore I >> only added a note regarding this in the "known restrict

Re: [PATCH 09/10] libbsd.txt: Describe current state of WLAN.

On 09/11/2017 17:41, Christian Mauderer wrote: > > currently there is still no rc.conf support. I took a look at it and > found out that I can't do it in the scope of the project. Therefore I > only added a note regarding this in the "known restrictions". Hmmm. > In FreeBSD, the creation of such