Re: gEDA-user: Buses and gnetlist/pcb?

[Vanessa Ezekowitz <vanessaezekowitz@xxxxxxxxx>]

On Fri, 11 Jun 2010 20:05:43 -0700
Matthew Lai <cyberfish@xxxxxxxxxxx> wrote:

> I know that gnetlist and pcb don't care about buses, but how do people 
> usually name related nets?
> 
> I used A:1 A:2 etc, but apparently they will all get merged into one.

I've only used this feature a couple of times, but in so doing, I name the nets according to the device or port the signal stems from or most closely relates to, and the signals they carry.  If there are multiple, separate buses, each gets the same sort of treatment - a base name relating to that bus, and a suffix describing the signal the net carries.

A simple system bus port might get names like "SystemBus_D1", "SystemBus_A3", etc., or you might use the actual working name of the bus, such as "Expansion_D4" or "Expansion_IO2" (to borrow from terms used in my hobby).

If one were to attach a bus interface device to that system bus port that provides a secondary bus, one might name the nets coming off of that interface according to the type or meaning of the bus they create, i.e. "I2C_Data", or "AuxBus_D4", etc.

As unlikely as this would be in a proper design, if a device attached to that secondary bus provides yet a third bus of some kind, then you would want to properly name those nets also, in a similar manner.

-- 
"There are some things in life worth obsessing over.  Most
things aren't, and when you learn that, life improves."
http://starbase.globalpc.net/~ezekowitz
Vanessa Ezekowitz <vanessaezekowitz@xxxxxxxxx>


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user