[PATCH] bsp/raspberry: Add a bsp_fdt_map_intr().

[Christian Mauderer]

From: Christian Mauderer 

Fixes #3903
---
 bsps/arm/raspberrypi/include/bsp/irq.h |  2 ++
 bsps/arm/raspberrypi/start/bspstart.c  | 23 +++
 2 files changed, 25 insertions(+)

diff --git a/bsps/arm/raspberrypi/include/bsp/irq.h 
b/bsps/arm/raspberrypi/include/bsp/irq.h
index 6a9d05cba6..6758094519 100644
--- a/bsps/arm/raspberrypi/include/bsp/irq.h
+++ b/bsps/arm/raspberrypi/include/bsp/irq.h
@@ -35,6 +35,8 @@
 
 #define BCM2835_INTC_TOTAL_IRQ   64 + 8
 
+#define BCM2835_IRQ_SET1_MIN 0
+#define BCM2835_IRQ_SET2_MIN 32
 
 #define BCM2835_IRQ_ID_GPU_TIMER_M0  0
 #define BCM2835_IRQ_ID_GPU_TIMER_M1  1
diff --git a/bsps/arm/raspberrypi/start/bspstart.c 
b/bsps/arm/raspberrypi/start/bspstart.c
index 49896e4d47..89fe8707f1 100644
--- a/bsps/arm/raspberrypi/start/bspstart.c
+++ b/bsps/arm/raspberrypi/start/bspstart.c
@@ -101,6 +101,29 @@ void *raspberrypi_get_reg_of_node(const void *fdt, int 
node)
   return (BUS_TO_PHY((void *) fdt32_to_cpu(val[0])));
 }
 
+#ifdef BSP_FDT_IS_SUPPORTED
+uint32_t bsp_fdt_map_intr(const uint32_t *intr, size_t icells)
+{
+  uint32_t controller = intr[0];
+  uint32_t source = intr[1];
+
+  switch(controller) {
+case 0:
+return source + BCM2835_IRQ_ID_BASIC_BASE_ID;
+break;
+case 1:
+return source + BCM2835_IRQ_SET1_MIN;
+break;
+case 2:
+return source + BCM2835_IRQ_SET2_MIN;
+break;
+default:
+return (uint32_t)(-1);
+break;
+  }
+}
+#endif /* BSP_FDT_IS_SUPPORTED */
+
 void bsp_start(void)
 {
 bcm2835_get_board_spec_entries spec = { 0 };
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] bsp/raspberry: Add a bsp_fdt_map_intr().

[Gedare Bloom]

