[PATCH v5] Chapter-on-need-for-RTEMS-specific-cross-compiler

Removed '-' character and provided definition list format --- user/start/tools.rst | 33 + 1 file changed, 33 insertions(+) diff --git a/user/start/tools.rst b/user/start/tools.rst index c3f039b..1d83062 100644 --- a/user/start/tools.rst +++ b/user/start/tools.rst

Re: rtems-bsp-builder Job Load Calculation

On Fri, Apr 3, 2020 at 6:23 PM Joel Sherrill wrote: > > > On Fri, Apr 3, 2020 at 5:26 PM Chris Johns wrote: > >> On 2020-04-04 07:57, Joel Sherrill wrote: >> > How does rtems-bsp-builder calculate the amount of parallelism to use? >> >> The option is documented here ... >> >> >> https://docs.rte

Re: rtems-bsp-builder Job Load Calculation

On Fri, Apr 3, 2020 at 5:26 PM Chris Johns wrote: > On 2020-04-04 07:57, Joel Sherrill wrote: > > How does rtems-bsp-builder calculate the amount of parallelism to use? > > The option is documented here ... > > > https://docs.rtems.org/branches/master/user/tools/bsp-builder.html#cmdoption-jobs >

Re: [PATCH v1] RTEMS Docs: Add steps for sphinxcontrib-bibtex

On 2020-04-04 05:13, Gedare Bloom wrote: Anyone tell if FreeBSD or openSUSE also need a similar package? I could not find a package called sphinxcontrib-bibtex on FreeBSD. I use the virtualenv method to host sphinx. I find it simpler. Chris ___ dev

[PATCH] common: fix title page

Sphinx changed the default behavior of maketitle. Provide our own rtemsmaketitle command and use it instead. --- common/conf.py| 1 + common/rtemsstyle.sty | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/common/conf.py b/common/conf.py index 97f8dfa..257bc4e 100644 --

[PATCH] common/rtemsstyle.sty: change maketitle to sphinxmaketitle

Sphinx now uses its own sphinxmaketitle command to generate the title page. To create our own title page we can provide our own sphinxmaketitle. --- common/rtemsstyle.sty | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/common/rtemsstyle.sty b/common/rtemsstyle.sty index 15f80b5

Re: rtems-bsp-builder Job Load Calculation

On 2020-04-04 07:57, Joel Sherrill wrote: How does rtems-bsp-builder calculate the amount of parallelism to use? The option is documented here ... https://docs.rtems.org/branches/master/user/tools/bsp-builder.html#cmdoption-jobs and is ... --jobs The jobs options where the format is build

rtems-bsp-builder Job Load Calculation

Hi How does rtems-bsp-builder calculate the amount of parallelism to use? I ask because I have realized that I selected jobs=6/12 on a very beefy machine with 12 cores and 32 GB RAM. The main test machine I use is 8 cores/32 GB RAM. But the slowest ones are old with 4 cores/4 GB RAM. They are hit

Re: Proposal to add rule for nested CPP Directives in RTEMS coding conventions

On Sat, Apr 4, 2020, 1:41 AM Vijay Kumar Banerjee wrote: > > > On Sat, Apr 4, 2020 at 1:22 AM Vaibhav Gupta > wrote: > >> CPP directives like: >> 1) #if >> 2) #ifdef >> 3) #ifndef >> 4) #elif >> 5) #else >> 6) #endif >> >> do form code blocks. Since, they don't make use of brackets, >> as a part

Re: Proposal to add rule for nested CPP Directives in RTEMS coding conventions

On Sat, Apr 4, 2020 at 1:22 AM Vaibhav Gupta wrote: > CPP directives like: > 1) #if > 2) #ifdef > 3) #ifndef > 4) #elif > 5) #else > 6) #endif > > do form code blocks. Since, they don't make use of brackets, > as a part of C language rule, their nested and repeated use > can make the code very ha

Proposal to add rule for nested CPP Directives in RTEMS coding conventions

