Re: GSoC: Matt Joyce Introduction

Hi Gedare, Thank you very much for the welcome! Will do on the plain-text. Hopefully this is better. Hello Dr. Sherrill, I’ll stand by for your guidance at your convenience. I’d be happy to recommend updates to the POSIX Compliance Guide and API Guide if I can. Based on Ehsan Dhawan’s notes from

Re: GSoC Introduction, completed getting started guide.

Hello Everyone, I am very muck interested in the Ticket 4272 , BSP Executable Conversion. Please guide me if this project is suitable for GSoC and how can I proceed further to start working on this. Thanks & Regards, Daman On Sun, Mar 14, 2021 at 10:19 PM Ged

Short commit message was Re: [rtems commit] rtems: Fix rtems_task_mode()

Sorry to pick Sebastian and I know it is too late to fix but in providing feedback to Ryan and Alexon their commit messages, "Fix XXX" was a pattern I realized really was not good and encouraged them to avoid. Look at https://git.rtems.org/rtems/log/ and see which ones give you a solid hint and wh

Re: GSoC Introduction, completed getting started guide.

On Thu, Mar 18, 2021 at 6:37 AM Daman Bir Singh wrote: > Hello Everyone, > > I am very muck interested in the Ticket 4272 > , BSP Executable Conversion. Please > guide me if this project is suitable for GSoC and how can I proceed further > to start working on

[PATCH v1 1/2] cpukit: 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. --- cpukit/libdebugger/rtems-debugger-server.c | 4 ++-- cpukit/libdebugger/rtems-debugger-target.c

[PATCH v1 2/2] psxtests: Fix math function build warnings

Added conditionals to ensure that long double function tests were only built when newlib has long double math functions. --- testsuites/psxtests/psxhdrs/math/acoshl.c| 3 +++ testsuites/psxtests/psxhdrs/math/acosl.c | 3 +++ testsuites/psxtests/psxhdrs/math/asinhl.c| 3 +

Re: Short commit message was Re: [rtems commit] rtems: Fix rtems_task_mode()

Hello Joel, On 18/03/2021 14:15, Joel Sherrill wrote: rtems: Fix rtems_task_mode() Do the ASR and preemption mode change only if requested by the mode mask.  The bug was introduced by 508f868237225a75e566d9fd304206363cfe441d. I don't know what is wrong with this commit message subject. It t