On Sat, Apr 4, 2020 at 4:57 AM Christian Mauderer  wrote:
>
> From: Christian Mauderer 
>
> Fixes #3903
> ---
>  bsps/arm/raspberrypi/include/bsp/irq.h |  2 ++
>  bsps/arm/raspberrypi/start/bspstart.c  | 23 +++
>  2 files changed, 25 insertions(+)
>
> diff --git a/bsps/arm/raspberrypi/include/bsp/irq.h 
> b/bsps/arm/raspberrypi/include/bsp/irq.h
> index 6a9d05cba6..6758094519 100644
> --- a/bsps/arm/raspberrypi/include/bsp/irq.h
> +++ b/bsps/arm/raspberrypi/include/bsp/irq.h
> @@ -35,6 +35,8 @@
>
>  #define BCM2835_INTC_TOTAL_IRQ   64 + 8
>
> +#define BCM2835_IRQ_SET1_MIN 0
> +#define BCM2835_IRQ_SET2_MIN 32
>
>  #define BCM2835_IRQ_ID_GPU_TIMER_M0  0
>  #define BCM2835_IRQ_ID_GPU_TIMER_M1  1
> diff --git a/bsps/arm/raspberrypi/start/bspstart.c 
> b/bsps/arm/raspberrypi/start/bspstart.c
> index 49896e4d47..89fe8707f1 100644
> --- a/bsps/arm/raspberrypi/start/bspstart.c
> +++ b/bsps/arm/raspberrypi/start/bspstart.c
> @@ -101,6 +101,29 @@ void *raspberrypi_get_reg_of_node(const void *fdt, int 
> node)
>return (BUS_TO_PHY((void *) fdt32_to_cpu(val[0])));
>  }
>
> +#ifdef BSP_FDT_IS_SUPPORTED
> +uint32_t bsp_fdt_map_intr(const uint32_t *intr, size_t icells)
> +{
> +  uint32_t controller = intr[0];
> +  uint32_t source = intr[1];
> +
> +  switch(controller) {
should have spaces here:
  switch ( controller ) {

> +case 0:
> +return source + BCM2835_IRQ_ID_BASIC_BASE_ID;
> +break;
> +case 1:
> +return source + BCM2835_IRQ_SET1_MIN;
> +break;
> +case 2:
> +return source + BCM2835_IRQ_SET2_MIN;
> +break;
> +default:
> +return (uint32_t)(-1);
Not my favorite thing to see. Is 0 an ok error condition?

It can be pushed either way

> +break;
> +  }
> +}
> +#endif /* BSP_FDT_IS_SUPPORTED */
> +
>  void bsp_start(void)
>  {
>  bcm2835_get_board_spec_entries spec = { 0 };
> --
> 2.25.1
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] bsp/raspberry: Add a bsp_fdt_map_intr().

[Christian Mauderer]

On 04/04/2020 17:04, Gedare Bloom wrote:
> On Sat, Apr 4, 2020 at 4:57 AM Christian Mauderer  wrote:
>>
>> From: Christian Mauderer 
>>
>> Fixes #3903
>> ---
>>  bsps/arm/raspberrypi/include/bsp/irq.h |  2 ++
>>  bsps/arm/raspberrypi/start/bspstart.c  | 23 +++
>>  2 files changed, 25 insertions(+)
>>
>> diff --git a/bsps/arm/raspberrypi/include/bsp/irq.h 
>> b/bsps/arm/raspberrypi/include/bsp/irq.h
>> index 6a9d05cba6..6758094519 100644
>> --- a/bsps/arm/raspberrypi/include/bsp/irq.h
>> +++ b/bsps/arm/raspberrypi/include/bsp/irq.h
>> @@ -35,6 +35,8 @@
>>
>>  #define BCM2835_INTC_TOTAL_IRQ   64 + 8
>>
>> +#define BCM2835_IRQ_SET1_MIN 0
>> +#define BCM2835_IRQ_SET2_MIN 32
>>
>>  #define BCM2835_IRQ_ID_GPU_TIMER_M0  0
>>  #define BCM2835_IRQ_ID_GPU_TIMER_M1  1
>> diff --git a/bsps/arm/raspberrypi/start/bspstart.c 
>> b/bsps/arm/raspberrypi/start/bspstart.c
>> index 49896e4d47..89fe8707f1 100644
>> --- a/bsps/arm/raspberrypi/start/bspstart.c
>> +++ b/bsps/arm/raspberrypi/start/bspstart.c
>> @@ -101,6 +101,29 @@ void *raspberrypi_get_reg_of_node(const void *fdt, int 
>> node)
>>return (BUS_TO_PHY((void *) fdt32_to_cpu(val[0])));
>>  }
>>
>> +#ifdef BSP_FDT_IS_SUPPORTED
>> +uint32_t bsp_fdt_map_intr(const uint32_t *intr, size_t icells)
>> +{
>> +  uint32_t controller = intr[0];
>> +  uint32_t source = intr[1];
>> +
>> +  switch(controller) {
> should have spaces here:
>   switch ( controller ) {

I'll fix that before pushing.

> 
>> +case 0:
>> +return source + BCM2835_IRQ_ID_BASIC_BASE_ID;
>> +break;
>> +case 1:
>> +return source + BCM2835_IRQ_SET1_MIN;
>> +break;
>> +case 2:
>> +return source + BCM2835_IRQ_SET2_MIN;
>> +break;
>> +default:
>> +return (uint32_t)(-1);
> Not my favorite thing to see. Is 0 an ok error condition?
> 
> It can be pushed either way

0 is a valid interrupt. I wanted one that isn't valid as an error value
so that some function throws an error (for example there are some checks
during bsp_interrupt_vector_enable / _disable for this BSP).

If you prefer, I could use one of the following:

* (BSP_INTERRUPT_VECTOR_MAX + 1)
* BSP_IRQ_COUNT
* UINT32_MAX
* BSP_INTERRUPT_VECTOR_INVALID and set that define to for example UINT32_MAX

Best regards

Christian

> 
>> +break;
>> +  }
>> +}
>> +#endif /* BSP_FDT_IS_SUPPORTED */
>> +
>>  void bsp_start(void)
>>  {
>>  bcm2835_get_board_spec_entries spec = { 0 };
>> --
>> 2.25.1
>>
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
> 
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] bsp/raspberry: Add a bsp_fdt_map_intr().

[Gedare Bloom]

On Sat, Apr 4, 2020 at 9:14 AM Christian Mauderer  wrote:
>
> On 04/04/2020 17:04, Gedare Bloom wrote:
> > On Sat, Apr 4, 2020 at 4:57 AM Christian Mauderer  
> > wrote:
> >>
> >> From: Christian Mauderer 
> >>
> >> Fixes #3903
> >> ---
> >>  bsps/arm/raspberrypi/include/bsp/irq.h |  2 ++
> >>  bsps/arm/raspberrypi/start/bspstart.c  | 23 +++
> >>  2 files changed, 25 insertions(+)
> >>
> >> diff --git a/bsps/arm/raspberrypi/include/bsp/irq.h 
> >> b/bsps/arm/raspberrypi/include/bsp/irq.h
> >> index 6a9d05cba6..6758094519 100644
> >> --- a/bsps/arm/raspberrypi/include/bsp/irq.h
> >> +++ b/bsps/arm/raspberrypi/include/bsp/irq.h
> >> @@ -35,6 +35,8 @@
> >>
> >>  #define BCM2835_INTC_TOTAL_IRQ   64 + 8
> >>
> >> +#define BCM2835_IRQ_SET1_MIN 0
> >> +#define BCM2835_IRQ_SET2_MIN 32
> >>
> >>  #define BCM2835_IRQ_ID_GPU_TIMER_M0  0
> >>  #define BCM2835_IRQ_ID_GPU_TIMER_M1  1
> >> diff --git a/bsps/arm/raspberrypi/start/bspstart.c 
> >> b/bsps/arm/raspberrypi/start/bspstart.c
> >> index 49896e4d47..89fe8707f1 100644
> >> --- a/bsps/arm/raspberrypi/start/bspstart.c
> >> +++ b/bsps/arm/raspberrypi/start/bspstart.c
> >> @@ -101,6 +101,29 @@ void *raspberrypi_get_reg_of_node(const void *fdt, 
> >> int node)
> >>return (BUS_TO_PHY((void *) fdt32_to_cpu(val[0])));
> >>  }
> >>
> >> +#ifdef BSP_FDT_IS_SUPPORTED
> >> +uint32_t bsp_fdt_map_intr(const uint32_t *intr, size_t icells)
> >> +{
> >> +  uint32_t controller = intr[0];
> >> +  uint32_t source = intr[1];
> >> +
> >> +  switch(controller) {
> > should have spaces here:
> >   switch ( controller ) {
>
> I'll fix that before pushing.
>
> >
> >> +case 0:
> >> +return source + BCM2835_IRQ_ID_BASIC_BASE_ID;
> >> +break;
> >> +case 1:
> >> +return source + BCM2835_IRQ_SET1_MIN;
> >> +break;
> >> +case 2:
> >> +return source + BCM2835_IRQ_SET2_MIN;
> >> +break;
> >> +default:
> >> +return (uint32_t)(-1);
> > Not my favorite thing to see. Is 0 an ok error condition?
> >
> > It can be pushed either way
>
> 0 is a valid interrupt. I wanted one that isn't valid as an error value
> so that some function throws an error (for example there are some checks
> during bsp_interrupt_vector_enable / _disable for this BSP).
>
> If you prefer, I could use one of the following:
>
> * (BSP_INTERRUPT_VECTOR_MAX + 1)
> * BSP_IRQ_COUNT
> * UINT32_MAX
> * BSP_INTERRUPT_VECTOR_INVALID and set that define to for example UINT32_MAX
>
It would be nice to have something that could be used consistently,
since this is a shared low-level interface. I like
BSP_INTERRUPT_VECTOR_INVALID idea.

> Best regards
>
> Christian
>
> >
> >> +break;
> >> +  }
> >> +}
> >> +#endif /* BSP_FDT_IS_SUPPORTED */
> >> +
> >>  void bsp_start(void)
> >>  {
> >>  bcm2835_get_board_spec_entries spec = { 0 };
> >> --
> >> 2.25.1
> >>
> >> ___
> >> devel mailing list
> >> devel@rtems.org
> >> http://lists.rtems.org/mailman/listinfo/devel
> >
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH v2] bsp/raspberry: Add a bsp_fdt_map_intr().

[Christian Mauderer]

From: Christian Mauderer 

Fixes #3903
---
 bsps/arm/raspberrypi/include/bsp/irq.h |  3 +++
 bsps/arm/raspberrypi/start/bspstart.c  | 24 
 2 files changed, 27 insertions(+)

diff --git a/bsps/arm/raspberrypi/include/bsp/irq.h 
b/bsps/arm/raspberrypi/include/bsp/irq.h
index 6a9d05cba6..17e4472b34 100644
--- a/bsps/arm/raspberrypi/include/bsp/irq.h
+++ b/bsps/arm/raspberrypi/include/bsp/irq.h
@@ -35,6 +35,8 @@
 
 #define BCM2835_INTC_TOTAL_IRQ   64 + 8
 
+#define BCM2835_IRQ_SET1_MIN 0
+#define BCM2835_IRQ_SET2_MIN 32
 
 #define BCM2835_IRQ_ID_GPU_TIMER_M0  0
 #define BCM2835_IRQ_ID_GPU_TIMER_M1  1
@@ -69,6 +71,7 @@
 
 #define BSP_INTERRUPT_VECTOR_MIN(0)
 #define BSP_INTERRUPT_VECTOR_MAX(BCM2835_INTC_TOTAL_IRQ - 1)
+#define BSP_INTERRUPT_VECTOR_INVALID (UINT32_MAX)
 
 #define BSP_IRQ_COUNT   (BCM2835_INTC_TOTAL_IRQ)
 
diff --git a/bsps/arm/raspberrypi/start/bspstart.c 
b/bsps/arm/raspberrypi/start/bspstart.c
index 49896e4d47..8d7f6aa503 100644
--- a/bsps/arm/raspberrypi/start/bspstart.c
+++ b/bsps/arm/raspberrypi/start/bspstart.c
@@ -23,6 +23,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include 
 
@@ -101,6 +102,29 @@ void *raspberrypi_get_reg_of_node(const void *fdt, int 
node)
   return (BUS_TO_PHY((void *) fdt32_to_cpu(val[0])));
 }
 
