Re: [PATCH] user/bld/index.rst: removed references to legacy network config options

Hi Harrison, It's very close, just one little change On Fri, May 7, 2021 at 5:02 PM Harrison Gerber wrote: > > From: Harrison > As it was mentioned in your last review. Please use your full legal name in the patches for attribution purposes. Thank you for the patch. Best regards, Vijay >

[PATCH] user/bld/index.rst: removed references to legacy network config options

From: Harrison --- user/bld/index.rst | 7 --- 1 file changed, 7 deletions(-) diff --git a/user/bld/index.rst b/user/bld/index.rst index ebedf5a..411b3a2 100644 --- a/user/bld/index.rst +++ b/user/bld/index.rst @@ -309,10 +309,6 @@ in the configuration file. Set ``RTEMS_MULTIPROCES

code review: help implementing clock_montonic

hello, Currenttly i'm trying to implement the clock_monotonic which was part of ticket #3889. So far these are the changes are as follows ptimer->clock_type= &clock_id; in the timer create i added a field for the timer id and saved it when the timer was made. Then in getttime I used the appropr

[PATCH v5] rtems-debugger: Fixed 32bit pointers

Using 32bit types like uint32_t for pointers creates issues on 64 bit architectures like AArch64. Replaced occurrences of these with uintptr_t, which will work for both 32 and 64 bit architectures. Added hex_decode_addr function to rtems-debugger. Changed rtems_debugger_target_swbreak_control() par

Re: FVP_BaseR_Cortex-R52x1 not exist when testing arm/fvp_cortex_r52

On Fri, May 7, 2021 at 12:12 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > On 07/05/2021 19:07, Joel Sherrill wrote: > > > > > > On Fri, May 7, 2021 at 11:42 AM Sebastian Huber > > > > wrote: > > > > > > On 07/05/2021 17:12, Đức

[PATCH v2] rtemstoolkit/mailer.py: Fix option ordering for add_arguments

The ordering of keys cannot be guaranteed in a dictionary. This changes the options iteration to no longer rely on key ordering. Closes #4402 --- rtemstoolkit/mailer.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/rtemstoolkit/mailer.py b/rtemstoolkit/mailer.py index ae5

OAR RTEMS Automated Build Sweep Update

Hi I wanted to pass along that I turned on rtems7 tools to be built once a week and test the same BSPs and configurations done for rtems6. Results should be showing up on build@. Currently the following is done: + If RTEMS Tools has changed, Coverity is run at 12:15 PM every day (CentOS) + If

Re: FVP_BaseR_Cortex-R52x1 not exist when testing arm/fvp_cortex_r52

On 07/05/2021 19:07, Joel Sherrill wrote: On Fri, May 7, 2021 at 11:42 AM Sebastian Huber > wrote: On 07/05/2021 17:12, Đức Anh wrote: > Dear all, > > I built arm/fvp_cortex_r52 on the master branch, commit a1679af3805. > W

Re: FVP_BaseR_Cortex-R52x1 not exist when testing arm/fvp_cortex_r52

On Fri, May 7, 2021 at 11:42 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > On 07/05/2021 17:12, Đức Anh wrote: > > Dear all, > > > > I built arm/fvp_cortex_r52 on the master branch, commit a1679af3805. > > When I run rtems-test for this BSP, the program report > > that FVP_Ba

Re: FVP_BaseR_Cortex-R52x1 not exist when testing arm/fvp_cortex_r52

On 07/05/2021 17:12, Đức Anh wrote: Dear all, I built arm/fvp_cortex_r52 on the master branch, commit a1679af3805. When I run rtems-test for this BSP, the program report that FVP_BaseR_Cortex-R52x1 does not exist. So that all the tests failed. It works for me: [4329/4329] Linking /tmp/sh/

Re: FVP_BaseR_Cortex-R52x1 not exist when testing arm/fvp_cortex_r52

On Fri, May 7, 2021, 10:13 AM Đức Anh wrote: > Dear all, > > I built arm/fvp_cortex_r52 on the master branch, commit a1679af3805. When > I run rtems-test for this BSP, the program report > that FVP_BaseR_Cortex-R52x1 does not exist. So that all the tests failed. > I don't see a configuration fil

FVP_BaseR_Cortex-R52x1 not exist when testing arm/fvp_cortex_r52

Dear all, I built arm/fvp_cortex_r52 on the master branch, commit a1679af3805. When I run rtems-test for this BSP, the program report that FVP_BaseR_Cortex-R52x1 does not exist. So that all the tests failed. How can I fix this problem? I followed all the build step (./waf configure, build, instal

Re: [PATCH rtems-libbsd] ipsec-tools/pfkey: Fix socket leak

Hello Joel, Am 07.05.21 um 16:45 schrieb Joel Sherrill: On Fri, May 7, 2021 at 9:04 AM Christian MAUDERER > wrote: It is a bit hard to see: The setkey programm uses the functions from this library. In pfkey_open, a socket is opened and r

Re: [PATCH rtems-libbsd] ipsec-tools/pfkey: Fix socket leak

On Fri, May 7, 2021 at 9:04 AM Christian MAUDERER < christian.maude...@embedded-brains.de> wrote: > It is a bit hard to see: The setkey programm uses the functions from > this library. In pfkey_open, a socket is opened and returned to setkey. > But setkey never closes it. > This much I assumed fr

Re: [PATCH rtems-libbsd] ipsec-tools/pfkey: Fix socket leak

It is a bit hard to see: The setkey programm uses the functions from this library. In pfkey_open, a socket is opened and returned to setkey. But setkey never closes it. We already have wrappers around all of the "dangerous" functions that allocated resources. The wrappers register the resource

Re: [PATCH rtems-libbsd] ipsec-tools/pfkey: Fix socket leak

How does this fix a leak? On Fri, May 7, 2021 at 7:09 AM Christian MAUDERER < christian.maude...@embedded-brains.de> wrote: > Note that I would like to push this patch on 5-freebsd-12 as well as on > master. > > Best regards > > Christian > > > Am 07.05.21 um 14:08 schrieb Christian Mauderer: > >

Re: [PATCH rtems-libbsd] ipsec-tools/pfkey: Fix socket leak

Note that I would like to push this patch on 5-freebsd-12 as well as on master. Best regards Christian Am 07.05.21 um 14:08 schrieb Christian Mauderer: Fixes #4404 --- ipsec-tools/src/libipsec/pfkey.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/ipsec-tools/src/libipsec/pfke

[PATCH rtems-libbsd] ipsec-tools/pfkey: Fix socket leak

Fixes #4404 --- ipsec-tools/src/libipsec/pfkey.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/ipsec-tools/src/libipsec/pfkey.c b/ipsec-tools/src/libipsec/pfkey.c index a621be12..385a21a9 100644 --- a/ipsec-tools/src/libipsec/pfkey.c +++ b/ipsec-tools/src/libipsec/pfkey.c @@ -1,5 +1,1

Re: qemu version for source builder

On 5/7/21 8:15 AM, Richi Dubey wrote: >  So, does this qemu not support e6500 cores (for the t2080rdb platform)? IIRC e500/e5500/e6500 are supported by ppce500. Karel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel