X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-TCPREMOTEIP:	207.224.51.38
X-Authenticated-UID:	jpd AT noqsi DOT com
From:	John Doty <jpd AT noqsi DOT com>
Subject:	[geda-user] RFC: pin attribute remapping
Message-Id:	<5D1C97FB-F049-4ABB-90E4-F2108647A111@noqsi.com>
Date:	Sun, 13 Sep 2015 12:23:22 -0600
To:	geda-user AT delorie DOT com
Mime-Version:	1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer:	Apple Mail (2.1878.6)
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t8DINUUJ001564
Reply-To:	geda-user AT delorie DOT com

Folks,

I propose that an attribute of the form <name>:<pinnumber>=<value> attached to a symbol override the definition for attribute <name> of pin <pinnumber>.

This mapping would occur after slot assignment, which might seem a bit clumsy, but there are two reasons to do it this way:

1. Downstream tools generally identify pins by refdes/pinnumber pairs. They don’t understand geda-gaf slotting.

2. Gnetlist back ends also essentially identify pins by refdes/pinnumber. Slotting isn’t fully visible to a gnetlist back end.

For pinnumber itself, I propose two forms:

pinnumber:<previous>=<new>
pinnumber:<previous>=<refdes>:<new>

The second form allows swapping of pins between packages.

I believe this is implementable in gnetlist by a plug-in that wraps a few of the gnetlist primitives. This would require no changes to the core, and would even work with existing 1.8 binaries. However, it might not be the nicest way to factor this change.

For gschem, I’m not familiar enough with its scripting to know if it can be made to make the appropriate changes in the displayed graphics without a change to the gschem core.

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com

- Raw text -