On Thu, Jul 19, 2012 at 10:56 AM, Freddie Chopin <[email protected]> wrote: > W dniu 2012-07-19 10:10, Andreas Fritiofson pisze: > >> This should work with the changes I posted in a comment to patch set >> 7, which seems to match with what Andrew modified luminary.cfg to. > > > So this file should have 2 lines changed to: > > ftdi_layout_init 0x00a8 0x00eb > ftdi_layout_signal nSRST -noe 0x0020 > > And we can consider it verified/tested? Peter - does it match with what > you've found? > > >>> tcl/interface/ftdi/luminary.cfg >> >> >> This one was verified by Xiaofan. > > > So I guess we can also mark this one as verified/working too, right?
Yes. > How about interfaces that use common layouts? Should we mark them as > working, based on the fact that original is working too? For example - these > interfaces use "jtagkey" layout: > > busblaster.cfg > calao-usb-a9260-c01.cfg > calao-usb-a9260-c02.cfg > jtagkey.cfg > jtagkey2.cfg > jtagkey2p.cfg > jtagkey-tiny.cfg > neodb.cfg > openrd.cfg > sheevaplug.cfg > > so I guess it's safe to assume that they will work with new MPSSE driver (if > VID/PID/description is the same as in old drivers and pinout config is the > same as new config for jtagkey)? It should be safe enough. Let's submit them and see if there will be bug reports that say otherwise. > I've now noticed that you missed jtagkey-tiny.cfg in MPSSE configs? Any > specific reason, or you just forgot it? The use the same config. Tiny just sources the other one. I think it's pointless to maintain the redundant file in the new driver. /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
