On 2/5/2024 7:18 am, Cedric Berger wrote:
> Hello,
>
> On 25.04.2024 02:16, Chris Johns wrote:
>> I know I am getting ahead of myself but once we have GiLab running and you
>> have
>> a patch you would like merged please make a merge request.
>
> Done:
>
>
Hello,
On 25.04.2024 02:16, Chris Johns wrote:
I know I am getting ahead of myself but once we have GiLab running and you have
a patch you would like merged please make a merge request.
Done:
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/10
It worked really well.
Cedric
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
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
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
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
