Re: Requirement Identifiers

On 30/07/2019 00:25, Gedare Bloom wrote: We have to be careful to do what makes them presentable to humans. It would seem wise to make the hierarchy of requirements follow the same organization as the hierarchy of the Manual documentation. Yes, and the source code organization. We have also

Re: GSoC Project | Basic Support for Trace Compass

Hello Ravindra, On 29/07/2019 08:14, Ravindra Kumar Meena wrote: *Plan of the week:* Last week I added the sched_switch in client-side. Trace compass can now show more details of the trace now. I will continue to continue to work on client-side. I checked in the RTEMS patch to add some basic

Re: Addition of Rule Checkers

On Mon, Jul 29, 2019 at 5:23 PM Gedare Bloom wrote: > On Wed, Jul 24, 2019 at 7:16 AM Joel Sherrill wrote: > > > > Hi > > > > I just wanted to make sure we followed proper procedures and policies > when considering rule checkers. > > > I guess these comments are germane to the other thread, but

Re: RFC: conditionalize tests on presence of new ndbm methods

On Mon, Jul 29, 2019 at 5:31 PM Gedare Bloom wrote: > On Mon, Jul 29, 2019 at 4:03 PM Chris Johns wrote: > > > > On 30/7/19 7:43 am, Gedare Bloom wrote: > > > On Thu, Jul 25, 2019 at 6:34 AM Joel Sherrill wrote: > > >> > > >> Hi > > >> > > >> I am in the middle of building tools with a newlib

Re: RFC: conditionalize tests on presence of new ndbm methods

On Mon, Jul 29, 2019 at 4:03 PM Chris Johns wrote: > > On 30/7/19 7:43 am, Gedare Bloom wrote: > > On Thu, Jul 25, 2019 at 6:34 AM Joel Sherrill wrote: > >> > >> Hi > >> > >> I am in the middle of building tools with a newlib bump to include the > >> ndbm addition. When I commit the patch which

Re: [PATCH] Adjust gdb-python checks

done On Mon, Jul 29, 2019 at 4:10 PM Chris Johns wrote: > > Thank you for the fix. It is a nice solution to the extra path on Linux. > > OK to push. > > Chris > > On 30/7/19 7:13 am, Gedare Bloom wrote: > > --- > > source-builder/config/gdb-common-1.cfg | 2 +- > > 1 file changed, 1

Re: Requirement Identifiers

On Tue, Jul 23, 2019 at 9:36 AM Joel Sherrill wrote: > > Hi > > I am not sure if I am derailing this or helping. I think we need to seriously > consider that we want these to be easy to manage and the logical names > should reflect the natural groups in RTEMS. > > I lean to something simple like

Re: Addition of Rule Checkers

On Wed, Jul 24, 2019 at 7:16 AM Joel Sherrill wrote: > > Hi > > I just wanted to make sure we followed proper procedures and policies when > considering rule checkers. > I guess these comments are germane to the other thread, but I want to reflect here a bit. > 1. The license must appropriate.

Re: [PATCH] eng: Add Software Requirements Engineering chapter

Seems to make sense to me. I noted just a few very small grammatical errors. On Wed, Jul 24, 2019 at 7:45 AM Sebastian Huber wrote: > > --- > eng/index.rst | 1 + > eng/req-eng.rst | 813 > ++ > images/eng/req-add.pdf| Bin

Re: [PATCH] Adjust gdb-python checks

Thank you for the fix. It is a nice solution to the extra path on Linux. OK to push. Chris On 30/7/19 7:13 am, Gedare Bloom wrote: > --- > source-builder/config/gdb-common-1.cfg | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/source-builder/config/gdb-common-1.cfg >

Re: RFC: conditionalize tests on presence of new ndbm methods

On Thu, Jul 25, 2019 at 6:34 AM Joel Sherrill wrote: > > Hi > > I am in the middle of building tools with a newlib bump to include the ndbm > addition. When I commit the patch which adds a test, builds with older > toolsets will break. > > I think I should conditionalize the test on the

Re: Patch review process

