delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2016/01/03/14:36:25

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Sun, 3 Jan 2016 14:36:19 -0500
Message-Id: <201601031936.u03JaJ3k011116@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
CC: geda-user AT delorie DOT com
In-reply-to: <56895BE5.9080200@ecosensory.com> (message from John Griessen on
Sun, 3 Jan 2016 11:35:33 -0600)
Subject: Re: [geda-user] ideas on slotting and mechanisms for
grouping/associating heterogenous symbols.
References: <CAM2RGhS4L-ch6FEcLtdSt0vA0BdQZvq+AuFDP+9ea7Ftd=AALg AT mail DOT gmail DOT com>
<8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com>
<alpine DOT DEB DOT 2 DOT 00 DOT 1512300544550 DOT 9035 AT igor2priv>
<87FC7D4C-157A-499E-8B93-97653D6A7C68 AT noqsi DOT com>
<alpine DOT DEB DOT 2 DOT 11 DOT 1601012231450 DOT 1728 AT newt>
<AE52C1DB-01A3-43FA-AE8E-68AD33F37180 AT noqsi DOT com>
<624E6A69-62CE-4FCB-9D44-9FDF036254A3 AT sbcglobal DOT net>
<56880043 DOT 7040003 AT ecosensory DOT com>
<20160102182739 DOT 5d195829880cf75768ae0a82 AT gmail DOT com>
<201601021755 DOT u02HtOWs020325 AT envy DOT delorie DOT com>
<20160102191018 DOT 5e68c0c4ecc70a49bd9998f6 AT gmail DOT com>
<201601021816 DOT u02IGHCC021127 AT envy DOT delorie DOT com>
<568817CC DOT 7090207 AT ecosensory DOT com>
<201601021843 DOT u02IhC5U021940 AT envy DOT delorie DOT com>
<20160102203149 DOT 375887378ec1a58ee7e9bc79 AT gmail DOT com>
<201601021936 DOT u02JameZ023677 AT envy DOT delorie DOT com>
<568882B7 DOT 6060607 AT ecosensory DOT com>
<201601030212 DOT u032C6dO009363 AT envy DOT delorie DOT com> <56895BE5 DOT 9080200 AT ecosensory DOT com>
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> Wouldn't it change in some cases?  Where you have schematic with signal nets
> drawn to show flow of signal through a system?  And where your symbols for slot parts
> do not go down to single sections?

I define swapping at layout as a modification that doesn't change the
geometry of the schematic, partly because it's too hard to annotate
but mostly because layout isn't a schematic capture tool.

So the scope of layout-based pin/gate swapping is: changes that can be
reflected only by changing the pinnumber= attribute (and optionally,
if we can figure out how, the refdes= one) on an existing symbol.

So you can rearrange the eight data pins of a RAM chip, but not move
half of them to a different chip.  You can swap the two inputs of a
NAND gate, or swap two NAND gates, but not swap a NAND for a NOR or
use part of an N+1 input NAND gate elsewhere.

> In that case, nets drawn to not overlap and "appear" simple and
> streamlined might have to change to crossing over some to allow for
> a decision made based on layout goals.

Shouldn't have to.  If you have two schematic lines going to a NAND
gate, but they cross on the layout, you do a pin swap.  This swaps the
physical pins on the layout, but *renumbers* the pins on the
schematic.  I.e.  if the top pin was "1" before, the top pin migh be
"2" after swapping.

> Strategy might not get executed all the way in real life.  I don't
> assume changing the pinnumber= attribute on existing symbols is all
> that will ever be needed, even if it handles most cases.

I'm limiting it to that anyway, because that's the case we can handle.
If you need something more complicated, you do it in capture instead
of layout.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019