Re: RTEMS 6 branching

> On Apr 23, 2024, at 5:45 PM, Vijay Kumar Banerjee wrote: > > > > On Tue, Apr 23, 2024 at 1:02 PM Joel Sherrill wrote: > > > On Tue, Apr 23, 2024, 12:56 PM Sebastian Huber > wrote: > - Am 21. Apr 2024 um 3:00 schrieb Chris Johns chr...@rtems.org: > > > Hi, > > > > There has been s

Cortex-M floating point (Was: RTEMS 6 branching)

Hello Sebastian, On 23.04.2024 19:56, Sebastian Huber wrote: 1. Are all the things need for the release resolved? Tickets reviewed? It would be nice to have the interrupt get/set priority API in RTEMS 6. The Cortex-M floating point issue is not yet fixed in the RTEMS master. Do you have any

Re: RTEMS 6 branching

On Wed, Apr 24, 2024 at 6:43 AM Peter Dufault wrote: > > On Apr 23, 2024, at 5:45 PM, Vijay Kumar Banerjee > wrote: > > On Tue, Apr 23, 2024 at 1:02 PM Joel Sherrill wrote: > > > > > > On Tue, Apr 23, 2024, 12:56 PM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > > - Am 21.

Re: RTEMS 6 branching

> On Apr 24, 2024, at 9:27 AM, Kinsey Moore wrote: > > That use case definitely wasn't considered for rtems-lwip and I don't know > that it's ever been discussed. If that were intended, I'd expect a "./waf > uninstall" target to exist that would remove the installed network stack so > that y

Re: [PATCH] bsps/aarch64/raspberrypi: Add system timer support

Looks good, thanks! Kinsey On Tue, Apr 16, 2024 at 5:20 AM Ning Yang wrote: > The clock from the ARM timer is derived from the system clock. This clock > can > change dynamically e.g. if the system goes into reduced power or in low > power > mode. Thus the clock speed adapts to the overall syst

Re: RTEMS 6 branching

On 25/4/2024 12:06 am, Peter Dufault wrote: >> On Apr 24, 2024, at 9:27 AM, Kinsey Moore wrote: >> >> That use case definitely wasn't considered for rtems-lwip and I don't know >> that it's ever been discussed. If that were intended, I'd expect a "./waf >> uninstall" target to exist that would r

Re: Cortex-M floating point (Was: RTEMS 6 branching)

On 24/4/2024 10:37 pm, Cedric Berger wrote: > Hello Sebastian, > > On 23.04.2024 19:56, Sebastian Huber wrote: >>> 1. Are all the things need for the release resolved? Tickets reviewed? >> It would be nice to have the interrupt get/set priority API in RTEMS 6. The >> Cortex-M floating point issue

Re: Cortex-M floating point (Was: RTEMS 6 branching)

On 24/4/2024 10:37 pm, Cedric Berger wrote: > Hello Sebastian, > > On 23.04.2024 19:56, Sebastian Huber wrote: >>> 1. Are all the things need for the release resolved? Tickets reviewed? >> It would be nice to have the interrupt get/set priority API in RTEMS 6. The >> Cortex-M floating point issue

Re: Introduction and preparation for the "Add BSP for Polarfire based Beagle" Project

(Adding devel back in the CC) On Wed, Apr 24, 2024 at 1:34 AM Purva Yeshi wrote: > Please feel free to call me Vijay :) > > Sure. > > That's great! You might be able to relate some of the documentation to the >> riscv BSP code in the repository. > > Yes, and I also added examples related to risc

Re: Cortex-M floating point (Was: RTEMS 6 branching)

On 24.04.24 14:37, Cedric Berger wrote: Hello Sebastian, On 23.04.2024 19:56, Sebastian Huber wrote: 1. Are all the things need for the release resolved? Tickets reviewed? It would be nice to have the interrupt get/set priority API in RTEMS 6. The Cortex-M floating point issue is not yet fixe

Re: [PATCH v2] rtems: Add get/set interrupt priorities

On 16.04.24 07:25, Sebastian Huber wrote: On 09.04.24 16:28, Sebastian Huber wrote: Add directives to get and set the priority of an interrupt vector. Implement the directives for the following BSP families: * arm/lpc24xx * arm/lpc32xx * powerpc/mpc55xxevb * powerpc/qoriq Implement the direct