Hello Joel,
On 13/02/2020 07:31, Sebastian Huber wrote:
On 13/02/2020 01:17, Joel Sherrill wrote:
Without this change, rtems-libbsd does not compile. A macro turns
free into bsd_free.
Also the use of a standard library element as a program identifier
is a violation of a MISRA rule. Turns out
On 14/02/2020 03:54, Chris Johns wrote:
On 2020-02-12 17:27, Sebastian Huber wrote:
Commit 72c684eff2cd932b4948e21902680a93473340c3 removed the default
value of rtems_tools. If the --rtems--tools option was omitted the
rtems-test command printed lots of
error: run.cfg:61: macro '%{rtems_t
On 14/02/2020 04:41, chr...@rtems.org wrote:
From: Chris Johns
Update #3870
---
testsuites/libtests/newlib01/init.c | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/testsuites/libtests/newlib01/init.c
b/testsuites/libtests/newlib01/init.c
index 74e64879
On 14/02/2020 04:00, Chris Johns wrote:
I must be must be mising what has changed. I cannot see the "wrong
options that have changed?
I removed the serial/monitor settings from qemu_opts_base and moved them
to the new qemu_opts_serial. The realview_pbx_a9_qemu doesn't work with
the serial
Great thanks. Now please begin to work toward identifying what kind of
projects you might be interested in. Hopefully we will find out next week
about our status in GSoC 2020.
On Thu, Feb 13, 2020 at 2:26 PM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:
>
> Mistakenly entered wrong emai
From: Chris Johns
Update #3870
---
testsuites/libtests/newlib01/init.c | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/testsuites/libtests/newlib01/init.c
b/testsuites/libtests/newlib01/init.c
index 74e648799e..1bff052363 100644
--- a/testsuites/libtests/new
On 2020-02-13 18:25, Christian Mauderer wrote:
On 13/02/2020 07:51, Amar Takhar wrote:
On 2020-02-13 07:20 +0100, Christian Mauderer wrote:
Hello Amar,
Hey!
Understood it. It still works when build locally so it shouldn't be a
big problem fixing it. I just wasn't really aware of the single
On 2020-02-12 18:01, Sebastian Huber wrote:
The realview_pbx_a9_qemu test configuration for Qemu produced no output
due to wrong serial/monitor settings. Remove the serial/monitor
settings from qemu_opts_base and move them to the new qemu_opts_serial.
---
tester/rtems/testing/bsps/generic_
On 2020-02-12 17:27, Sebastian Huber wrote:
Commit 72c684eff2cd932b4948e21902680a93473340c3 removed the default
value of rtems_tools. If the --rtems--tools option was omitted the
rtems-test command printed lots of
error: run.cfg:61: macro '%{rtems_tools}' not found
error messages.
I
On 2020-02-13 17:42 -0500, Peter Dufault wrote:
>
> Can you explain this to those of us who are part-time git users?
> I pulled during this time frame, so I must "re-clone" or do a "forced push
> back".
See below.
> I assume "re-clone" means I "rm -rf" a local repository and, well, "re-clone".
>
> On Feb 13, 2020, at 11:55 , Gedare Bloom wrote:
>
> Hello everyone,
>
> Due to some unfortunate mishap, the rtems.git repository needs to be
> rolled back. Anyone who pulled/cloned it since February 12 will be
> impacted, and probably need to re-clone. Most likely, this is going to
> involve
Mistakenly entered wrong email id for the mailing list.
Please follow the thread for the messages.
Thanks & Regret for the typo
From: Mritunjay Sharma
Sent: Friday, February 14, 2020 2:49 AM
To: j...@rtems.org
Cc: dev...@rtems.org
Subject: Re: [PATCH] Initial Comm
Hello Amar,
On 13/02/2020 19:06, Amar Takhar wrote:
Due to a mishap the main repository has been rewound two commits back to
d252e20ab.
The two commits removed were 2272825 and a994e646. You may have to do a force
pull if you grabbed these two commits before this happened.
thanks for fixing t
Due to a mishap the main repository has been rewound two commits back to
d252e20ab.
The two commits removed were 2272825 and a994e646. You may have to do a force
pull if you grabbed these two commits before this happened.
Amar.
___
devel mailing lis
On Thu, Feb 13, 2020 at 11:16 PM Alan Cudmore
wrote:
> "set scheduler-locking on" in GDB works! I was able to run RPI2 hello.exe
>
> So I consider your instructions ready to go in the repo.
> More Pi 2 SMP debugging when I get the time..
> Thanks!
> Alan
>
> Great. But just a caution, QEMU suppor
"set scheduler-locking on" in GDB works! I was able to run RPI2 hello.exe
So I consider your instructions ready to go in the repo.
More Pi 2 SMP debugging when I get the time..
Thanks!
Alan
On Thu, Feb 13, 2020 at 12:30 PM G. S. Niteesh wrote:
>
> On Thu, Feb 13, 2020 at 10:57 PM Alan Cudmore w
On Thu, Feb 13, 2020 at 10:57 PM Alan Cudmore
wrote:
> I get exceptions when trying to run hello.exe.
> I'm using qemu-system-arm v 2.11.1 from ubuntu. Should I try using the
> one built by RSB?
>
No this should be fine. Can you post a screenshot of the output?
> I was trying to get this setup t
I get exceptions when trying to run hello.exe.
I'm using qemu-system-arm v 2.11.1 from ubuntu. Should I try using the
one built by RSB?
I was trying to get this setup to try RPI 2 SMP in QEMU. I may want to
get the latest repo and do a clean build to try this again.
Thanks,
Alan
On Thu, Feb 13, 20
On Thu, Feb 13, 2020 at 10:40 PM Alan Cudmore
wrote:
> Hi Niteesh,
> I have followed your instructions for getting RTEMS running on the Pi
> 1 and 2. SMP currently is not working on the 2 for me, but that is not
> a problem with these instructions.
> I started to try running on QEMU following you
Hi Niteesh,
I have followed your instructions for getting RTEMS running on the Pi
1 and 2. SMP currently is not working on the 2 for me, but that is not
a problem with these instructions.
I started to try running on QEMU following your instructions but have
not been able to get time to complete my
Hello everyone,
Due to some unfortunate mishap, the rtems.git repository needs to be
rolled back. Anyone who pulled/cloned it since February 12 will be
impacted, and probably need to re-clone. Most likely, this is going to
involve a forced push back to commit
d252e20ab5717afea2ac89543ab4e0d379434b
---
c-user/multiprocessing.rst | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/c-user/multiprocessing.rst b/c-user/multiprocessing.rst
index b9f3d43..e6f8271 100644
--- a/c-user/multiprocessing.rst
+++ b/c-user/multiprocessing.rst
@@ -279,11 +279,8 @@ following prototype:
Hello,
this is a first proposal how to split up confdefs.h.
The general approach is to place the default configuration of things in
librtemscpu.a. The benefit is that the application configuration object file
will only include data structures which have a user-defined value.
The component based
The corresponding data structure not longer exists. This function was
not tested.
Close #3871.
---
cpukit/include/rtems/config.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/cpukit/include/rtems/config.h b/cpukit/include/rtems/config.h
index c1d735f587..1c9b35da87 100644
--- a/cpukit/inc
Hi Chris
Yes??It works??thanks??
iPhone
-- Original --
From: Chris Johns https://git.rtems.org/rtems-source-builder/commit/?id=591deae6d7411af04fd31d2a68dee9520b33c657
>
> ... however this option does not help. It is not clear to me what is wrong
w
The testsuites/ada/sptests/sp19/Makefile was added to document how
sptest.adb is generated. However, this Makefile is in the way of
./bootstrap -c. Add an exception.
---
bootstrap | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bootstrap b/bootstrap
index 7ed592d435..b3da3938
---
cpukit/include/rtems/score/wkspace.h | 11 ---
cpukit/score/src/wkspace.c | 5 -
testsuites/sptests/spwkspace/init.c | 14 --
3 files changed, 30 deletions(-)
diff --git a/cpukit/include/rtems/score/wkspace.h
b/cpukit/include/rtems/score/wkspace.h
index 8d
Remove DEBUG_WORKSPACE support. There are better ways to trace the
application. See Tracing chapter in the RTEMS User Manual.
Remove superfluous includes. Change format.
---
cpukit/score/src/wkspace.c | 42 +++---
1 file changed, 3 insertions(+), 39 deletion
28 matches
Mail list logo
