Re: [PATCH 1/2] bsp/raspberrypi: Fix build warnings.

I have a sent v2. It uses PRIdrtems_vector_number as the specifier. Please have a look at it. https://lists.rtems.org/pipermail/devel/2020-March/058716.html Thank you, Niteesh On Sun, Mar 29, 2020 at 5:17 AM Gedare Bloom wrote: > On Sat, Mar 28, 2020 at 10:11 AM Joel Sherrill wrote: > > > >

Re: [PATCH 1/2] bsp/raspberrypi: Fix build warnings.

On Sat, Mar 28, 2020 at 10:11 AM Joel Sherrill wrote: > > This looks ok. UNLESS we have an RTEMS specific inttypes.h format specifier > for vector. > > I don't recall where those are defined or documented. :( > Maybe we ought to, but this should never be an lu anyway. > On Sat, Mar 28, 2020,

[rtems-libbsd PATCH] wscript: Python2 support for unicode strings in contexts

Update #3909 --- wscript | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/wscript b/wscript index e0a7e9f7..3ca9478e 100644 --- a/wscript +++ b/wscript @@ -144,8 +144,8 @@ def bsp_init(ctx, env, contexts): newcmd = y.cmd + '-' + builder

Re: ticket #3372 Add tests for inttypes.h methods to RTEMS

On Sat, Mar 28, 2020, 3:46 PM Eshan Dhawan wrote: > Hello everyone, > I went through the currently available tests > they lack the test for functions > •imaxabs() > • imaxdiv() > Please tell that If any other function whose test is to be added. > If we knew, there would either be tests or

ticket #3372 Add tests for inttypes.h methods to RTEMS

Hello everyone, I went through the currently available tests they lack the test for functions •imaxabs() • imaxdiv() Please tell that If any other function whose test is to be added. Thanks -Eshan ___ devel mailing list devel@rtems.org

POSIX Compliance project proposal

Hello everyone, I have completed my project proposal on POSIX Compliance . I have tried to implement every feedback and comments that I have received on the proposal. Also could tell me the tickets

Re: [PATCH] user/gsoc: GSoC Getting Started Instructions

We have an Installation chapter under the User manual https://docs.rtems.org/branches/master/user/installation/index.html But it isn't detailed enough like the quick start guide. IMO it is the right place to add detailed instructions. It already has important information for a good setup like

Re: [PATCH 2/2] gpio/gpio-support: Fix build warnings.

On Sat, Mar 28, 2020 at 9:38 PM Joel Sherrill wrote: > We don't think you should assert or generate a fatal error after > initialization. This could cause an unknown, but safety critical, > application to fail. > > This same logic should be converted to a run-time error. > Should I just return

[PATCH v2] bsp/raspberrypi: Fix build warnings.

1) _Memory_Initialize makes pointer from integer without a cast. 2) printf format error, expects %u but %lu provided. --- bsps/arm/raspberrypi/irq/irq.c | 4 +++- bsps/arm/raspberrypi/start/bspstarthooks.c | 2 ++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git

Re: [PATCH 1/2] bsp/raspberrypi: Fix build warnings.

This looks ok. UNLESS we have an RTEMS specific inttypes.h format specifier for vector. I don't recall where those are defined or documented. :( On Sat, Mar 28, 2020, 5:50 AM G S Niteesh Babu wrote: > 1) _Memory_Initialize makes pointer from integer w > ithout a cast. > 2) printf format error,

Re: [PATCH 2/2] gpio/gpio-support: Fix build warnings.

We don't think you should assert or generate a fatal error after initialization. This could cause an unknown, but safety critical, application to fail. This same logic should be converted to a run-time error. This is probably guidance that is or should be in the coding style in the software

Re: Discussion regarding high-level interface for GSoC memory protection project.

Got it, I will modify my proposal draft accordingly. On Sat, Mar 28, 2020 at 7:12 PM Gedare Bloom wrote: > On Sat, Mar 28, 2020 at 4:59 AM Peter Dufault wrote: > > > > > > > > > On Mar 27, 2020, at 14:16 , Utkarsh Rai > wrote: > > > > > > > > > On Fri, Mar 27, 2020 at 9:31 PM Gedare Bloom

Re: Discussion regarding high-level interface for GSoC memory protection project.

On Sat, Mar 28, 2020 at 4:59 AM Peter Dufault wrote: > > > > > On Mar 27, 2020, at 14:16 , Utkarsh Rai wrote: > > > > > > On Fri, Mar 27, 2020 at 9:31 PM Gedare Bloom wrote: > > Hi Utkarsh, > > > > You can remove "Discussion regarding" from your subject lines. We know > > your emails are

Re: Discussion regarding high-level interface for GSoC memory protection project.

> On Mar 27, 2020, at 14:16 , Utkarsh Rai wrote: > > > On Fri, Mar 27, 2020 at 9:31 PM Gedare Bloom wrote: > Hi Utkarsh, > > You can remove "Discussion regarding" from your subject lines. We know > your emails are discussions regarding the subject. > > On Fri, Mar 27, 2020 at 5:26 AM

[PATCH 2/2] gpio/gpio-support: Fix build warnings.

Fixes "array subscript is outside array bounds" in gpio-support.c --- bsps/shared/dev/gpio/gpio-support.c | 1 + 1 file changed, 1 insertion(+) diff --git a/bsps/shared/dev/gpio/gpio-support.c b/bsps/shared/dev/gpio/gpio-support.c index 9c053dc151..04f1c8ca90 100644 ---

[PATCH 1/2] bsp/raspberrypi: Fix build warnings.

1) _Memory_Initialize makes pointer from integer w ithout a cast. 2) printf format error, expects %u but %lu provided. --- bsps/arm/raspberrypi/irq/irq.c | 2 +- bsps/arm/raspberrypi/start/bspstarthooks.c | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git