On Mon, May 21, 2012 at 10:08 PM, Tomek CEDRO <[email protected]> wrote: > Hello :-) > > Sorry for my ignorance but Andreas could you please tell in one or two > words what is the main reason of creating "new" ft2232 driver and what > is new about that driver - the MPSSE is still the same instruction > set..?
I have ranted enough on this list about that. But, oh... the old driver is an unstructured, unmaintainable, buggy and incomplete mess that is bloated with unrelated and repeated details for specific adapter variants. And I see Peter has already responded with a more concise answer so I'll rest my case. > Could you please tell what is the difference between new driver and > ft2232_bitbang and ft2232_transfer that I use for SWD as part of > LibSWD - maybe I could improve its speed too? :-) I wish I had more time to look into and discuss your and others' work on SWD but I haven't right now. But I'm sure that it would be extremely simple to write an SWD driver using the same MPSSE abstraction as my new ftdi driver is using. I wrote an SWD driver over raw MPSSE (inside the old ft2232 driver) in less than a weekend, three years ago. And it would have been less work if I had this MPSSE abstraction. And faster too, even if my previous SWD work was on par or better than JTAG for the same target/interface, as far as I remember. I won't write another SWD driver though, until the proper framework is in place. The difficulty with SWD is not in the driver, but in core OpenOCD. I'm not really satisfied with the current transport abstraction. My main motivation for rewriting the driver was the need for a solid base for experimentation with the core interfaces in OpenOCD. And I'll probably continue with that, as time allows. /Andreas ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