CPP directives like: 1) #if 2) #ifdef 3) #ifndef 4) #elif 5) #else 6) #endif do form code blocks. Since, they don't make use of brackets, as a part of C language rule, their nested and repeated use can make the code very hard to read. Can even result it spaghetti code. This can be understood by t

Re: [PATCH v11] tests for fenv.h functions

On Sat, Apr 4, 2020, 1:01 AM Gedare Bloom wrote: > On Fri, Apr 3, 2020 at 1:11 PM Vaibhav Gupta > wrote: > > > > IMO we should have a rule for nested CPP directives. > > And also the commenting. It makes the code more readable > > as a part of good coding style. > > > > Specially if the directiv

Re: [PATCH v11] tests for fenv.h functions

On Fri, Apr 3, 2020 at 1:11 PM Vaibhav Gupta wrote: > > IMO we should have a rule for nested CPP directives. > And also the commenting. It makes the code more readable > as a part of good coding style. > > Specially if the directives are nested, because they don't > use brackets, too many opening-

[PATCH v5] Tests for inttype.h methods

--- testsuites/psxtests/psxinttypes01/init.c | 28 +-- .../psxtests/psxinttypes01/psxinttypes01.doc | 10 ++- 2 files changed, 34 insertions(+), 4 deletions(-) diff --git a/testsuites/psxtests/psxinttypes01/init.c b/testsuites/psxtests/psxinttypes01/init.c index 030aa2a

Re: [PATCH v11] tests for fenv.h functions

IMO we should have a rule for nested CPP directives. And also the commenting. It makes the code more readable as a part of good coding style. Specially if the directives are nested, because they don't use brackets, too many opening-closing pair can make the code hard to read. -- Vaibhav Gupta ___

Re: [PATCH v4] Tests for inttype.h methods

On Fri, Apr 3, 2020 at 1:00 PM Eshan Dhawan wrote: > > > > On Sat, Apr 4, 2020 at 12:27 AM Gedare Bloom wrote: >> >> On Fri, Apr 3, 2020 at 12:50 PM Eshan dhawan wrote: >> > >> > --- >> > testsuites/psxtests/psxinttypes01/init.c | 27 --- >> > .../psxtests/psxinttypes01/psx

Re: [PATCH v11] tests for fenv.h functions

> Good advice, Thanks! > although I'm not sure if we have these 2 things in our > conventions yet: nesting CPP conditional blocks, and comments on CPP > conditional blocks? > Well in that case I guess Eshan should re-work on patch and also make changes in wiki. -- Vaibhav Gupta ___

Re: [PATCH v4] Tests for inttype.h methods