+#ifdef BSP_FDT_IS_SUPPORTED
+uint32_t bsp_fdt_map_intr(const uint32_t *intr, size_t icells)
+{
+  uint32_t controller = intr[0];
+  uint32_t source = intr[1];
+
+  switch ( controller ) {
+case 0:
+return source + BCM2835_IRQ_ID_BASIC_BASE_ID;
+break;
+case 1:
+return source + BCM2835_IRQ_SET1_MIN;
+break;
+case 2:
+return source + BCM2835_IRQ_SET2_MIN;
+break;
+default:
+return BSP_INTERRUPT_VECTOR_INVALID;
+break;
+  }
+}
+#endif /* BSP_FDT_IS_SUPPORTED */
+
 void bsp_start(void)
 {
 bcm2835_get_board_spec_entries spec = { 0 };
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH v2] bsp/raspberry: Add a bsp_fdt_map_intr().

[Gedare Bloom]

Looks good, go ahead; thanks.

On Sat, Apr 4, 2020 at 10:39 AM Christian Mauderer  wrote:
>
> From: Christian Mauderer 
>
> Fixes #3903
> ---
>  bsps/arm/raspberrypi/include/bsp/irq.h |  3 +++
>  bsps/arm/raspberrypi/start/bspstart.c  | 24 
>  2 files changed, 27 insertions(+)
>
> diff --git a/bsps/arm/raspberrypi/include/bsp/irq.h 
> b/bsps/arm/raspberrypi/include/bsp/irq.h
> index 6a9d05cba6..17e4472b34 100644
> --- a/bsps/arm/raspberrypi/include/bsp/irq.h
> +++ b/bsps/arm/raspberrypi/include/bsp/irq.h
> @@ -35,6 +35,8 @@
>
>  #define BCM2835_INTC_TOTAL_IRQ   64 + 8
>
> +#define BCM2835_IRQ_SET1_MIN 0
> +#define BCM2835_IRQ_SET2_MIN 32
>
>  #define BCM2835_IRQ_ID_GPU_TIMER_M0  0
>  #define BCM2835_IRQ_ID_GPU_TIMER_M1  1
> @@ -69,6 +71,7 @@
>
>  #define BSP_INTERRUPT_VECTOR_MIN(0)
>  #define BSP_INTERRUPT_VECTOR_MAX(BCM2835_INTC_TOTAL_IRQ - 1)
> +#define BSP_INTERRUPT_VECTOR_INVALID (UINT32_MAX)
>
>  #define BSP_IRQ_COUNT   (BCM2835_INTC_TOTAL_IRQ)
>
> diff --git a/bsps/arm/raspberrypi/start/bspstart.c 
> b/bsps/arm/raspberrypi/start/bspstart.c
> index 49896e4d47..8d7f6aa503 100644
> --- a/bsps/arm/raspberrypi/start/bspstart.c
> +++ b/bsps/arm/raspberrypi/start/bspstart.c
> @@ -23,6 +23,7 @@
>  #include 
>  #include 
>  #include 
> +#include 
>
>  #include 
>
> @@ -101,6 +102,29 @@ void *raspberrypi_get_reg_of_node(const void *fdt, int 
> node)
>return (BUS_TO_PHY((void *) fdt32_to_cpu(val[0])));
>  }
>
> +#ifdef BSP_FDT_IS_SUPPORTED
> +uint32_t bsp_fdt_map_intr(const uint32_t *intr, size_t icells)
> +{
> +  uint32_t controller = intr[0];
> +  uint32_t source = intr[1];
> +
> +  switch ( controller ) {
> +case 0:
> +return source + BCM2835_IRQ_ID_BASIC_BASE_ID;
> +break;
> +case 1:
> +return source + BCM2835_IRQ_SET1_MIN;
> +break;
> +case 2:
> +return source + BCM2835_IRQ_SET2_MIN;
> +break;
> +default:
> +return BSP_INTERRUPT_VECTOR_INVALID;
> +break;
> +  }
> +}
> +#endif /* BSP_FDT_IS_SUPPORTED */
> +
>  void bsp_start(void)
>  {
>  bcm2835_get_board_spec_entries spec = { 0 };
> --
> 2.25.1
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH v2] bsp/raspberry: Add a bsp_fdt_map_intr().

[Christian Mauderer]

On 04/04/2020 19:10, Gedare Bloom wrote:
> Looks good, go ahead; thanks.

Thanks for the review. Pushed it.

