As Hannes Weisbach wrote:
> Just a comment about pthread dependencies, I think I’ve made
> before. If nothing changed, only the ftdi_syncbb programmer used
> that and it was required only, because buffer limits of the FTDI
> chip were ignored. Given proper handling of buffer sizes (see
> avrftdi)
On Fri, Dec 3, 2021 at 7:29 AM Hannes Weisbach wrote:
>
> Just a comment about pthread dependencies, I think I’ve made before. If
> nothing changed,
> only the ftdi_syncbb programmer used that and it was required only, because
> buffer limits
> of the FTDI chip were ignored. Given proper
Hey,
> MinGW turned out to be "good enough" for me, that's why I even did it
> that way. Nobody else volunteered to run Windows release builds,
> despite of many users asking for it.
>
> But if there's a MSVC path, I wouldn't mind, as long as it doesn't break
> the GCC path for unixoid systems.
Trying a mass-reply to all the answers that arrived.
As greu...@mgtek.com wrote:
> It is certainly too much work for a single person, and I really do
> appreciate that you are donating your spare time to keep avrdude alive!
Thanks!
> Speaking of testing, I was wondering what kind of tests you
> On 21 Nov 2021, at 21:22, Joerg Wunsch 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