On Fri, Jul 26, 2019 at 2:25 AM Sebastian Huber wrote: > > Hello, > > Joel asked me to document the normal patch review process. Should this > be in a "Contributing" chapter in the user manual or should this stuff > be in the RTEMS Software Engineering manual? > I suggest we try to document all

[PATCH] Adjust gdb-python checks

--- source-builder/config/gdb-common-1.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source-builder/config/gdb-common-1.cfg b/source-builder/config/gdb-common-1.cfg index 159b8a5..0f028ff 100644 --- a/source-builder/config/gdb-common-1.cfg +++

Re: [PATCH v2] user/exe : Add Device Tree section

On Sat, Jul 27, 2019 at 5:49 PM Christian Mauderer wrote: > Hello Vijay, > > sorry for the long delay between posting and review. It was a busy week. > > Would that replace part of the documentation you did in the beagle BSP? > In that case it might could be good to remove it from there and put

Re: How to handle pinmux in libbsd (was: Re: [PATCH 10/10] TI Pinmux : Port to RTEMS)

We had a GSoC project about GPIO API implemented for RPi. https://devel.rtems.org/wiki/GSoC/2013/Raspberry_Pi_BSP_Peripherals On Mon, Jul 29, 2019 at 4:10 AM Christian Mauderer wrote: > > On 29/07/2019 10:54, Vijay Kumar Banerjee wrote: > > > > > > On Sun, Jul 28, 2019 at 5:44 PM Christian

[PATCH v3] user/exe: Add Device Tree section

--- user/bsps/arm/beagle.rst | 21 + user/exe/device-tree.rst | 92 user/exe/index.rst | 1 + 3 files changed, 95 insertions(+), 19 deletions(-) create mode 100644 user/exe/device-tree.rst diff --git a/user/bsps/arm/beagle.rst

Re: [PATCH v6] ndbm test suite

On Tue, Jul 30, 2019 at 12:11 AM Joel Sherrill wrote: > > > On Mon, Jul 29, 2019 at 1:07 PM Vaibhav Gupta > wrote: > >> >> >> On Mon, Jul 29, 2019 at 10:44 PM Joel Sherrill wrote: >> >>> >>> >>> On Mon, Jul 29, 2019 at 11:35 AM Vaibhav Gupta >>> wrote: >>> Thanks Joel! . Now

Re: [PATCH v6] ndbm test suite

On Mon, Jul 29, 2019 at 1:07 PM Vaibhav Gupta wrote: > > > On Mon, Jul 29, 2019 at 10:44 PM Joel Sherrill wrote: > >> >> >> On Mon, Jul 29, 2019 at 11:35 AM Vaibhav Gupta >> wrote: >> >>> Thanks Joel! >>> . >>> Now when the testsuite patch is successfully accepted, I would like >>> to add an

Re: [PATCH v6] ndbm test suite

On Mon, Jul 29, 2019 at 10:44 PM Joel Sherrill wrote: > > > On Mon, Jul 29, 2019 at 11:35 AM Vaibhav Gupta > wrote: > >> Thanks Joel! >> . >> Now when the testsuite patch is successfully accepted, I would like >> to add an example in: >>

Re: GSoC Project | Basic Support for Trace Compass

- Am 29. Jul 2019 um 12:21 schrieb Ravindra Kumar Meena rmeena...@gmail.com: >> >> > What I understand from here is that _prev_state is the previous state of >> > the thread(TID)). >> >> Yes, but what is the meaning of these state values? We have to figure this >> out since we need a mapping

Re: [PATCH v6] ndbm test suite

On Mon, Jul 29, 2019 at 11:35 AM Vaibhav Gupta wrote: > Thanks Joel! > . > Now when the testsuite patch is successfully accepted, I would like > to add an example in: > https://devel.rtems.org/wiki/Developer/Coding/80_characters_per_line, > about wrapping a "function call" in "80 characters per

Re: [PATCH v6] ndbm test suite

