Hi Paul. :) On Wed, 4 Feb 2015 00:20:30 +0300, Paul Fertser wrote: >> What would be the preferred implementation - a new stand-alone >> driver or a "one size fits all" ? > > [...] lower maintenance burden long-term [...] > Usually sharing as much code as reasonably possible helps with that [...]
Thank you for the input, this is very helpful. I'm leaning towards adding code to kinetis.c, so I might start by trying to generalizing this code. I might first try writing a stand-alone driver, though; just to make sure I get everything right. The target auto-detection carries some weight for me as well; if just specifying 'kinetis', then it's easier for the end-user, but it also makes it possible to recycle a shared .cfg file. Love Jens ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