> 
> On Sat, Apr 4, 2020 at 10:39 AM Christian Mauderer  wrote:
>>
>> From: Christian Mauderer 
>>
>> Fixes #3903
>> ---
>>  bsps/arm/raspberrypi/include/bsp/irq.h |  3 +++
>>  bsps/arm/raspberrypi/start/bspstart.c  | 24 
>>  2 files changed, 27 insertions(+)
>>
>> diff --git a/bsps/arm/raspberrypi/include/bsp/irq.h 
>> b/bsps/arm/raspberrypi/include/bsp/irq.h
>> index 6a9d05cba6..17e4472b34 100644
>> --- a/bsps/arm/raspberrypi/include/bsp/irq.h
>> +++ b/bsps/arm/raspberrypi/include/bsp/irq.h
>> @@ -35,6 +35,8 @@
>>
>>  #define BCM2835_INTC_TOTAL_IRQ   64 + 8
>>
>> +#define BCM2835_IRQ_SET1_MIN 0
>> +#define BCM2835_IRQ_SET2_MIN 32
>>
>>  #define BCM2835_IRQ_ID_GPU_TIMER_M0  0
>>  #define BCM2835_IRQ_ID_GPU_TIMER_M1  1
>> @@ -69,6 +71,7 @@
>>
>>  #define BSP_INTERRUPT_VECTOR_MIN(0)
>>  #define BSP_INTERRUPT_VECTOR_MAX(BCM2835_INTC_TOTAL_IRQ - 1)
>> +#define BSP_INTERRUPT_VECTOR_INVALID (UINT32_MAX)
>>
>>  #define BSP_IRQ_COUNT   (BCM2835_INTC_TOTAL_IRQ)
>>
>> diff --git a/bsps/arm/raspberrypi/start/bspstart.c 
>> b/bsps/arm/raspberrypi/start/bspstart.c
>> index 49896e4d47..8d7f6aa503 100644
>> --- a/bsps/arm/raspberrypi/start/bspstart.c
>> +++ b/bsps/arm/raspberrypi/start/bspstart.c
>> @@ -23,6 +23,7 @@
>>  #include 
>>  #include 
>>  #include 
>> +#include 
>>
>>  #include 
>>
>> @@ -101,6 +102,29 @@ void *raspberrypi_get_reg_of_node(const void *fdt, int 
>> node)
>>return (BUS_TO_PHY((void *) fdt32_to_cpu(val[0])));
>>  }
>>
>> +#ifdef BSP_FDT_IS_SUPPORTED
>> +uint32_t bsp_fdt_map_intr(const uint32_t *intr, size_t icells)
>> +{
>> +  uint32_t controller = intr[0];
>> +  uint32_t source = intr[1];
>> +
>> +  switch ( controller ) {
>> +case 0:
>> +return source + BCM2835_IRQ_ID_BASIC_BASE_ID;
>> +break;
>> +case 1:
>> +return source + BCM2835_IRQ_SET1_MIN;
>> +break;
>> +case 2:
>> +return source + BCM2835_IRQ_SET2_MIN;
>> +break;
>> +default:
>> +return BSP_INTERRUPT_VECTOR_INVALID;
>> +break;
>> +  }
>> +}
>> +#endif /* BSP_FDT_IS_SUPPORTED */
>> +
>>  void bsp_start(void)
>>  {
>>  bcm2835_get_board_spec_entries spec = { 0 };
>> --
>> 2.25.1
>>
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
> 
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Covid Code-In Update (4 April 2020)

[Joel Sherrill]

Hi

I hope this email finds you and your loved ones all well.  Thanks to
everyone who has submitted patches moving us to a release. Here in
Huntsville, it has been quiet at home with us working from home for over
two weeks. Today, a state-wide "stay home" order goes into effect.

The RTEMS Core Developers have been busy testing. There were over 1500 test
results posted to the bu...@rtems.org mailing list and over 300 so far in
April.

Here are some updates on potential small tasks to pass time.

+ Help knock down barriers to the upcoming release.
https://devel.rtems.org/milestone/5.1 has a list of all outstanding tickets.

+ If one of those tickets doesn't strike your fancy, just test on your BSP
and report that the git master is OK or not.  Even better, learn to run the
RTEMS Tester on your BSP and report full results. It will help move your
BSP up the tiers.

+ Chris Johns periodically posts release candidate snapshots. Test them.
Please.

+ There are more Small Tasks (https://devel.rtems.org/wiki/SmallTasks). I
am happy to report that there is progress in converting the useful BSP
specific content from the Wiki to the Users Guide and in filling in some
testing gaps. Thanks to those picking away at these. They are small but
important.

+ If you have a cool self-made mask, post a picture to the RTEMS Users
Facebook group. This is a creative group, let's see what you have done. :)

Follow medical expert advice and stay healthy.

Thanks.

--joel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH RSB 0/2] RSB removed used tools configuration files.

[Gedare Bloom]

These two patches demonstrate a bash script approach
to automate the removal of unused configuration (*.cfg)
files within the RSB.

See https://devel.rtems.org/ticket/3273


___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH RSB 1/2] Add clean-cfg.sh script to find and remove unused cfg files

[Gedare Bloom]

Closes #3273.
---
 clean-cfg.sh | 11 +++
 1 file changed, 11 insertions(+)
 create mode 100644 clean-cfg.sh

diff --git a/clean-cfg.sh b/clean-cfg.sh
new file mode 100644
index 000..cad678b
--- /dev/null
+++ b/clean-cfg.sh
@@ -0,0 +1,11 @@
+#!/bin/bash
+
+for f in `find . -name "*.cfg" -printf '%f\n' | sed -e 's/\.cfg//g'`
+do
+  ack -l $f > /dev/null
+  if [ ! $? -eq 0 ]
+  then
+find . -name ${f}.cfg | xargs git rm
+  fi
+done
+
-- 
2.17.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH RSB 1/2] Add clean-cfg.sh script to find and remove unused cfg files

[Gedare Bloom]

On Sat, Apr 4, 2020 at 1:29 PM Gedare Bloom  wrote:
>
> Closes #3273.
> ---
>  clean-cfg.sh | 11 +++
>  1 file changed, 11 insertions(+)
>  create mode 100644 clean-cfg.sh
>
> diff --git a/clean-cfg.sh b/clean-cfg.sh
> new file mode 100644
> index 000..cad678b
> --- /dev/null
> +++ b/clean-cfg.sh
> @@ -0,0 +1,11 @@
> +#!/bin/bash
> +
> +for f in `find . -name "*.cfg" -printf '%f\n' | sed -e 's/\.cfg//g'`
> +do
> +  ack -l $f > /dev/null
I'm using a little bit non-standard ack. I think this can be rewritten
with grep.

I don't know that we actually want to keep the script where it gets
run, but should have it around for reference to clean things up again
in the future?

> +  if [ ! $? -eq 0 ]
> +  then
> +find . -name ${f}.cfg | xargs git rm
> +  fi
> +done
> +
> --
> 2.17.1
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH RSB v2 1/2] Add clean-cfg.sh script to find and remove unused cfg files

[Gedare Bloom]

Updates #3273.
---
 clean-cfg.sh | 11 +++
 1 file changed, 11 insertions(+)
 create mode 100644 clean-cfg.sh

diff --git a/clean-cfg.sh b/clean-cfg.sh
new file mode 100644
index 000..eb3a82b
--- /dev/null
+++ b/clean-cfg.sh
@@ -0,0 +1,11 @@
+#!/bin/bash
+
+for f in `find . -name "*.cfg" -printf '%f\n' | sed -e 's/\.cfg//g'`
+do
+  grep -r $f > /dev/null
+  if [ ! $? -eq 0 ]
+  then
+find . -name ${f}.cfg | xargs git rm
+  fi
+done
+
-- 
2.17.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-tools] Add support to take version number from user

[Vijay Kumar Banerjee]

Closes #3671
---
 tester/rt/test.py| 6 +-
 tester/rtems/version.cfg | 6 +-
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/tester/rt/test.py b/tester/rt/test.py
index 16ac352..e0a47b4 100644
--- a/tester/rt/test.py
+++ b/tester/rt/test.py
@@ -367,7 +367,8 @@ def run(args, command_path = None):
 '--filter': 'Glob that executables must match to 
