Guys, you will never build anything out of pure complain. You need to show the alternative, and prove this alternative is better, preferably with a code example.
Example 1: Me: Bitbang idea allows to implement other protocols and move this functionality to the TCL interpreter. You: But bitbang is prone to usb bottleneck. Me: Then usb interfaces will be solwer, this will work fine with GPIO. You: Why don't we make a queue that will compact bitbang operations and send as many compacted as possible? Me: Good idea, bitbang can be more efficient this way, please show me where is the example queueing code. You: Here it is I can help you with the code... Example 2: Me: I have used jtag_interface structure for my work, this structure was representing the interfaces that control the electricity on the wire. You: But we are working on a something better, its Adapter, jtag_interface is obsolete. Me: Okay, then we have starting point in the current code, and we have direction on where to go in near future. There is an open thread for this kind of discussion on internals reorganization. I expected it to look like Examples above, not like "this is bad, end of story". If you prefer to first clean up the internals and then do the SWD, go ahead, call me when you need SWD support :-) Best regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ------------------------------------------------------------------------------ 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
