[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [patch #9328] ft245r.c: add TPI support (patches 5-7)

From: David Mosberger
Subject: Re: [patch #9328] ft245r.c: add TPI support (patches 5-7)
Date: Wed, 24 Nov 2021 12:10:39 -0700


On Wed, Nov 24, 2021 at 2:12 AM Joerg Wunsch <INVALID.NOREPLY@gnu.org>

> Update of patch #9328 (project avrdude):
>                   Status:                    None => In Progress
>     _______________________________________________________
> Follow-up Comment #2:
> I'm not sure about D2XX. The issue came up earlier, it might contradict
> Savannah's policy to offer "non-free" software hooks. Let's see.

No strong feelings on that from my side.  We are Linux-based anyhow and for
our partners who aren't, we just ask them to use Raspberry Pi for
programming purposes.  That has worked fine so far.

> I'm quite impressed about the sheer amount of rework you did here.

Thanks!  It was a lot of work, but it has paid off.  We use this support on
a daily basis in manufacturing.  Being able to program the boards with an
off-the-shelf FTDI cable makes everything super easy.

> Question about that baudrate fixing patch: Would it hurt anyone to offer
> this
> as a default? I've tried testing the ft245r driver on my (old) UM245R
> board,
> and have the impression I'm affected by that. Since most people probably
> use
> AVRDUDE as a binary, the compile-time option wouldn't be much useful to
> those
> users.
> Alternatively (if enabling it has a negative impact to other features), any
> chance for a run-time guess whether it needs to be enabled?

It's been 4 years since I last worked on it, but from what I remember (and
rereading the patch), I believe it's safe to always enable the workaround.
As far as I remember, all of our FTDI cables required the workaround at the
time.  We have always had this workaround turned on and have not run into
any issues with any of the FTDI cables we used over the years.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]