Re: [myhdl-list] IP core library
Brought to you by:
jandecaluwe
From: Euripedes R. F. <roc...@gm...> - 2015-05-04 15:38:06
|
2015-05-04 12:14 GMT-03:00 Christopher Felton <chr...@gm...>: > On 5/3/2015 6:39 AM, Euripedes Rocha Filho wrote: > > Henry, > > good articles. > > > > @Christopher, > > I will follow this approach: > > > > module.py > > parameters - named tuple with the parameters/generics for the design > > interface - class with necessary signals > > module(parameters, interface) - hdl implementation > > > > For each module I don't think you should force > everything into one interface for the module. > In my opinion have logically grouped interfaces: > > module(interface1, interface2, ..., parameters) > > The idea is to have some regularity across all modules and in the higher level you just need: import module module_interface = module.interface() - An instance of the signals to interconect parameters = module.parameters('Parameter') module_instance = module.module(parameters, interface) > What is the benefit of using namedtuples over > dictionary or your own Parameters class? > Named tuples seems to fit better the purpouse of a parameters list and it will force the definition of all parameters, it will also force the concept that the parameters should not change in run time. Regards Regards, > Chris > > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > |