Re: Booting a rtems exe on Zynq UltraScale+ MPSoC ZCU106 board

Thanks! Can I get rtems to build images as an AArch64 code, so that I don't have to change anything for uboot? On Thu, Apr 15, 2021 at 12:01 AM Kinsey Moore wrote: > That exception dump doesn't say a lot other than the ELR pointing at the > very first instruction in your image, so I suspect

Re: [PATCH v1 1/3] cpukit: Add signal mapping support

On 19/4/21 9:23 am, Joel Sherrill wrote: > > > On Sun, Apr 18, 2021, 5:13 PM Chris Johns > wrote: > > On 17/4/21 10:00 am, Kinsey Moore wrote: > > On 4/16/2021 08:48, Gedare Bloom wrote: > >> On Fri, Apr 16, 2021 at 1:19 AM Sebastian Huber > >>

Re: [PATCH v1 1/3] cpukit: Add signal mapping support

On Sun, Apr 18, 2021, 5:13 PM Chris Johns wrote: > On 17/4/21 10:00 am, Kinsey Moore wrote: > > On 4/16/2021 08:48, Gedare Bloom wrote: > >> On Fri, Apr 16, 2021 at 1:19 AM Sebastian Huber > >> wrote: > >>> Hello Kinsey, > >>> > >>> why don't you use a fatal error extension for this? You can

Re: OS Neutrality in Python Development Guidelines?

On Sun, Apr 18, 2021, 5:29 PM Chris Johns wrote: > On 16/4/21 3:28 pm, Sebastian Huber wrote: > > On 15/04/2021 22:58, Gedare Bloom wrote: > >> I guess we should define something to add here? Is anything written > >> somewhere we can adopt? > > the spirit of the Python guide is to have rules

Re: [PATCH v1] c-user: Add documentation for exception mapping

On 16/4/21 11:19 pm, Sebastian Huber wrote: > On 16/04/2021 15:05, Kinsey Moore wrote: > >> Yes, that's currently the case for non-aarch64 platforms. The test is set to >> require aarch64 as a result. > > How do you get this information from the documentation? > > In case this is something

Re: OS Neutrality in Python Development Guidelines?

On 16/4/21 3:28 pm, Sebastian Huber wrote: > On 15/04/2021 22:58, Gedare Bloom wrote: >> I guess we should define something to add here? Is anything written >> somewhere we can adopt? > the spirit of the Python guide is to have rules which are enforced by tools. I see a guide as a means to

Re: [PATCH v1 1/3] cpukit: Add signal mapping support

On 17/4/21 10:00 am, Kinsey Moore wrote: > On 4/16/2021 08:48, Gedare Bloom wrote: >> On Fri, Apr 16, 2021 at 1:19 AM Sebastian Huber >> wrote: >>> Hello Kinsey, >>> >>> why don't you use a fatal error extension for this? You can save all the >>> processor state to a structure and use it to jump

Re: [PATCH v1 2/3] aarch64: Add support for mapping exceptions

On 18/4/21 8:40 am, Joel Sherrill wrote: > > > On Sat, Apr 17, 2021, 4:27 PM Gedare Bloom > wrote: > > On Sat, Apr 17, 2021 at 8:10 AM Joel Sherrill > wrote: > > > > > > > > On Sat, Apr 17, 2021, 8:25 AM Gedare Bloom

Re: [PATCH RTEMS v2 0/1] bsp/beagle: Refactored i2c driver and Updated

Hello Niteesh, looks good to me. I'll wait two or three days before pushing so that others can review the libbsd patch too. Please ping me on Wednesday if I didn't push it by then. Best regards Christian On 18/04/2021 17:19, Niteesh G. S. wrote: Hello Christian, On Sun, Apr 18, 2021 at

Re: [PATCH RTEMS v2 0/1] bsp/beagle: Refactored i2c driver and Updated

Hello Christian, On Sun, Apr 18, 2021 at 4:54 PM Christian Mauderer wrote: > Hello Niteesh, > > sorry for not taking a look earlier. > No problem > > The patches seem OK for me. Just a tiny change request: > > I know that I suggested the "rtems,path" for the device tree. When > testing I noted

[PATCH libBSD] iicbus/rtems-i2c.c: Add rtems, path as an additional bus path

Adds "rtems,path" as an additional bus path for the i2c driver. Previously the bus path was provided in "rtems,i2c-path" property only. --- rtemsbsd/sys/dev/iicbus/rtems-i2c.c | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/rtemsbsd/sys/dev/iicbus/rtems-i2c.c

Re: [PATCH RTEMS v2 0/1] bsp/beagle: Refactored i2c driver and Updated

Hello Niteesh, sorry for not taking a look earlier. The patches seem OK for me. Just a tiny change request: I know that I suggested the "rtems,path" for the device tree. When testing I noted that we have the rtems-i2c driver in libbsd which is more or less just a compatibility layer between