On Sun, 2007-04-08 at 22:04 -0400, evan foss wrote: > How does this effect the multi page system? I suggest there be three > levels in your system. > Global nets (/) that cross all pages. Local nets (/pagename) that are > page specific. Then local nets (/pagename/busname). Each containing > the net(s) name(s). This will help with automatic net naming that I > would like to add to gschem. Net names should be visible on each page. > I hate having to go through and add them manually just to be able to > see where the names land. I would suggest that all this information be > visible optionally so that we can check the auto netlisting is > working. Also the global nets should get a visible difference just to > be safe. I just thought I should toss my 2cents in.
I'm not sure about global nets, or "/" in the netname. I was using a path like structure to home in on a particular net within a nested bus scheme, however (you might see from the diagram), I was specifying these paths relative to the current piece of bus which I was breaking a signal out from. There is some argument that "global" nets don't really have much place in hierarchy, and are in fact brought out to ports on the circuit, be they represented on the schematic or not. For optimal re-use and user sanity, named nets should not propagate between levels of hierarchy. Steve Meier has already implemented something like this, which allows (for example, "VCC") in one hierarchy level to be wired to a different net in another. This is the sort of scheme I'd like to keep. If we use global nets, and want to connect them to a higher hierarchy level, there should be something in the circuit description, and ideally a pin in the schematic to make it explicit. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
