X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 18.111.13.192 X-Authenticated-UID: jpd AT noqsi DOT com Content-Type: multipart/signed; boundary="Apple-Mail=_74BD2D32-4F38-4F5A-8A8F-3AAA585C07FB"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [geda-user] Possible paths of gnetlist development X-Pgp-Agent: GPGMail From: John Doty In-Reply-To: <20160926102647.1820967e@floyd.freeelectron.net> Date: Tue, 27 Sep 2016 09:54:27 -0400 Message-Id: <83F603BB-B5A2-4332-80D4-92D31DA03949@noqsi.com> References: <9067F448-ADF3-4A04-AC40-E82A87AC2BB5 AT noqsi DOT com> <20160926102647 DOT 1820967e AT floyd DOT freeelectron DOT net> To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.1878.6) 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 --Apple-Mail=_74BD2D32-4F38-4F5A-8A8F-3AAA585C07FB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Sep 26, 2016, at 10:26 AM, al davis wrote: > On Mon, 26 Sep 2016 09:05:21 -0400 > John Doty wrote: >> 1. Use attributes for rather than special backend-dependent symbols >> like spice-subcircuit-LL. >=20 > I agree. >=20 > Likewise, backends should not have anything symbol-specific. There=92s nothing symbol-specific in gnetlist. A back end can=92t even = find out which symbol(s) a =93package=94 corresponds to. But = spice-subcircuit-LL.sym has the attribute device=3Dspice-subcircuit-LL, = which the SPICE back ends recognize. The problem here is that the layout = back ends think this is an actual component. >=20 > and all backends should support attributes, in a consistent way. >=20 The trouble here is that gEDA supports an open-ended variety of flows, = and one size does not fit all. Every gnetlist back end uses the = footprint attribute, but what should you put in it? The names from your = layout tool=92s library? The gEDA convention = (http://wiki.geda-project.org/geda:pcb_footprint_naming_conventions, = mischievously presented as a pcb convention)? If you use the gEDA = convention, do you alias the footprints in the library to match, or do = you automatically translate? A lot depends on the size of the project, = the tools employed, and the skills and preferences of the designer(s). = I=92ve used every one of these approaches for one project or another. If you=92re simulating with SPICE, you=92ll want your numeric value = attributes to be SPICE numbers. Fortunately, procurement folks find this = usable in a BOM. But for a different flow, you might want something = different. Then, there are attributes for specific back ends. Some of the standard = library symbols have pins and class attributes for Allegro. The class = attribute is probably not useful for any other flow, but I find pins = useful for DRC = (http://www.gedasymbols.org/user/john_doty/tools/check-pincount.html). John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com --Apple-Mail=_74BD2D32-4F38-4F5A-8A8F-3AAA585C07FB Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJX6noUAAoJEF1Aj/0UKykRnLoP/Au9lqwkOYqBsL5QYkVW6k9+ TD0dvPe/XWpT3h9TFXEzINTPi1VbRhtfF+MGfHNIBKQtzjD/aG7jKBZdCdrxJvCh Ce0KZM7+De9ky45OzdTq4+T1vm1mQ8ynlu25ZuYJeMesXrVDBvjfwflq3GmqZStM XQp+L9CG5dGqZ6G8fIa9yNNRSkziH+P2K8bg0L1+dtw9CMofMQeoNCLN0nO212iy lGwb6b49ObgzBVD+pV+q6qhucMqdkfpejuCzkRVkq6dC419HkPkDr8VC4huRMDt1 7LCObTWJqggPRUKbBqFdq27GsIXiZDe0adC29uVkgauLGmT+sKccAs4ZUTE5t/AX lMU3fN1E4MDGZTZwCipetNIiAh81x6WM9ylifojHOs2ppPrfje66dyOYM9B8UOIA /PiJaMR3ee7gifaAvCg4RRF9Xrdq0AZaJ6fgvZJEI/XhaujBX4swy+3l7cxy8czG /6w2Bv2oql0Zv7F85F3fvCLBIC9/up/ivTQfK5IId9G8nbHhVO8Ml/ZhwZZe9Dp4 fNFARmyh1/lV4gvOiwhSy5fy441OmENDZK5YMKN1zW17fNbwQZZZF/z3ucjTU1bH Wrk1n1J7HQ5zwB16j9NawZQPMVQvG0CscfWIcktnLCrTc7x1wyG8SYUftLNIWjlZ vVju2eUnPl6yALj+pyrC =75yU -----END PGP SIGNATURE----- --Apple-Mail=_74BD2D32-4F38-4F5A-8A8F-3AAA585C07FB--