Richard Weickelt

Since early 2019 this ugly workaround should no longer be necessary because clcache now determines whether the first command line argument is a compiler executable. However, the last released version...

Yeah, I know how it is. Great that you have developed it, it seems to work well enough with MS VS 2017. Thanks to #346, [integration of clcache was very...

Actually, I think the problem is a missing `--enable-multiarch` in this toolchain's configuration.

Do I get You right: What You basically want is some kind of template mechanism to customize the output of directives? For instance to create Your own class, namespace, group,...

Thanks for the quick reply. > What do you mean by "doesn't recognize the interrupt"? I can see an edge on the GPIO line that should have triggered an event,...

I switched to the CAPI now. Same behavior. Maybe I am using libgpiod the wrong way? My program waits on interrupts on 2 different IO pins concurrently in 2 different...

Yes, everything is completely separated. No objects are shared. The kernel log does not contain any warnings btw.

When the host sees an event (falling edge on IO line), it acknowledges the interrupt with a SPI message. After the message, the peripheral will deassert the IO line and...

@warthog618 Here's a trace of the problem:  The trace consists of - 2 peripherals connected to the same SPI bus (SCLK, PICO and POCI) - distinct CS lines A...

Today I found [this topic](https://forums.raspberrypi.com/viewtopic.php?t=350295) which indicates that the issue discussed here might be hardware bug. A [workaround is in place](https://github.com/raspberrypi/linux/pull/5457). Surprising that any modern MCU would fail on such...