Thanks Joel! . Now when the testsuite patch is successfully accepted, I would like to add an example in: https://devel.rtems.org/wiki/Developer/Coding/80_characters_per_line, about wrapping a "function call" in "80 characters per line". . Gedare and me discussed about it on a thread. That time he

Re: [PATCH v6] ndbm test suite

Hi Now pushed. Thanks. I finally got a local sparc tool chain built with the git master of newlib to build and run this test. It was a bit more complicated than I expected. I did add a bit of logic to the psxtests configure.ac and Makefile.am to ensure the test was not built unless the toolset

Re: Build failed for RTEMS Source Builder

Hi Chris, Sorry for late reply as I am busy here for admission in an university. So I tried the solution suggested by you and it somewhere got build failed. This time it didn't asked for sudo privilege and went on building but somewhere build got failed. I checked the error report but there is no

RTEMS Open Class in Huntsville AL US Sept 23-27

Hi There will be an RTEMS Open Class in Huntsville Alabama the week of September 23-27. September 23 - Getting Started September 24 - 27 - Open Class Details and registration forms at http://rtems.com/trainingschedule. If you have questions at all about the class, feel free to email me

Flight Software Workshop 2019

Hi The 12th annual Flight Software Workshop will be held in Huntsville AL USA from December 9-12 2019. Details are at http://flightsoftware.jhuapl.edu/ The Call for Presentations and Registration is currently open. Important dates are: + Call for Presentations/Registration: Monday, June 3rd,

[PATCH 1/3] user/rsb/deployment.rst: Fix typo.

--- user/rsb/deployment.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user/rsb/deployment.rst b/user/rsb/deployment.rst index ad5dd57..afbf13a 100644 --- a/user/rsb/deployment.rst +++ b/user/rsb/deployment.rst @@ -81,7 +81,7 @@ A build set tar file is created by adding

[PATCH 2/3] hosts/windows.rst: Add warning for spaces in PATH

--- user/hosts/windows.rst | 16 1 file changed, 16 insertions(+) diff --git a/user/hosts/windows.rst b/user/hosts/windows.rst index 7aaa9c3..fac1366 100644 --- a/user/hosts/windows.rst +++ b/user/hosts/windows.rst @@ -58,6 +58,22 @@ The release packages of the RSB when unpacked

[PATCH 3/3] hosts/posix.rst: Fix typo of sudu to sudo

Closes #3754. --- user/hosts/posix.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user/hosts/posix.rst b/user/hosts/posix.rst index 044b8bd..24e811f 100644 --- a/user/hosts/posix.rst +++ b/user/hosts/posix.rst @@ -126,7 +126,7 @@ Xubuntu. A minimal installation was used

FW: RTEMS Software Coding Standard

Hi again, (@Joel, sorry for sending this email twice to you, just figure out that I sent to the wrong mailing list) Thank you for your remarks. This is indeed a sensible subject that should be dealt with care. Friday we had a very productive meeting with ESA static analysis expert and

Re: GSoC Project | Basic Support for Trace Compass

> > > What I understand from here is that _prev_state is the previous state of > > the thread(TID)). > > Yes, but what is the meaning of these state values? We have to figure this > out since we need a mapping from RTEMS thread states to these Linux thread > states. Could you use an example trace

Re: How to handle pinmux in libbsd (was: Re: [PATCH 10/10] TI Pinmux : Port to RTEMS)

On 29/07/2019 10:54, Vijay Kumar Banerjee wrote: > > > On Sun, Jul 28, 2019 at 5:44 PM Christian Mauderer > wrote: > > On 28/07/2019 12:42, Vijay Kumar Banerjee wrote: > > > > > > > > On Sat, Jul 27, 2019 at 7:35 PM Christian Mauderer >

Re: How to handle pinmux in libbsd (was: Re: [PATCH 10/10] TI Pinmux : Port to RTEMS)

On Sun, Jul 28, 2019 at 5:44 PM Christian Mauderer wrote: > On 28/07/2019 12:42, Vijay Kumar Banerjee wrote: > > > > > > > > On Sat, Jul 27, 2019 at 7:35 PM Christian Mauderer > > wrote: > > > > Does this initialize only the pins for drivers that are registered in