[PATCH] pwdgrp.c: Changed assert to void to fix runtime issues (CID #1399781)

Changed the _Assert_unused_value_equals macro to just a void due to /etc having already been created by the network stack initialization or an initial filesystem image. --- cpukit/libcsupport/src/pwdgrp.c | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/cpukit/libcsuppo

Re: [PATCH] pwdgrp.c: Changed assert to void to fix runtime issues (CID #1399781)

Hello Joel, maybe we should first settle on a maximum line length for the commit message subject. So far I assumed that we use standard 50 characters. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94

Re: Short commit message was Re: [rtems commit] rtems: Fix rtems_task_mode()

On Thu, Mar 18, 2021 at 8:21 AM Sebastian Huber wrote: > > Hello Joel, > > On 18/03/2021 14:15, Joel Sherrill wrote: > > > > > rtems: Fix rtems_task_mode() > > > > Do the ASR and preemption mode change only if requested by the mode > > mask. The bug was introduced by > > 508f868237225a75e566d9fd3

Re: [PATCH] pwdgrp.c: Changed assert to void to fix runtime issues (CID #1399781)

Ignoring the first line of commit issue... On Thu, Mar 18, 2021 at 8:29 AM Ryan Long wrote: > > Changed the _Assert_unused_value_equals macro to just a void due to > /etc having already been created by the network stack initialization > or an initial filesystem image. Is there a related ticket?

RE: [PATCH] pwdgrp.c: Changed assert to void to fix runtime issues (CID #1399781)

I didn't make another ticket. I didn't know if I needed to since this was a fix for a previous commit that was merged. Should I? Moving/removing the CID number is fine with me. Whatever y'all think is best. I think having something in the commit message to identify that it was a Coverity issue

Re: [PATCH] pwdgrp.c: Changed assert to void to fix runtime issues (CID #1399781)

On 18/03/2021 16:45, Ryan Long wrote: I didn't make another ticket. I didn't know if I needed to since this was a fix for a previous commit that was merged. Should I? If it is related to an already existing ticket, then please use "Update #XXX" even if the ticket is already closed. It is not u

Re: [PATCH v1 2/2] psxtests: Fix math function build warnings

Hi Stephen, On Thu, Mar 18, 2021 at 8:19 AM Stephen Clark wrote: > > Added conditionals to ensure that long double function tests were only > built when newlib has long double math functions. This patch is not related to the other patch in the series. I recommend that you generally should send u

Re: [PATCH v1 1/2] cpukit: Fixed 32bit pointers

On Thu, Mar 18, 2021 at 8:18 AM Stephen Clark wrote: > > 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. I'd like Chris' opinion on this patch.

Re: Question regarding an open project and documentation enhancement

On Thu, Mar 18, 2021 at 10:08 AM Ayushman Mishra wrote: > > Sorry for the delay (actually I was little busy due to my semester > examination) and extremely sorry for my previous behaviour > > I have created a frequently asked questions (FAQ) page under > quick-start section in user guide according

Re: [PATCH v1 1/2] cpukit: Fixed 32bit pointers

On Thu, Mar 18, 2021 at 9:18 AM Stephen Clark wrote: > 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. > --- > cpukit/libdebugger/rtems-debugg

Re: GSoC: Matt Joyce Introduction

On Wed, Mar 17, 2021 at 10:50 AM Gedare Bloom wrote: > Hi Matt, > > On Wed, Mar 17, 2021 at 6:18 AM Matthew Joyce > wrote: > > > > Hello RTEMS Community! > > > > My name is Matt, I’m a former US Army infantry officer, now back in > school pursuing a second bachelor’s in Computer Science at Orego

Re: [PATCH 2/5] rtems-fdt.c: Fix Resource leak (CID #1437645)

On Thu, Mar 18, 2021 at 1:01 AM Chris Johns wrote: > I do not know. Maybe ask or post a patch? > I have sent a patch please take a look at it https://lists.rtems.org/pipermail/devel/2021-March/065610.html > > On 18 Mar 2021, at 2:14 am, Niteesh G. S. wrote: > >  > > > On Wed, 17 Mar 2021, 12:0

RE: [PATCH v3] covoar: Handle periods in symbols from objdump

> -Original Message- > From: Chris Johns > Sent: Tuesday, March 16, 2021 7:18 PM > To: j...@rtems.org; Alex White > Cc: rtems-de...@rtems.org > Subject: Re: [PATCH v3] covoar: Handle periods in symbols from objdump > > On 17/3/21 9:56 am, Joel Sherrill wrote: > > On Tue, Mar 16, 2021, 4

Re: About is_non_preempt_mode_supported

Thanks for your help! I read the doc. > This is definitely an area where you have to think a bit at the > conceptual purpose of the API/feature to realize why it can't > work or is unsafe in SMP mode. I understand. The only reason we would want to have a feature like no preemption for a thread is

[PATCH v2] psxtests: Fix math function build warnings

Added conditionals to ensure that long double function tests were only built when newlib has long double math functions. --- testsuites/psxtests/psxhdrs/math/acoshl.c| 3 +++ testsuites/psxtests/psxhdrs/math/acosl.c | 3 +++ testsuites/psxtests/psxhdrs/math/asinhl.c| 3 +

[PATCH v2 1/3] 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. --- cpukit/libdebugger/rtems-debugger-server.c | 4 ++-- cpukit/libdebugger/rtems-debugger-target.c

[PATCH v2 2/3] rtems-fdt: 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. --- cpukit/libmisc/rtems-fdt/rtems-fdt-shell.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletion

[PATCH v2 3/3] stackchk: 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. --- cpukit/libmisc/stackchk/check.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --

[PATCH v2] pwdgrp.c: removed assert causing runtime issues

Changed the _Assert_unused_variable_equals macro to just a (void) due to /etc having already been created by the network stack initialization or an initial filesystem image. Updates #4282 --- cpukit/libcsupport/src/pwdgrp.c | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --gi

Re: [PATCH v2 1/3] rtems-debugger: Fixed 32bit pointers

After picking on Ryan, Alex, and Sebastian, you get it next. :) "Fix" or "Fixed" in the short commit message title is not useful when you browse the log of commits: https://git.rtems.org/rtems/log/ Something like "Use uint32_t not uintptr_t for portability to 64-bit CPUs" says a lot more. Think

[PATCH v5 0/2] Fix NOP recognition

v5: - Fix missing std::dec at the end of error message printing in Coverage::finalizeSymbol() v4: - Add specialized CoverageMapNotFoundError exception class to ExecutableInfo - Catch ExecutableInfo::CoverageMapNotFoundError in Coverage::finalizeSymbol() v3: - Fix double increment of rangeIndex

[PATCH v5 2/2] covoar/Target_i386: Add NOP patterns

A couple of NOP patterns found with the pc686 BSP were not detected. This has been fixed. --- tester/covoar/Target_i386.cc | 9 + 1 file changed, 9 insertions(+) diff --git a/tester/covoar/Target_i386.cc b/tester/covoar/Target_i386.cc index e0c9c0f..4567c1e 100644 --- a/tester/covoar/Targ

[PATCH v5 1/2] covoar: Fix NOP execution marking

Some NOP instructions were not being marked as executed because they are located at the end of uncovered ranges. This has been fixed. --- tester/covoar/CoverageMapBase.cc | 10 +++ tester/covoar/CoverageMapBase.h | 4 ++ tester/covoar/DesiredSymbols.cc | 38 +-- tester/covoar/Desi

RE: [PATCH v2 1/3] rtems-debugger: Fixed 32bit pointers

I think Sebastian and Gedare might have referenced this earlier, but I’m not sure if how to be that descriptive within the 50 character limit. "Use uintptr_t not uint32_t for portability to 64-bit CPUs" is 58 characters without a prefix. Even when pared down to something like “Use uintptr_t to b

Re: [PATCH v2 1/3] rtems-debugger: Fixed 32bit pointers

On Thu, Mar 18, 2021, 1:10 PM Stephen Clark wrote: > I think Sebastian and Gedare might have referenced this earlier, but I’m > not sure if how to be that descriptive within the 50 character limit. "Use > uintptr_t not uint32_t for portability to 64-bit CPUs" is 58 characters > without a prefix.

Re: About is_non_preempt_mode_supported

On Thu, Mar 18, 2021 at 11:25 AM Richi Dubey wrote: > > Thanks for your help! I read the doc. >> >> This is definitely an area where you have to think a bit at the >> conceptual purpose of the API/feature to realize why it can't >> work or is unsafe in SMP mode. > > I understand. The only reason w

Re: [PATCH v2] pwdgrp.c: removed assert causing runtime issues

On Thu, Mar 18, 2021 at 11:40 AM Ryan Long wrote: > > Changed the _Assert_unused_variable_equals macro to just a (void) due to > /etc having already been created by the network stack initialization > or an initial filesystem image. > > Updates #4282 > --- > cpukit/libcsupport/src/pwdgrp.c | 9 +++

RE: [PATCH v2] pwdgrp.c: removed assert causing runtime issues

When Joel and I looked at it, this was the only assert that prevented it from running. -Original Message- From: Gedare Bloom Sent: Thursday, March 18, 2021 2:14 PM To: Ryan Long Cc: devel@rtems.org Subject: Re: [PATCH v2] pwdgrp.c: removed assert causing runtime issues On Thu, Mar 18,

Re: [PATCH v2 1/3] rtems-debugger: Fixed 32bit pointers

On Thu, Mar 18, 2021 at 12:14 PM Joel Sherrill wrote: > > > > On Thu, Mar 18, 2021, 1:10 PM Stephen Clark wrote: >> >> I think Sebastian and Gedare might have referenced this earlier, but I’m not >> sure if how to be that descriptive within the 50 character limit. "Use >> uintptr_t not uint32_t

Re: [PATCH v2] pwdgrp.c: removed assert causing runtime issues

On Thu, Mar 18, 2021 at 2:14 PM Gedare Bloom wrote: > On Thu, Mar 18, 2021 at 11:40 AM Ryan Long wrote: > > > > Changed the _Assert_unused_variable_equals macro to just a (void) due to > > /etc having already been created by the network stack initialization > > or an initial filesystem image. >

Re: [PATCH v2] pwdgrp.c: removed assert causing runtime issues

On Thu, Mar 18, 2021 at 2:16 PM Ryan Long wrote: > When Joel and I looked at it, this was the only assert that prevented it > from running. > But Gedare's suggestion is good since it is a VERY precise check. --joel > > -Original Message- > From: Gedare Bloom > Sent: Thursday, March 18

Re: [PATCH v2] pwdgrp.c: removed assert causing runtime issues

On Thu, Mar 18, 2021 at 1:20 PM Joel Sherrill wrote: > > > > On Thu, Mar 18, 2021 at 2:16 PM Ryan Long wrote: >> >> When Joel and I looked at it, this was the only assert that prevented it >> from running. > > > But Gedare's suggestion is good since it is a VERY precise check. > We're not runni

Re: [PATCH v2] psxtests: Fix math function build warnings

Please see my prior email on the first version of this patch, and address those comments. Thanks On Thu, Mar 18, 2021 at 11:31 AM Stephen Clark wrote: > > Added conditionals to ensure that long double function tests were only > built when newlib has long double math functions. > --- > testsuites

Re: [PATCH 1/4] eng: Update EARS syntax

On 18/3/21 4:50 pm, Sebastian Huber wrote: > On 18/03/2021 01:43, Chris Johns wrote: > >> On 18/3/21 4:34 am, Sebastian Huber wrote: >>> The document used the EARS syntax from 2009 which slightly changed in >>> 2016, see "Listens Learned (8 Lessons Learned Applying EARS)".  The >>> optional pre-co

[PATCH v3] pwdgrp.c: removed assert causing runtime issues

Removed the _Assert_unused_variable_equals macro due to /etc having already been created by the network stack initialization or an initial filesystem image. Updates #4282 --- cpukit/libcsupport/src/pwdgrp.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/cpukit/libcsuppor

Re: [PATCH v2 1/3] rtems-debugger: Fixed 32bit pointers

On 19/3/21 4:49 am, Joel Sherrill wrote: > On Thu, Mar 18, 2021 at 12:33 PM Stephen Clark > wrote: > > Using 32bit types like uint32_t for pointers creates issues on 64 bit > architectures like AArch64. Replaced occurrences of these with uintptr_t, >

Re: [PATCH v3] pwdgrp.c: removed assert causing runtime issues

On Thu, Mar 18, 2021 at 1:55 PM Ryan Long wrote: > > Removed the _Assert_unused_variable_equals macro due to /etc > having already been created by the network stack initialization > or an initial filesystem image. > > Updates #4282 > --- > cpukit/libcsupport/src/pwdgrp.c | 6 +- > 1 file chan

Re: [PATCH v2] pwdgrp.c: removed assert causing runtime issues

On 19/3/21 6:19 am, Joel Sherrill wrote: > On Thu, Mar 18, 2021 at 2:14 PM Gedare Bloom > wrote: > On Thu, Mar 18, 2021 at 11:40 AM Ryan Long > wrote: > > > > Changed the _Assert_unused_variable_equals macro to just a (void) d

Re: [PATCH v2] pwdgrp.c: removed assert causing runtime issues

On Thu, Mar 18, 2021 at 3:11 PM Chris Johns wrote: > On 19/3/21 6:19 am, Joel Sherrill wrote: > > On Thu, Mar 18, 2021 at 2:14 PM Gedare Bloom > > wrote: > > On Thu, Mar 18, 2021 at 11:40 AM Ryan Long > > wrote: > > > > > >

[PATCH 3/3] bsps/aarch64: changed comments and test statuses

Expanded upon the commments that were present previously. Added more tests that may finish as 'indeterminate'. --- spec/build/bsps/aarch64/a53/tsta53.yml| 39 +++ spec/build/bsps/aarch64/xilinx-zynqmp/tstqemu.yml | 39 +++ 2 files changed, 66 ins

[PATCH 2/3] Changed variable type to fix AARCH64 test issues

Changed maximum_pending_messages to type size_t to fix the ts-validation0 test. --- cpukit/include/rtems/rtems/message.h| 2 +- cpukit/include/rtems/score/coremsgimpl.h| 2 +- cpukit/score/src/coremsg.c | 2 +- testsuites/validation/tc-message-c

[PATCH 0/3] Renamed tests, test fix, additions to YAML files

Hi, These patches are pretty diverse. They are all from the work we've been doing for AArch64. Patch 1: For this, if a test's YAML file's executable field differed from the name of the file, it was renamed to the name specified in the executable field. After this, I had to change any references

QEMU Beagleboard Emulator

Hi everyone, I'm new to RTEMS Project. I'm interested to work in #2891 ticket (Beagle BSP) for GSoC. I need a *beagleboard* emulator. I tried the following, $ ../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/5 devel/qemu4 $ qemu-system-arm

Re: [PATCH 0/3] Renamed tests, test fix, additions to YAML files

I don't see 1/3 in my email, anyone else? On Thu, Mar 18, 2021 at 2:27 PM Ryan Long wrote: > > Hi, > > These patches are pretty diverse. They are all from the work we've been > doing for AArch64. > > Patch 1: > > For this, if a test's YAML file's executable field differed from the > name of the f

RE: [PATCH 0/3] Renamed tests, test fix, additions to YAML files

Yeah, it was over 250kb or whatever the limit was. It said it was sent to list moderator. -Original Message- From: Gedare Bloom Sent: Thursday, March 18, 2021 3:49 PM To: Ryan Long Cc: devel@rtems.org Subject: Re: [PATCH 0/3] Renamed tests, test fix, additions to YAML files I don't se

Re: [PATCH 2/3] Changed variable type to fix AARCH64 test issues

I've lost some context, but wasn't this already addressed? https://lists.rtems.org/pipermail/devel/2021-March/065021.html On Thu, Mar 18, 2021 at 2:27 PM Ryan Long wrote: > > Changed maximum_pending_messages to type size_t to fix the > ts-validation0 test. > --- > cpukit/include/rtems/rtems/mess

Re: [PATCH 2/3] Changed variable type to fix AARCH64 test issues

On Thu, Mar 18, 2021 at 3:53 PM Gedare Bloom wrote: > I've lost some context, but wasn't this already addressed? > https://lists.rtems.org/pipermail/devel/2021-March/065021.html Ryan .. is this a case where the internal tree fixed it one way and Sebastian fixed it another? Perhaps Sebastian fix

Re: QEMU Beagleboard Emulator

Hi Husni, On Thu, Mar 18, 2021 at 2:28 PM Ahamed Husni wrote: > > Hi everyone, >I'm new to RTEMS Project. I'm interested to work in #2891 ticket (Beagle > BSP) for GSoC. I need a beagleboard emulator. I tried the following, > Welcome. This project is only suitable if you have access to the

RE: [PATCH 2/3] Changed variable type to fix AARCH64 test issues

Yes, a different fix for this went in a couple weeks back. This patch needs to be dropped from the set. Kinsey From: devel On Behalf Of Joel Sherrill Sent: Thursday, March 18, 2021 15:57 To: Gedare Bloom Cc: devel@rtems.org Subject: Re: [PATCH 2/3] Changed variable type to fix AARCH64 test iss

Directories Included in Coverage Reports

Hi Alex has been working hard on getting covoar into shapt and generating reports as he goes. Eventually, this work will all be merged and I will work to generate these reports on an automated basis. But we need to have some discussions on what is and is not covered. Copying over part of an email

Re: Directories Included in Coverage Reports

Now I can reply to this and there will be context. :) On Thu, Mar 18, 2021 at 5:14 PM Joel Sherrill wrote: > Hi > > Alex has been working hard on getting covoar into shapt and generating > reports as he goes. Eventually, this work will all be merged and I will > work to generate these reports on

Re: QEMU Beagleboard Emulator

On Thu, Mar 18, 2021 at 3:58 PM Gedare Bloom wrote: > Hi Husni, > > On Thu, Mar 18, 2021 at 2:28 PM Ahamed Husni > wrote: > > > > Hi everyone, > >I'm new to RTEMS Project. I'm interested to work in #2891 ticket > (Beagle BSP) for GSoC. I need a beagleboard emulator. I tried the following, >

Ada Tests Not Linking

Hi I am trying to build Ada tests for the leon3 and all fail to link. When did these build last? I need to look at adaint.c to see if there is an alternative implementation choice. But, if there isn't, does anyone see an option other than porting at least a minimal version of the missing method(s

[PATCH v2 3/3] bsps/xilinx-zynqmp: Avoid constant UART reinit

Constantly reinitializing the Cadence UART on every character output causes data corruption/loss on some ZynqMP hardware. Only initialize the UART once for early output and give it a kick on startup. --- bsps/aarch64/xilinx-zynqmp/console/console.c | 6 ++ bsps/shared/dev/serial/zynq-uart-poll

[PATCH v2 1/3] cpukit/aarch64: Add ESR register decoding

From: Alex White --- .../aarch64/aarch64-exception-frame-print.c | 83 ++- 1 file changed, 79 insertions(+), 4 deletions(-) diff --git a/cpukit/score/cpu/aarch64/aarch64-exception-frame-print.c b/cpukit/score/cpu/aarch64/aarch64-exception-frame-print.c index 59b5d06032..71d94

[PATCH v2 2/3] score/aarch64: Align context validation frame

Ensure the stack remains aligned when validating the context frame to avoid stack alignment exceptions. --- .../cpu/aarch64/aarch64-context-validate.S | 18 +- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/cpukit/score/cpu/aarch64/aarch64-context-validate.S b/c

Re: [PATCH 3/3] bsps/aarch64: changed comments and test statuses

On 19/3/21 7:27 am, Ryan Long wrote: > Expanded upon the commments that were present previously. > Added more tests that may finish as 'indeterminate'. > --- > spec/build/bsps/aarch64/a53/tsta53.yml| 39 > +++ > spec/build/bsps/aarch64/xilinx-zynqmp/tstqemu.yml | 3

Re: [PATCH rtems-libbsd 1/2] racoon/session: Honor file descriptor maximum

On 3/3/21 7:41 pm, Christian MAUDERER wrote: > Hello Chris, > > Am 03.03.21 um 02:17 schrieb Chris Johns: >> On 2/3/21 7:26 pm, Christian MAUDERER wrote: >>> Hello Chris, >>> >>> Am 02.03.21 um 01:03 schrieb Chris Johns: On 1/3/21 7:24 pm, Christian MAUDERER wrote: > Hello Chris, > >>

GSoC Project- BSP Executable Conversion

Hello everyone, I am interested in pursuing ticket 4272 as my GSoC project. I have started going through the documentation to get to know more about RTEMS and its directory structure. Please guide me how to proceed and start working on this. Thanks & Regards

Re: About is_non_preempt_mode_supported

> > It would not provide anything, and it might encourage a false sense of > concurrency-safety. I understand. Thanks! On Fri, Mar 19, 2021 at 12:40 AM Gedare Bloom wrote: > On Thu, Mar 18, 2021 at 11:25 AM Richi Dubey wrote: > > > > Thanks for your help! I read the doc. > >> > >> This is defi

Re: [PATCH 1/3] bsps: Renamed YAML files to match test names

On 18/03/2021 21:27, Ryan Long wrote: Made the YAML file match the file name specified in the 'executable' field. Fixed any references to the previous file names. Is this massive file renaming really necessary? Why can't we change the executable names to match with the YAML file name? -- embe

Re: [PATCH 2/3] Changed variable type to fix AARCH64 test issues

On 18/03/2021 21:59, Kinsey Moore wrote: Yes, a different fix for this went in a couple weeks back. This patch needs to be dropped from the set. Yes, there is no need for an API change. The bug was actually in the test code. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puc

Re: [PATCH v2 1/3] cpukit/aarch64: Add ESR register decoding

On 18/03/2021 23:51, Kinsey Moore wrote: +void _binary_sprintf( + char *s, + size_t maxlen, + uint32_t num_bits, + uint32_t value +) +{ + uint32_t mask = 1<<(num_bits-1); + int cx = 0; + + while ( mask != 0 ) { +cx += snprintf(s + cx, maxlen - cx, "%d", (value&mask ? 1 : 0)); +mas