[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: gEDA-user: net labels question
CADENCE Framework II uses e.g. _CLK to write CLK with a bare above the string
for pin lables of symbols, to indicated an inverted CLK signal (input) port.
But these labels are not used as net names or something else.
Peter
Am Sonntag, 6. April 2008 17:16:33 schrieb Stuart Brorson:
> > Does everyone understand a trailing underscore as negative logic?
>
> No.
>
> In my experience, a negatively asserted signal can be flagged in
> several different ways, depending upon who is talking about the
> signal.
>
> In PCI bus land, signals asserted low are suffixed with a pound sign,
> #. For example: TRST#.
>
> For diff pair signals, e.g. LVDS & CML, I often see netnames suffixed
> with _N and _P which indicate the logic sense of each net, for example
> SIG_N, SIG_P.
>
> I've also seen people suffix diff pair netnames with + or -, although
> for reasons previously mentioned, that's probably not a good idea.
>
> Personally, I've sometimes used the convention that low asserted
> signals are suffixed with _L, for example RST_L.
>
> I've also seen low asserted signals flagged using _N, e.g. LATCH_N.
>
> I think there's no commonly accepted practice here....
>
> Stuart
>
>
> _______________________________________________
> geda-user mailing list
> geda-user@xxxxxxxxxxxxxx
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user