FW: RTEMS Software Coding Standard

Hi again, Thank you for your remarks. This is indeed a sensible subject that should be dealt with care. Today we had a very productive meeting with ESA static analysis expert and Sebastian. I learned quite a bit and would like to share some information with you. Let me just summarize the main

[PATCH v3] arm/raspberrypi: Fix linker map

Add NULL-pointer protection. Make MMU table read-only. Move vector table to start section. Close #3774. --- bsps/arm/raspberrypi/start/bspstarthooks.c | 2 +- bsps/arm/raspberrypi/start/linkcmds| 34 +++--- 2 files changed, 9 insertions(+), 27 deletions(-)

Re: [PATCH] arm/raspberrypi: Fix linker map

On 29/7/19 4:35 pm, Sebastian Huber wrote: > On 29/07/2019 08:24, Chris Johns wrote: >> On 29/7/19 4:16 pm, Sebastian Huber wrote: >>> On 29/07/2019 08:12, Chris Johns wrote: On 29/7/19 4:08 pm, Sebastian Huber wrote: > On 29/07/2019 08:04, Chris Johns wrote: >>> The new one is

Re: [PATCH] arm/raspberrypi: Fix linker map

On 29/07/2019 08:24, Chris Johns wrote: On 29/7/19 4:16 pm, Sebastian Huber wrote: On 29/07/2019 08:12, Chris Johns wrote: On 29/7/19 4:08 pm, Sebastian Huber wrote: On 29/07/2019 08:04, Chris Johns wrote: The new one is probably: 0x00200080 I am not sure about the 0x80 tail, it should be

Re: [PATCH] arm/raspberrypi: Fix linker map

On 29/7/19 4:16 pm, Sebastian Huber wrote: > On 29/07/2019 08:12, Chris Johns wrote: >> On 29/7/19 4:08 pm, Sebastian Huber wrote: >>> On 29/07/2019 08:04, Chris Johns wrote: > The new one is probably: > > 0x00200080 > > I am not sure about the 0x80 tail, it should be the same

Re: [PATCH] arm/raspberrypi: Fix linker map

On 29/07/2019 08:12, Chris Johns wrote: On 29/7/19 4:08 pm, Sebastian Huber wrote: On 29/07/2019 08:04, Chris Johns wrote: The new one is probably: 0x00200080 I am not sure about the 0x80 tail, it should be the same as it was previously. Better but interrupts? The address 0x0020 works

[PATCH v2] arm/raspberrypi: Fix linker map

Increase size available for initilization and mode stacks. Close #3774. --- bsps/arm/raspberrypi/start/linkcmds | 27 +++ 1 file changed, 3 insertions(+), 24 deletions(-) diff --git a/bsps/arm/raspberrypi/start/linkcmds b/bsps/arm/raspberrypi/start/linkcmds index

Re: [PATCH] arm/raspberrypi: Fix linker map

On 29/7/19 4:08 pm, Sebastian Huber wrote: > On 29/07/2019 08:04, Chris Johns wrote: >>> The new one is probably: >>> >>> 0x00200080 >>> >>> I am not sure about the 0x80 tail, it should be the same as it was >>> previously. >> Better but interrupts? >> >> The address 0x0020 works with hello

Re: [PATCH] arm/raspberrypi: Fix linker map

On 29/07/2019 08:04, Chris Johns wrote: The new one is probably: 0x00200080 I am not sure about the 0x80 tail, it should be the same as it was previously. Better but interrupts? The address 0x0020 works with hello but ticker prints the "TEST VERSION" banner and then nothing more. Then

Re: [PATCH] arm/raspberrypi: Fix linker map

On 29/7/19 3:55 pm, Sebastian Huber wrote: > What was the old start address? START_ADDR=0x8000 ENTRY_ADDR=0x8000 > The new one is probably: > > 0x00200080 > > I am not sure about the 0x80 tail, it should be the same as it was previously. Better but interrupts? The address 0x0020