rds,
Jan
-Original Message-
From: devel On Behalf Of
gabriel.moy...@dlr.de
Sent: Tuesday, April 13, 2021 10:09 AM
To: Moyano Heredia, Victor Gabriel ;
ged...@rtems.org
Cc: devel@rtems.org
Subject: AW: [PATCH 0/1] grlib/genirq: Issue when enabling/disabling
interrupt
Yes, rtems 5 also
13, 2021 10:09 AM
> To: Moyano Heredia, Victor Gabriel ;
> ged...@rtems.org
> Cc: devel@rtems.org
> Subject: AW: [PATCH 0/1] grlib/genirq: Issue when enabling/disabling
> interrupt
>
> >Yes, rtems 5 also has it. I can create a ticket.
>
> Here is the link to the
>Yes, rtems 5 also has it. I can create a ticket.
Here is the link to the ticket https://devel.rtems.org/ticket/4385#ticket.
BTW the proposed solution for the master branch can be also applied to 5 as
well.
>Regarding the proposed solution, I wanted to start a thread for discussing it
>(maybe t
Yes, rtems 5 also has it. I can create a ticket.
Regarding the proposed solution, I wanted to start a thread for discussing it
(maybe there is better was to do it).
>Is this a bug in rtems 5 also?
>
>If so, does it warrant a back-port fix and a ticket?
>
>On Mon, Apr 12, 2021 at 3:16 AM Moyano,
Is this a bug in rtems 5 also?
If so, does it warrant a back-port fix and a ticket?
On Mon, Apr 12, 2021 at 3:16 AM Moyano, Gabriel wrote:
>
> Hello everyone,
>
> I've found what can be an issue in the function genirq_set_active(): under
> some conditions it can return a value greater than 1.
>
Hello everyone,
I've found what can be an issue in the function genirq_set_active(): under some
conditions it can return a value greater than 1.
This function is used by genirq_enable() and genirq_disable() and both of them
returns the value returned by genirq_set_active(). According to the
do