On Sat, Apr 4, 2020 at 12:27 AM Gedare Bloom wrote: > On Fri, Apr 3, 2020 at 12:50 PM Eshan dhawan > wrote: > > > > --- > > testsuites/psxtests/psxinttypes01/init.c | 27 --- > > .../psxtests/psxinttypes01/psxinttypes01.doc | 10 ++- > > 2 files changed, 33 insertions(

Re: [PATCH v11] tests for fenv.h functions

On Fri, Apr 3, 2020 at 12:54 PM Gedare Bloom wrote: > > On Fri, Apr 3, 2020 at 12:35 PM Vaibhav Gupta > wrote: > > > > On Fri, 27 Mar 2020 at 22:35, Eshan dhawan wrote: > > > > > > --- > > > testsuites/psxtests/psxfenv01/init.c| 88 - > > > testsuites/psxtests/psxfe

Re: [PATCH v4] Tests for inttype.h methods

On Fri, Apr 3, 2020 at 12:50 PM Eshan dhawan wrote: > > --- > testsuites/psxtests/psxinttypes01/init.c | 27 --- > .../psxtests/psxinttypes01/psxinttypes01.doc | 10 ++- > 2 files changed, 33 insertions(+), 4 deletions(-) > > diff --git a/testsuites/psxtests/psxinttypes0

Re: [PATCH v11] tests for fenv.h functions

On Fri, Apr 3, 2020 at 12:35 PM Vaibhav Gupta wrote: > > On Fri, 27 Mar 2020 at 22:35, Eshan dhawan wrote: > > > > --- > > testsuites/psxtests/psxfenv01/init.c| 88 - > > testsuites/psxtests/psxfenv01/psxfenv01.doc | 9 ++- > > testsuites/psxtests/psxfenv01/psxfenv01

[PATCH v4] Tests for inttype.h methods

--- testsuites/psxtests/psxinttypes01/init.c | 27 --- .../psxtests/psxinttypes01/psxinttypes01.doc | 10 ++- 2 files changed, 33 insertions(+), 4 deletions(-) diff --git a/testsuites/psxtests/psxinttypes01/init.c b/testsuites/psxtests/psxinttypes01/init.c index 030aa2a

Re: [PATCH v11] tests for fenv.h functions

On Fri, 27 Mar 2020 at 22:35, Eshan dhawan wrote: > > --- > testsuites/psxtests/psxfenv01/init.c| 88 - > testsuites/psxtests/psxfenv01/psxfenv01.doc | 9 ++- > testsuites/psxtests/psxfenv01/psxfenv01.scn | 4 - > 3 files changed, 76 insertions(+), 25 deletions(-) >

Re: [PATCH v3] Tests for inttype.h methods

I tested it on the pc386 BSP. Once the style stuff is fixed, it should be OK to push. --joel On Fri, Apr 3, 2020 at 1:07 PM Gedare Bloom wrote: > Couple of formatting problems to fix: > > On Fri, Apr 3, 2020 at 10:53 AM Eshan dhawan > wrote: > > > > --- > > testsuites/psxtests/psxinttypes01/i

Re: [PATCH v1] RTEMS Docs: Add steps for sphinxcontrib-bibtex

Thanks, pushing presently. Anyone tell if FreeBSD or openSUSE also need a similar package? On Fri, Apr 3, 2020 at 12:11 PM Vaibhav Gupta wrote: > > Add step to install sphinxcontrib-bibtex > together with the steps mentioned for ArcLinux, > to install sphinx and dependencies. > > Signed-off-by:

[PATCH v1] RTEMS Docs: Add steps for sphinxcontrib-bibtex

Add step to install sphinxcontrib-bibtex together with the steps mentioned for ArcLinux, to install sphinx and dependencies. Signed-off-by: Vaibhav Gupta --- README.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/README.txt b/README.txt index 9fd2165..ce30505 100644 --- a/README.txt +++

Re: [PATCH v5] Chapter-on-need-for-RTEMS-specific-cross-compiler

On Fri, Apr 3, 2020 at 11:19 AM utkarsh.ra...@gmail.com wrote: > > --- > user/start/tools.rst | 32 > 1 file changed, 32 insertions(+) > > diff --git a/user/start/tools.rst b/user/start/tools.rst > index c3f039b..c1cd141 100644 > --- a/user/start/tools.rst > +++ b

Re: [PATCH v3] Tests for inttype.h methods

Couple of formatting problems to fix: On Fri, Apr 3, 2020 at 10:53 AM Eshan dhawan wrote: > > --- > testsuites/psxtests/psxinttypes01/init.c | 25 --- > .../psxtests/psxinttypes01/psxinttypes01.doc | 10 +++- > 2 files changed, 31 insertions(+), 4 deletions(-) > > diff

[PATCH v5] Chapter-on-need-for-RTEMS-specific-cross-compiler

--- user/start/tools.rst | 32 1 file changed, 32 insertions(+) diff --git a/user/start/tools.rst b/user/start/tools.rst index c3f039b..c1cd141 100644 --- a/user/start/tools.rst +++ b/user/start/tools.rst @@ -76,3 +76,35 @@ source code used. Add ``--verbose``

[PATCH v3] Tests for inttype.h methods

--- testsuites/psxtests/psxinttypes01/init.c | 25 --- .../psxtests/psxinttypes01/psxinttypes01.doc | 10 +++- 2 files changed, 31 insertions(+), 4 deletions(-) diff --git a/testsuites/psxtests/psxinttypes01/init.c b/testsuites/psxtests/psxinttypes01/init.c index 030aa2

Re: [PATCH v4] Chapter-on-need-for-RTEMS-specific-cross-compiler

Oh, forgot that one! I will do the changes. On Fri, Apr 3, 2020 at 9:17 PM Gedare Bloom wrote: > Hi Utkarsh, > > This is almost there, really! The only thing is that you maybe missed > or didn't understand a question from Sebastian, "What about using a > definition list instead of this hand cra

Re: [PATCH] cpukit/rfs: fix typo in header guard

Looks good. On Fri, Apr 3, 2020 at 10:31 AM Gedare Bloom wrote: > --- > cpukit/include/rtems/rfs/rtems-rfs-dir-hash.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/cpukit/include/rtems/rfs/rtems-rfs-dir-hash.h > b/cpukit/include/rtems/rfs/rtems-rfs-dir-hash.h > index

Re: [PATCH v4] Chapter-on-need-for-RTEMS-specific-cross-compiler

Hi Utkarsh, This is almost there, really! The only thing is that you maybe missed or didn't understand a question from Sebastian, "What about using a definition list instead of this hand crafted formatting?" Or any other kind of list structure. https://docutils.sourceforge.io/docs/user/rst/quick

[PATCH] cpukit/rfs: fix typo in header guard

--- cpukit/include/rtems/rfs/rtems-rfs-dir-hash.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cpukit/include/rtems/rfs/rtems-rfs-dir-hash.h b/cpukit/include/rtems/rfs/rtems-rfs-dir-hash.h index d9a8a2004f..7855c874b6 100644 --- a/cpukit/include/rtems/rfs/rtems-rfs-dir-hash

[PATCH v4] Chapter-on-need-for-RTEMS-specific-cross-compiler

--- user/start/tools.rst | 33 + 1 file changed, 33 insertions(+) diff --git a/user/start/tools.rst b/user/start/tools.rst index c3f039b..9a3a93a 100644 --- a/user/start/tools.rst +++ b/user/start/tools.rst @@ -3,6 +3,7 @@ .. Copyright (C) 2019 embedded brains Gmb

Re: [PATCH 1/1] tester: Add configuration pc-qemu.ini

pushed, thank you for this. On Fri, Apr 3, 2020 at 7:31 AM Jan Sommer wrote: > > --- > tester/rtems/testing/bsps/pc-qemu.ini | 39 > +++ > 1 file changed, 39 insertions(+) > create mode 100644 tester/rtems/testing/bsps/pc-qemu.ini > > diff --git a/tester/rtems/t

Re: [PATCH v3] Chapter-on-need-for-RTEMS-specific-cross-compiler

Hi Utkarsh, Please also fix some whitespace problems .git/rebase-apply/patch:23: trailing whitespace. ``Correct configuration of Newlib -`` .git/rebase-apply/patch:28: trailing whitespace. ``Threading in GCC support libraries -`` .git/rebase-apply/patch:31: trailing whitespace. done by the

Re: [PATCH v3] Chapter-on-need-for-RTEMS-specific-cross-compiler

Please ignore this patch, forgot to mention copyright details. On Fri, Apr 3, 2020 at 8:24 PM utkarsh.ra...@gmail.com < utkarsh.ra...@gmail.com> wrote: > --- > user/start/tools.rst | 33 + > 1 file changed, 33 insertions(+) > > diff --git a/user/start/tools.rst b/

Re: [PATCH] bsp/atsam: Use SDRAM memory map by default

On Fri, Apr 3, 2020 at 8:56 AM Sebastian Huber wrote: > > On 03/04/2020 16:51, Gedare Bloom wrote: > > > Thanks for this, please push it > Sorry, it was not meant to push. It doesn't fix the problem. The libbsd > build still fails. But fewer of the tests? I guess if the default configuration is

Re: [PATCH] bsp/atsam: Use SDRAM memory map by default

On 03/04/2020 16:51, Gedare Bloom wrote: Thanks for this, please push it Sorry, it was not meant to push. It doesn't fix the problem. The libbsd build still fails. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

[PATCH v3] Chapter-on-need-for-RTEMS-specific-cross-compiler

--- user/start/tools.rst | 33 + 1 file changed, 33 insertions(+) diff --git a/user/start/tools.rst b/user/start/tools.rst index c3f039b..494e95a 100644 --- a/user/start/tools.rst +++ b/user/start/tools.rst @@ -76,3 +76,36 @@ source code used. Add ``--verbose`

Re: [PATCH] bsp/atsam: Use SDRAM memory map by default

Thanks for this, please push it On Fri, Apr 3, 2020 at 8:44 AM Sebastian Huber wrote: > > This allows to link more libbsd tests. The following tests still fail to > link: > > -> task in 'dhcpcd02.exe' failed with exit status 1 (run with -v to display > more information) > -> task in 'foobarcl

[PATCH] bsp/atsam: Use SDRAM memory map by default

This allows to link more libbsd tests. The following tests still fail to link: -> task in 'dhcpcd02.exe' failed with exit status 1 (run with -v to display more information) -> task in 'foobarclient.exe' failed with exit status 1 (run with -v to display more information) -> task in 'dhcpcd01.

Re: [PATCH] bsps/console: Support device file system

On Fri, Apr 3, 2020 at 8:48 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 02/04/2020 22:28, Joel Sherrill wrote: > > > > On Thu, Apr 2, 2020 at 9:47 AM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> On 02/04/2020 16:45, Gedare Bloom wrote: >> >> > Can we

Re: Add BSP for STM32H7

On 19/03/2020 09:32, Sebastian Huber wrote: Hello, I started to work on a BSP for the STM32H7: https://devel.rtems.org/ticket/3910 I will use the new build system for this BSP. I finished the BSP for the STM32H7. It includes clock, console, random number, Ethernet (libbsd), and USB host dr

Re: [PATCH] bsps/console: Support device file system

On 02/04/2020 22:28, Joel Sherrill wrote: On Thu, Apr 2, 2020 at 9:47 AM Sebastian Huber > wrote: On 02/04/2020 16:45, Gedare Bloom wrote: > Can we hold this until 6? Joel complained that the CONFIGURE_USE_DEVFS_AS_BASE_FILESYSTEM is

Re: [PATCH] score: Fix _ISR_Stack_area_end

push it On Fri, Apr 3, 2020 at 1:53 AM Sebastian Huber wrote: > > The _ISR_Stack_area_begin and _ISR_Stack_area_end symbols are in > different sections. They must have the same alignment, otherwise the > following linker directive could separate them: > > *(SORT_BY_ALIGNMENT (SORT_BY_NAME (.rt

Re: [PATCH] Add a release procedure section.

Hi Chris, Mostly good. I can tell you wrote it top-down and got tired by the end :) Some errors in the last half, nothing major except the part about tagging. Thanks for this, see below: On Fri, Apr 3, 2020 at 1:15 AM wrote: > > From: Chris Johns > > --- > eng/release-mgmt.rst| 4 +- >

[PATCH 0/1] [rtems-tools] Add configuration pc-qemu

I don't mind to maintain that configuration locally, but I think it is generic enough that it might help others too. Jan Sommer (1): tester: Add configuration pc-qemu.ini tester/rtems/testing/bsps/pc-qemu.ini | 39 +++ 1 file changed, 39 insertions(+) create mo

[PATCH 1/1] tester: Add configuration pc-qemu.ini

--- tester/rtems/testing/bsps/pc-qemu.ini | 39 +++ 1 file changed, 39 insertions(+) create mode 100644 tester/rtems/testing/bsps/pc-qemu.ini diff --git a/tester/rtems/testing/bsps/pc-qemu.ini b/tester/rtems/testing/bsps/pc-qemu.ini new file mode 100644 index 000

Re: [PATCH v2] Chapter-on-need-for-RTEMS-specific-cross-compiler

On Thu, Apr 2, 2020 at 11:38 PM Utkarsh Rai wrote: > > > On Fri, Apr 3, 2020 at 8:15 AM Chris Johns wrote: >> >> On 2020-03-28 00:13, utkarsh.ra...@gmail.com wrote: >> > --- >> > user/start/tools.rst | 34 ++ >> > 1 file changed, 34 insertions(+) >> > >> > diff

Re: sqlite build failure on BSP bsets

For those who might reference this in the future, this is the RSB command I used to build sqlite last night from the RTEMS directory: ../source-builder/sb-set-builder \ --log=l-sqlite.txt \ --host=arm-rtems5 \ --prefix=${HOME}/rtems-work/tools/5/bsp-install/ \ --with-tools=${HOME}/rtems-wo

Re: [PATCH] bsp/shared/clock: Reset Clock_driver_isrs to correct value

On 02/04/2020 21:05, Jan Sommer wrote: CLOCK_DRIVER_ISRS_PER_TICK is the configuration define, CLOCK_DRIVER_ISRS_PER_TICK_VALUE is the actual value of ISRS per clock tick, therefore use this one to reset the Clock_driver_isrs after each tick. Thanks, I checked this in. _

RE: Traceability from specification to source code?

HI Sebastian, Marked below with [HS]. -Original Message- From: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] Sent: quarta-feira, 1 de abril de 2020 06:31 To: Helder Silva; RTEMS Subject: Re: Traceability from specification to source code? Hello Helder, On 31/03/2020 20:11

Re: [PATCH v5] doc: Moving M68K BSP Content to User Manual (#3905)

On Fri, Apr 3, 2020 at 3:35 AM Joel Sherrill wrote: > Is there now a list of wiki pages that need to be deleted? > Perhaps, I will report to you more on it after moving almost all useful content of BSPS to User Manual. > > Thank you and I'm glad to see this patch. :) > > --joel > Thanks to you

[PATCH] score: Fix _ISR_Stack_area_end

The _ISR_Stack_area_begin and _ISR_Stack_area_end symbols are in different sections. They must have the same alignment, otherwise the following linker directive could separate them: *(SORT_BY_ALIGNMENT (SORT_BY_NAME (.rtemsstack*))) Update #3799. --- cpukit/Makefile.am |

Re: [PATCH v5] doc: Moving M68K BSP Content to User Manual (#3905)

On Fri, Apr 3, 2020 at 3:24 AM Chris Johns wrote: > Pushed and again thank you for doing this. > > Chris > > All thanks to such enthusiastic and passionate mentors. Perhaps this task is giving me more chills than Netflix :) Mritunjay On 2020-04-02 19:49, Mritunjay wrote: > > Fixed trailing spac

[PATCH v2 1/1] testsuite: A description for each test added

--- testsuite/arphole/test_main.c| 6 ++-- testsuite/cdev01/test_main.c | 7 + testsuite/commands01/test_main.c | 7 + testsuite/condvar01/test_main.c | 7 + testsuite/crypto01/test_main.c | 6 testsuite/debugger01/test_main.

[PATCH v2 0/1] testsuite: A description for each test added

I've moved the description before the copyright header and added some brief tags where needed. Moyano, Gabriel (1): testsuite: A description for each test added testsuite/arphole/test_main.c| 6 ++-- testsuite/cdev01/test_main.c | 7 + testsuite/commands01/test_m

[PATCH] Add a release procedure section.

From: Chris Johns --- eng/release-mgmt.rst| 4 +- eng/release-process.rst | 275 2 files changed, 276 insertions(+), 3 deletions(-) create mode 100644 eng/release-process.rst diff --git a/eng/release-mgmt.rst b/eng/release-mgmt.rst index 6706d62..