run (default: ' +
   default_exefilter + ')',
 '--stacktrace': 'Dump a stack trace on a user 
termination (^C)',
-'--coverage':   'Perform coverage analysis of test 
executables.'}
+'--coverage':   'Perform coverage analysis of test 
executables.',
+'--version':'Set version number to use 
non-standard tools.'}
 mailer.append_options(optargs)
 opts = options.load(args,
 optargs = optargs,
@@ -397,6 +398,9 @@ def run(args, command_path = None):
 check_report_formats(report_formats, report_location)
 else:
 report_formats = []
+usr_version = opts.find_arg('--version')
+if usr_version:
+opts.defaults['__version'] = usr_version[1]
 log.notice('RTEMS Testing - Tester, %s' % (version.string()))
 if opts.find_arg('--list-bsps'):
 bsps.list(opts)
diff --git a/tester/rtems/version.cfg b/tester/rtems/version.cfg
index 2cd9073..caf9d9e 100644
--- a/tester/rtems/version.cfg
+++ b/tester/rtems/version.cfg
@@ -32,4 +32,8 @@
 # RTEMS Version
 #
 
-%define rtems_version 5
+%ifn %{defined __version}
+ %define rtems_version 5
+%else
+ %define rtems_version %{__version}
+%endif
-- 
2.21.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-tools] rtemstoolkit: add override option for rtems_version

[Gedare Bloom]

Use in tester to allow defining custom rtems_version
to use in tools.

Closes #3671.
---
 rtemstoolkit/options.py  | 1 +
 tester/rtems/version.cfg | 4 +++-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/rtemstoolkit/options.py b/rtemstoolkit/options.py
index 32a7016..e991bc8 100644
--- a/rtemstoolkit/options.py
+++ b/rtemstoolkit/options.py
@@ -80,6 +80,7 @@ class command_line(object):
 self.long_opts = {
 # key macrohandler
param  defs   init
 '--jobs'   : ('_jobs', self._lo_jobs, 
True,  'default', True),
+'--rtems-version'  : ('rtems_version', self._lo_string,  
True, None,   False),
 '--log': ('_logfile',  self._lo_string,   
True,  None,  False),
 '--macros' : ('_macros',   self._lo_string,   
True,  None,  False),
 '--force'  : ('_force',self._lo_bool, 
False, '0',   True),
diff --git a/tester/rtems/version.cfg b/tester/rtems/version.cfg
index 2cd9073..0ca057e 100644
--- a/tester/rtems/version.cfg
+++ b/tester/rtems/version.cfg
@@ -32,4 +32,6 @@
 # RTEMS Version
 #
 
-%define rtems_version 5
+%if ! %{defined rtems_version}
+  %define rtems_version 5
+%endif
-- 
2.17.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH rtems-tools] rtemstoolkit: add override option for rtems_version

[Vijay Kumar Banerjee]

On Sun, Apr 5, 2020, 3:55 AM Vijay Kumar Banerjee 
wrote:

>
>
> On Sun, Apr 5, 2020, 3:45 AM Gedare Bloom  wrote:
>
>> Use in tester to allow defining custom rtems_version
>> to use in tools.
>>
>> Closes #3671.
>>
>
> Looks like someone else was also chasing this bug with a similar approach
> ;)
> https://lists.rtems.org/pipermail/devel/2020-April/059001.html
>
>
>
> ---
>>  rtemstoolkit/options.py  | 1 +
>>  tester/rtems/version.cfg | 4 +++-
>>  2 files changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/rtemstoolkit/options.py b/rtemstoolkit/options.py
>> index 32a7016..e991bc8 100644
>> --- a/rtemstoolkit/options.py
>> +++ b/rtemstoolkit/options.py
>> @@ -80,6 +80,7 @@ class command_line(object):
>>  self.long_opts = {
>>  # key macrohandler
>>   param  defs   init
>>  '--jobs'   : ('_jobs', self._lo_jobs,
>>  True,  'default', True),
>> +'--rtems-version'  : ('rtems_version', self._lo_string,
>> True, None,   False),
>>  '--log': ('_logfile',  self._lo_string,
>>  True,  None,  False),
>>  '--macros' : ('_macros',   self._lo_string,
>>  True,  None,  False),
>>  '--force'  : ('_force',self._lo_bool,
>>  False, '0',   True),
>> diff --git a/tester/rtems/version.cfg b/tester/rtems/version.cfg
>> index 2cd9073..0ca057e 100644
>> --- a/tester/rtems/version.cfg
>> +++ b/tester/rtems/version.cfg
>> @@ -32,4 +32,6 @@
>>  # RTEMS Version
>>  #
>>
>> -%define rtems_version 5
>> +%if ! %{defined rtems_version}
>> +  %define rtems_version 5
>> +%endif
>> --
>> 2.17.1
>>
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH rtems-tools] rtemstoolkit: add override option for rtems_version

[Gedare Bloom]

On Sat, Apr 4, 2020 at 4:25 PM Vijay Kumar Banerjee
 wrote:
>
>
>
> On Sun, Apr 5, 2020, 3:45 AM Gedare Bloom  wrote:
>>
>> Use in tester to allow defining custom rtems_version
>> to use in tools.
>>
>> Closes #3671.
>
>
> Looks like someone else was also chasing this bug with a similar approach ;)
> https://lists.rtems.org/pipermail/devel/2020-April/059001.html
>
Yeah, we could have collaborated on IRC! :)

Am discussing briefly the approaches taken with Chris.

>
>
>> ---
>>  rtemstoolkit/options.py  | 1 +
>>  tester/rtems/version.cfg | 4 +++-
>>  2 files changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/rtemstoolkit/options.py b/rtemstoolkit/options.py
>> index 32a7016..e991bc8 100644
>> --- a/rtemstoolkit/options.py
>> +++ b/rtemstoolkit/options.py
>> @@ -80,6 +80,7 @@ class command_line(object):
>>  self.long_opts = {
>>  # key macrohandler
>> param  defs   init
>>  '--jobs'   : ('_jobs', self._lo_jobs, 
>> True,  'default', True),
>> +'--rtems-version'  : ('rtems_version', self._lo_string, 
>>  True, None,   False),
>>  '--log': ('_logfile',  self._lo_string,   
>> True,  None,  False),
>>  '--macros' : ('_macros',   self._lo_string,   
>> True,  None,  False),
>>  '--force'  : ('_force',self._lo_bool, 
>> False, '0',   True),
>> diff --git a/tester/rtems/version.cfg b/tester/rtems/version.cfg
>> index 2cd9073..0ca057e 100644
>> --- a/tester/rtems/version.cfg
>> +++ b/tester/rtems/version.cfg
>> @@ -32,4 +32,6 @@
>>  # RTEMS Version
>>  #
>>
>> -%define rtems_version 5
>> +%if ! %{defined rtems_version}
>> +  %define rtems_version 5
>> +%endif
>> --
>> 2.17.1
>>
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [rtems commit] score: Fix _ISR_Stack_area_end

[Chris Johns]

On 2020-04-04 00:49, Sebastian Huber wrote:

Module:rtems
Branch:master
Commit:8e80876bdd54e36fb668eee655eec1dd588daf13
Changeset: 
http://git.rtems.org/rtems/commit/?id=8e80876bdd54e36fb668eee655eec1dd588daf13


Buildbot is showing this has broken master for some BSP ...

https://buildbot.rtems.org/#/builders/16/builds/111

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH rtems-tools] rtemstoolkit: add override option for rtems_version

