On 08/06/2022 22:11, Gedare Bloom wrote:
On Wed, Jun 8, 2022 at 1:04 PM Sebastian Huber
wrote:
On 08/06/2022 17:40, Gedare Bloom wrote:
Hm. This looks ok, but it also seems to be a bit of an awkward
requirement. Is this only relevant for the tm27 test?
I hijacked the tm27 support to add an A
On Wed, Jun 8, 2022 at 1:04 PM Sebastian Huber
wrote:
>
> On 08/06/2022 17:40, Gedare Bloom wrote:
> > Hm. This looks ok, but it also seems to be a bit of an awkward
> > requirement. Is this only relevant for the tm27 test?
>
> I hijacked the tm27 support to add an API for software interrupts.
>
D
On 08/06/2022 17:40, Gedare Bloom wrote:
Hm. This looks ok, but it also seems to be a bit of an awkward
requirement. Is this only relevant for the tm27 test?
I hijacked the tm27 support to add an API for software interrupts.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puch
Hm. This looks ok, but it also seems to be a bit of an awkward
requirement. Is this only relevant for the tm27 test?
On Tue, Jun 7, 2022 at 8:01 AM Sebastian Huber
wrote:
>
> Some BSPs require that Clear_tm27_intr() is called in the interrupt
> service routine.
>
> Update #3269.
> ---
> testsuit
Some BSPs require that Clear_tm27_intr() is called in the interrupt
service routine.
Update #3269.
---
testsuites/validation/tx-call-within-isr.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/testsuites/validation/tx-call-within-isr.c
b/testsuites/validation/tx-call-within-isr.c
index 22