Freddie Chopin wrote:
> So what's the plan here? Is ft2232.c going to be deleted? Is it
> going to be kept but no further changes for this code will be
> accepted?
I'm eager to delete it. One step on the way is to deprecate it.
Unsure what should happen when. It's a good point that the sooner it
goes away the less confusion, but on the other hand I think it makes
sense to have one release where it is still available, even if it is
not the default.
> It must be stated that ft2232.c has at least two important
> advantages over ftdi.c:
> 1. it can use ftd2xx, which for some people IS important
Why is it important?
> 2. all interfaces' configs embedded in it are tested (or - at lest
> - majority of them), as opposed to ftdi.c which only has partial
> coverage (I estimate it to be about 1/3)
That will fix itself once it becomes the default driver.
> If we consider ftdi.c "stable" (I do) we could think about a way to
> making it "default", but there's no such concept in OpenOCD... The only
> thing that comes to my mind is moving config files using "old" ft2232.c
> to some subdir ("deprecated"), possibly adding a warning about them
> being deprecated (directly to ft2232.c or to each config), and moving
> configs using "new" ftdi.c one level "up".
Yes, that's the way to do it.
> I just don't think it's possible to deprecate ft2232.c any time soon
It is already deprecated in my not so humble opinion. Look at the
horrible code.
//Peter
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
