On Thu, Feb 2, 2012 at 12:15 PM, Freddie Chopin <[email protected]> wrote: > W dniu 2012-02-02 18:09, Chris Morgan pisze: > >> Do you know who came up with the init_target idea? That's the person >> that would probably best help decide what to do. > > > Ųyvind? I don't remember, probably it would be best to see the commits > around year ago or list archives... > > >> Maybe you are right and the lpcxxx.cpu scripts should be modified to >> call to the generic ones directly, removing the init_target usage, as >> you've suggested. Then when sourced the $_TARGETNAME would be valid. > > > Nope, I'd leave init_targets, but move _TARGETNAME "outside" and pass that > to init_targets - currently this var is created in init_targets, thus valid > only after init. >
Not sure what you mean but you know this better than I do. That sounds good. > >> If there was an init_board then the actionable code in the ea board >> file could be placed into there and openocd could call init_target() >> and then init_board() and everything would work since the target would >> be initialized before use. > > > That's a very good idea, but I don't know whether you can define handlers > (like reset-init), which are something like a procedure, INSIDE another > procedure (init_whatever())... > > 4\/3!! Yeah. The best approach is probably to move back to the same approach used for the rest of the config files. If/when a coherent approach to this kind of thing comes up then all targets/cpus should be modified in short order, instead of just one at a time. Sorry to see some of your changes get reverted but looks like most of them will remain no? Chris ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
