> On 21 Nov 2021, at 21:22, Joerg Wunsch <invalid.nore...@gnu.org> wrote: > > Follow-up Comment #3, patch #9565 (project avrdude): > > Short of that, maybe we should implement a kind of per-programmer notion of a > short vs. long timeout (defaulting to 100 ms / 5 s) that is subsequently be > used to toggle between both values. Then, the wavr programmer driver could > establish a longer "short" timeout than those 100 ms. > > How does that sound?
That could be doable. Assuming the current timeout is used for the new ’short’ timeout, can a default for the ‘long’ timeout be added at a high enough level to avoid churning code in the existing drivers? Steve
