X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Sun, 3 Jan 2016 14:38:49 -0500
Message-Id: <201601031938.u03Jcnrt011354@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: <56895EC2.80509@ecosensory.com> (message from John Griessen on
	Sun, 3 Jan 2016 11:47:46 -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> <56895EC2 DOT 80509 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
Precedence: bulk


> Maybe call it fpga-pin-swap for clarity.  The affected nets/pins
> could have wires drawn, and could go to slotted packages/symbols
> too.

The problem of assigning semantics to FPGA pins is slightly different,
because it's more complicated than just swapping pins (FPGA pins might
have interface limitations, clock domains, etc).  Still, the
developers can create a swap map for the fpga's layout where it makes
sense, although I suspect something like John's fpgas-as-tables to be
a better alternative.