[Gedare Bloom]

On Sat, Apr 4, 2020 at 4:28 PM Gedare Bloom  wrote:
>
> On Sat, Apr 4, 2020 at 4:25 PM Vijay Kumar Banerjee
>  wrote:
> >
> >
> >
> > On Sun, Apr 5, 2020, 3:45 AM Gedare Bloom  wrote:
> >>
> >> Use in tester to allow defining custom rtems_version
> >> to use in tools.
> >>
> >> Closes #3671.
> >
> >
> > Looks like someone else was also chasing this bug with a similar approach ;)
> > https://lists.rtems.org/pipermail/devel/2020-April/059001.html
> >
> Yeah, we could have collaborated on IRC! :)
>
> Am discussing briefly the approaches taken with Chris.
>

After IRC discussion, we think the approach should be a little more
rigorous. An idea to pursue is to provide a way to align the ini/cfg
files to be able to use the triplet in rtems-tool. This would be both
more flexible but also should be more easily checked for correctness.
It will require probably rewriting the 25 or so cfg/ini files that use
the %rtems_version macro, and eliminate the macro.

> >
> >
> >> ---
> >>  rtemstoolkit/options.py  | 1 +
> >>  tester/rtems/version.cfg | 4 +++-
> >>  2 files changed, 4 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/rtemstoolkit/options.py b/rtemstoolkit/options.py
> >> index 32a7016..e991bc8 100644
> >> --- a/rtemstoolkit/options.py
> >> +++ b/rtemstoolkit/options.py
> >> @@ -80,6 +80,7 @@ class command_line(object):
> >>  self.long_opts = {
> >>  # key macrohandler
> >> param  defs   init
> >>  '--jobs'   : ('_jobs', self._lo_jobs, 
> >> True,  'default', True),
> >> +'--rtems-version'  : ('rtems_version', self._lo_string,   
> >>True, None,   False),
> >>  '--log': ('_logfile',  self._lo_string,   
> >> True,  None,  False),
> >>  '--macros' : ('_macros',   self._lo_string,   
> >> True,  None,  False),
> >>  '--force'  : ('_force',self._lo_bool, 
> >> False, '0',   True),
> >> diff --git a/tester/rtems/version.cfg b/tester/rtems/version.cfg
> >> index 2cd9073..0ca057e 100644
> >> --- a/tester/rtems/version.cfg
> >> +++ b/tester/rtems/version.cfg
> >> @@ -32,4 +32,6 @@
> >>  # RTEMS Version
> >>  #
> >>
> >> -%define rtems_version 5
> >> +%if ! %{defined rtems_version}
> >> +  %define rtems_version 5
> >> +%endif
> >> --
> >> 2.17.1
> >>
> >> ___
> >> devel mailing list
> >> devel@rtems.org
> >> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH rtems-tools] rtemstoolkit: add override option for rtems_version

[Chris Johns]

On 2020-04-05 11:28, Gedare Bloom wrote:

On Sat, Apr 4, 2020 at 4:28 PM Gedare Bloom  wrote:


On Sat, Apr 4, 2020 at 4:25 PM Vijay Kumar Banerjee
 wrote:




On Sun, Apr 5, 2020, 3:45 AM Gedare Bloom  wrote:


Use in tester to allow defining custom rtems_version
to use in tools.

Closes #3671.



Looks like someone else was also chasing this bug with a similar approach ;)
https://lists.rtems.org/pipermail/devel/2020-April/059001.html


Yeah, we could have collaborated on IRC! :)

Am discussing briefly the approaches taken with Chris.



After IRC discussion, we think the approach should be a little more
rigorous. An idea to pursue is to provide a way to align the ini/cfg
files to be able to use the triplet in rtems-tool. This would be both
more flexible but also should be more easily checked for correctness.
It will require probably rewriting the 25 or so cfg/ini files that use
the %rtems_version macro, and eliminate the macro.


Yes, I think a way to update or set macros via the INI files. I think 
this needs to wait until after RTEMS 5 has been branched.


I would at macro maps and then a way to have INI files create and update 
macro maps. This lets you layer specialised versions.


Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH v2] sb/reports: add sanitize parameter enabled for --mail

[Gedare Bloom]

Adds a --sanitize option to command line for reports.py
and also for the reports.report() interface from setbuilder.py
to remove the Remotes information from git.

Closes #3887.
---
 source-builder/sb/reports.py| 52 +
 source-builder/sb/setbuilder.py |  4 +--
 2 files changed, 35 insertions(+), 21 deletions(-)

diff --git a/source-builder/sb/reports.py b/source-builder/sb/reports.py
index ab20671..e7870c4 100644
--- a/source-builder/sb/reports.py
+++ b/source-builder/sb/reports.py
@@ -241,13 +241,16 @@ class markdown_formatter(formatter):
 self.line(self._strong('Remotes:'))
 self.line('')
 rc = 1
-for r in remotes:
-if 'url' in remotes[r]:
-text = remotes[r]['url']
-else:
-text = 'no URL found'
-self.line('%d. %s: %s' % (rc, r, text))
-rc += 1
+if not remotes:
+self.line('[ remotes removed, contact sender for details ]')
+else:
+for r in remotes:
+if 'url' in remotes[r]:
+text = remotes[r]['url']
+else:
+text = 'no URL found'
+self.line('%d. %s: %s' % (rc, r, text))
+rc += 1
 self.line('')
 self.line(self._strong('Status:'))
 self.line('')
@@ -427,14 +430,17 @@ class text_formatter(formatter):
 if valid:
 self.line('%s Remotes:' % (self.cini))
 rc = 0
-for r in remotes:
-rc += 1
-if 'url' in remotes[r]:
-text = remotes[r]['url']
-else:
-text = 'no URL found'
-text = '%s: %s' % (r, text)
-self.line('%s  %2d: %s' % (self.cini, rc, text))
+if not remotes:
+self.line('[ remotes removed, contact sender for details ]')
+else:
+for r in remotes:
+rc += 1
+if 'url' in remotes[r]:
+text = remotes[r]['url']
+else:
+text = 'no URL found'
+text = '%s: %s' % (r, text)
+self.line('%s  %2d: %s' % (self.cini, rc, text))
 self.line('%s Status:' % (self.cini))
 if dirty:
 self.line('%s  Repository is dirty' % (self.cini))
