On Tue, Jun 30, 2009 at 11:10 PM, Anthony Shanks<[email protected]> wrote: > >> - hierarchy configuration from top-level schematic, > > What do you mean by this?
Say, you want to modify a subcircuit somewhere deep down the hierarchy or use an extracted netlist for some of sub-blocks. If there is no hierarchy configuration, you would have to modify all cells in the design starting from the swapped one up to the top level. With hierarchy configuration, you can specify that the sub-cell should be mapped to a particular "cell view/architecture" (e.g. "extracted" or "schematic_for_openloop_gain_simulation"). If this could be integrated with gschem, so that it knew which schematic it should descend to, that would be perfect. Unfortunately, AFAIK gschem has neither the notion of "cell view" nor the hierarchy configuration. One idea would be to add a text-like "component" on the top level schematic, say "hierarchyConfiguration", where the user could write something like this: ----- # original_file_name file_name_to_be_used preamp.sch preamp_for_openloop_sim.sch analoglatch.sch analoglatch_extracted.sp # path_to_instance file_name /X5/X1/something something_else.sch ----- IMHO, having this information present and displayed on the top level schematic (testbench) is very convenient from the design management point of view. If it was to be added in a GUI or in makefile the information would have to be stored and handled separately. Regards, -r. _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
