David Röthlisberger

XMP: Fix repeats

XMP: Fix repeats

XMP: Add missing gap from XMP protocol

The nabble link doesn't work but this appears to be the same thread: http://developer.intra2net.com/mailarchive/html/libftdi/2016/msg00001.html (archive: https://web.archive.org/web/20180115232835/http://developer.intra2net.com/mailarchive/html/libftdi/2016/msg00001.html ) There's an unresolved question in that thread about whether that was a counterfeit chip, but I could easily believe that a genuine FTDI chip has weird undocumented clock behaviour in bit-bang mode (see my experience with FT232R:...

I also was affected by this bug. To summarize: The sigalarm used for scheduling repeat signals was racy with lircd's main poll loop. The symptom was: A 2nd irsend (hot on the heels of the 1st irsend) would hang (gdb showed lircd was in poll), until you sent a 3rd irsend (and then both the 2nd & 3rd irsends would be processed). I could only reproduce it with drivers/plugins that block while each signal is being sent, such as the kernel driver (I was using pwm-ir-tx) — I couldn't reproduce it with...

I also was affected by this bug. To summarize: The sigalarm used for scheduling repeat signals was racy with lircd's main poll loop. The symptom was: A 2nd irsend (hot on the heels of the 1st irsend) would hang (gdb showed lircd was in poll), until you sent a 3rd irsend (and then both the 2nd & 3rd irsends would be processed). I could only reproduce it with drivers/plugins that block while each signal is being sent, such as the kernel driver (I was using pwm-ir-tx) — I couldn't reproduce it with...

I also was affected by this bug. To summarize: The sigalarm used for scheduling repeat signals could interrupt lircd's main poll loop. The symptom was: A 2nd irsend (hot on the heels of the 1st irsend) would hang (gdb showed lircd was in poll), until you sent a 3rd irsend (and then both the 2nd & 3rd irsends would be processed). I could only reproduce it with drivers/plugins that block while each signal is being sent, such as the kernel driver (I was using pwm-ir-tx) — I couldn't reproduce it with...

Never mind, someone else already did just that (in 2018! https://sourceforge.net/p/lirc/tickets/315/#0719 — I wish I had found that 6 months ago) and you merged it recently in #50. Thanks again (for reviewing both mine & @asunxx's patches).