@@ -603,7 +609,7 @@ def _merge(_dict, new):
 class report:
 """Report the build details about a package given a config file."""
 
-def __init__(self, formatter, _configs, opts, macros = None):
+def __init__(self, formatter, sanitize, _configs, opts, macros = None):
 if type(formatter) == str:
 if formatter == 'text':
 self.formatter = text_formatter()
@@ -621,6 +627,7 @@ class report:
 self.formatter = formatter
 self.configs = _configs
 self.opts = opts
+self.sanitize = sanitize
 if macros is None:
 self.macros = opts.defaults
 else:
@@ -649,7 +656,10 @@ class report:
 
 def git_status(self):
 r = git.repo('.', self.opts, self.macros)
-self.formatter.git_status(r.valid(), r.dirty(), r.head(), r.remotes())
+if self.sanitize:
+self.formatter.git_status(r.valid(), r.dirty(), r.head(), None)
+else:
+self.formatter.git_status(r.valid(), r.dirty(), r.head(), 
r.remotes())
 
 def introduction(self, name, intro_text = None):
 now = datetime.datetime.now().ctime()
@@ -892,7 +902,8 @@ def run(args):
 optargs = { '--list-bsets':   'List available build sets',
 '--list-configs': 'List available configurations',
 '--format':   'Output format (text, html, markdown, 
ini, xml)',
-'--output':   'File name to output the report' }
+'--output':   'File name to output the report',
+'--sanitize': 'Remove Remotes information from report'}
 opts = options.load(args, optargs, logfile = False)
 if opts.get_arg('--output') and len(opts.params()) > 1:
 raise error.general('--output can only be used with a single 
config')
@@ -922,7 +933,10 @@ def run(args):
 formatter = xml_formatter()
 else:
 raise error.general('invalid format: %s' % (format_opt[1]))
-r = report(formatter, configs, opts)
+sanitize = False
+if opts.get_arg('--sanitize'):
+sanitize = True
+r = report(formatter, sanitize, configs, opts)
 for _config in opts.params():
 if output is None:
 outname = path.splitext(_config)[0] + formatter.ext()
diff --git a/source-builder/sb

Re: [PATCH v5] Chapter-on-need-for-RTEMS-specific-cross-compiler

[Gedare Bloom]

Pushed, thank you for your contribution!

On Fri, Apr 3, 2020 at 9:46 PM Utkarsh Rai  wrote:
>
> Removed '-' character and provided definition list format
> ---
>  user/start/tools.rst | 33 +
>  1 file changed, 33 insertions(+)
>
> diff --git a/user/start/tools.rst b/user/start/tools.rst
> index c3f039b..1d83062 100644
> --- a/user/start/tools.rst
> +++ b/user/start/tools.rst
> @@ -3,6 +3,7 @@
>  .. Copyright (C) 2019 embedded brains GmbH
>  .. Copyright (C) 2019 Sebastian Huber
>  .. Copyright (C) 2020 Chris Johns
> +.. Copyright (C) 2020 Utkarsh Rai
>
>  .. _QuickStartTools:
>
> @@ -76,3 +77,35 @@ source code used.
>
>
>  Add ``--verbose`` to the GCC command for the the verbose version details.
> +
> +Need for RTEMS-Specific Cross-Compiler
> +-
> +
> +New users are often confused as to why they cannot use their distribution's
> +cross-compiler for their target on rtems, e.g., the riscv64-linux-gnu or the
> +arm-none-eabi-gcc on RTEMS. Below mentioned are some of the reasons for using
> +the RTEMS cross-compiler.
> +
> + Correct configuration of Newlib
> + Newlib is a C standard library implementation intended for use on 
> embedded
> + systems. Most of the POSIX and libc support for RTEMS is derived from
> + Newlib. The RTEMS cross-compiler configures Newlib correctly for RTEMS.
> +
> + Threading in GCC support libraries
> + Several threading packages in GCC such as Go threads (libgo), OpenMP
> + (libgomp), and OpenACC need to be customized according to RTEMS. This is
> + done by the RTEMS specific cross-compiler.
> +
> + Provide preprocessor define __rtems__
> + The  ``__rtems__``  preprocessor define is used to provide conditional 
> code
> + compilation in source files that are shared with other projects e.g. in
> + Newlib or imported code from FreeBSD.
> +
> + Multilib variants to match the BSP
> + RTEMS configures GCC to create separate runtime libraries for each
> + supported instruction set, floating point unit, vector unit, word size
> + (e.g. 32-bit and 64-bit), endianness, ABI, processor errata workarounds,
> + and so on in the architecture. These libraries are termed as 
> :ref:`Multilib
> + ` variants. Multilib variants to match the BSP are 
> set
> + by selecting a specific set of machine options using the RTEMS
> + cross-compiler.
> --
> 2.17.1
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH] user: update copyright and minor typo

[Gedare Bloom]

---
 user/index.rst   | 1 +
 user/start/tools.rst | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/user/index.rst b/user/index.rst
index 5c39cca..0e6e886 100644
--- a/user/index.rst
+++ b/user/index.rst
@@ -11,6 +11,7 @@ RTEMS User Manual (|version|).
 .. topic:: Copyrights and License
 
 | |copy| 2020 Niteesh Babu
+| |copy| 2020 Utkarsh Rai
 | |copy| 2019 Vijay Kumar Banerjee
 | |copy| 2018 Amaan Cheval
 | |copy| 2018 Marçal Comajoan Cara
diff --git a/user/start/tools.rst b/user/start/tools.rst
index 1d83062..baa2387 100644
--- a/user/start/tools.rst
+++ b/user/start/tools.rst
@@ -82,8 +82,8 @@ Need for RTEMS-Specific Cross-Compiler
 -
 
 New users are often confused as to why they cannot use their distribution's
-cross-compiler for their target on rtems, e.g., the riscv64-linux-gnu or the
-arm-none-eabi-gcc on RTEMS. Below mentioned are some of the reasons for using
+cross-compiler for their target on RTEMS, e.g., the riscv64-linux-gnu or the
+arm-none-eabi-gcc. Below mentioned are some of the reasons for using
 the RTEMS cross-compiler.
 
  Correct configuration of Newlib
-- 
2.17.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] user: update copyright and minor typo

[Gedare Bloom]

Sorry, this is a mistake one, already been pushed ignore..

