On Sun, Jul 14, 2013 at 4:07 AM, Matthew Hicks <[email protected]> wrote:
> As a person that has to deal with or1200_monitor on a regular basis, this > files is a nightmare and of limited use to beginners. What are people's > thoughts on breaking each monitor into its own aptly named file that can > then be included in the main monitor file as needed? Some documentation > would also be nice :). > > > ---Matthew Hicks > > > Yes, it's a complete disaster, and my plan is to incrementally make things better. Splitting it to sub modules is a good idea. I was thinking about removing the wishbone protocol monitor next. That is a useful function for other things than just or1200. Help and ideas are highly appreciated. And yes, documentation wouldn't hurt :) //Olof
_______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