On Sat, Apr 4, 2020 at 10:43 PM Gedare Bloom  wrote:
>
> ---
>  user/index.rst   | 1 +
>  user/start/tools.rst | 4 ++--
>  2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/user/index.rst b/user/index.rst
> index 5c39cca..0e6e886 100644
> --- a/user/index.rst
> +++ b/user/index.rst
> @@ -11,6 +11,7 @@ RTEMS User Manual (|version|).
>  .. topic:: Copyrights and License
>
>  | |copy| 2020 Niteesh Babu
> +| |copy| 2020 Utkarsh Rai
>  | |copy| 2019 Vijay Kumar Banerjee
>  | |copy| 2018 Amaan Cheval
>  | |copy| 2018 Marçal Comajoan Cara
> diff --git a/user/start/tools.rst b/user/start/tools.rst
> index 1d83062..baa2387 100644
> --- a/user/start/tools.rst
> +++ b/user/start/tools.rst
> @@ -82,8 +82,8 @@ Need for RTEMS-Specific Cross-Compiler
>  -
>
>  New users are often confused as to why they cannot use their distribution's
> -cross-compiler for their target on rtems, e.g., the riscv64-linux-gnu or the
> -arm-none-eabi-gcc on RTEMS. Below mentioned are some of the reasons for using
> +cross-compiler for their target on RTEMS, e.g., the riscv64-linux-gnu or the
> +arm-none-eabi-gcc. Below mentioned are some of the reasons for using
>  the RTEMS cross-compiler.
>
>   Correct configuration of Newlib
> --
> 2.17.1
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH] user/rsb: describe how to create configuration reports

[Gedare Bloom]

Closes #3629.
---
 user/rsb/configuration.rst | 21 ++---
 1 file changed, 18 insertions(+), 3 deletions(-)

diff --git a/user/rsb/configuration.rst b/user/rsb/configuration.rst
index 8c8c87f..7ad58ed 100644
--- a/user/rsb/configuration.rst
+++ b/user/rsb/configuration.rst
@@ -364,11 +364,26 @@ points to are loaded. The second is a file called 
``.rsb_macros`` in your home
 directory. You need to have the environment variable ``HOME`` defined for this
 work.
 
+Configuration Reports
+^
+
+A configuration report detailing a build configuration is generated by the
+``sb-set-builder`` command. The report can also be generated separately from
+the build process by invoking the ``sb-report`` command on the build set used
+for the build, for example:
+
+.. code-block:: shell
+
+  cd rtems
+  ../source-builder/sb-reports 5/rtems-sparc
+  less 5-rtems-sparc.txt
+
 Report Mailing
-^^
+~~
 
-The build reports can be mailed to a specific email address to logging and
-monitoring. Mailing requires a number of parameters to function. These are:
+Configuration reports from a build can be mailed to a specific email address
+for logging and monitoring. Mailing requires a number of parameters to
+function. These are:
 
 - To mail address
 
-- 
2.17.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: rtems-boot-image tool: Raspberry Pi

[G. S. Niteesh]

Hii,
It has been quite a few days since the last mail.
Chris, can you please take a look at this when you are free?

Thanks,
Niteesh

On Mon, Mar 23, 2020 at 1:23 AM Christian Mauderer 
wrote:

> Hello Niteesh,
>
> thanks for the (private) remainder. This thread really stopped quite
> some time ago. A lot of us are quite busy right now but that shouldn't
> happen. If you don't get a response for some question: Please give it
> about a week of time and then just ping the thread.
>
> On 05/03/2020 11:06, G. S. Niteesh wrote:
> > On Wed, Feb 26, 2020 at 8:39 AM Chris Johns  > > wrote:
> >
> > On 22/2/20 1:45 am, G. S. Niteesh wrote:
> > > Hi,
> > >
> > > This is regarding adding RPi support to the boot image generation
> > tool.
> > >
> > > The boot process for Raspberry Pi is very unconventional. The GPU
> > starts
> > > first, initializes RAM, other hardware, loads the bootloaders and
> > then starts
> > > the ARM CPU.
> > >
> > > The minimum files that are required to boot an RPi are
> > > bootcode.bin, startx.elf, fixup.dat, kernel.img, config.txt
> > > There are also other variants of startx.elf and fixup.dat.
> > > Please have a look
> > >
> > at
> https://www.raspberrypi.org/documentation/configuration/config-txt/boot.md
> > > for information on the variants.
> > >
> > > From what I have tried on my Rpi3 model b v1.2 the minimum files
> > that are
> > > required are start_x.elf, fixup_x.dat, bootcode.bin, kernel.img,
> > config.txt
> > > But for this to work, we must add start_x=1 to config.txt because
> > by default
> > > start.elf is loaded.
> >
> > Hello Chris,
> >
> >
> > I would have look at how the tool maps to RPi to know if it needs
> > more work :)
> >
> >
> > Did you take a look at it?
>
> Chris is most likely too busy with the release right now.
>
> >
> > In my opinion, there are two ways to do it.
> > The first would be to modify the U-Boot bootloader object to have a
> > files field
> > to make sure the user provides all the necessary files(fixup.dat,
> > startx.elf, config.txt).
> > So after this change the rtems-boot.ini for RPI should look something
> > like this
> > [u-boot-raspberrypi]
> > uses = u-boot-arm-raspberrypi
> > ..
> > ..
> > first_stage = %{ubootdir}/bootcode.bin
> > boot_device = mmc 0
> > second_stage = uboot or startx
> > files = [config.txt, fixup.dat etc]
> > But also please keep in mind that if we want to support RPi4 then the
> > first_stage
> > will start4x.elf since bootcode.bin is now replaced by code in the
> > EEPROM in RPi4 SOC.
>
> As far as I understand that approach it more or less tells: To start a
> raspberry you need U-Boot. U-Boot needs the fixup.dat, startx.elf and
> config.txt to boot. But that sounds a bit wrong. On Raspberry U-Boot is
> purely optional, isn't it? So from a high-level view it would be more a
>
> - Raspberry needs fixup.dat, startx.elf and config.txt
> - That can start either:
>   - an application or
>   - an U-Boot which can then start an application (or do other things)
>
> >
> > Another approach will be to create the default Raspberry Pi bootloader
> > object. But having
> > support for U-Boot is important since it will allow for automatic
> testing.
>
> That approach sounds more correct. But I don't really know the
> rtems-boot-image tool. That makes it a lot harder for me to tell whether
> that approach works well. From that ignorant position I would say that
> it would be nice to have a boot-image command that can be called with or
> without a option (like --with-u-boot). Alternatively maybe two targets
> would be possible. One raspiboot-u-boot-pi1 and one raspiboot-raw-pi1.
>
> But your best bet might is to wait for Chris to get free again and
> answer that question. He knows the boot image tool and can tell you a
> lot better which concept works best.
>
> Best regards
>
> Christian
>
> >
> > Which one do you think is a better approach?
> >
> > Thank you.
> >
> >
> > >
> > > So, what should be the values for the first and second stages in
> > rtems-boot.ini
> > > for Rpi?
> >
> > Would this be bootcode.bin?
> >
> > > And also wouldn't it be nice if we could add a files field, which
> > will copy the
> > > specified files to the image? This would save a lot of typing in
> > case of RPi
> >
> > Do you have an example?
> >
> > Chris
> >
> >
> > ___
> > devel mailing list
> > devel@rtems.org
> > http://lists.rtems.org/mailman/listinfo/devel
> >
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel