X-Authentication-Warning:	delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient:	geda-help AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:content-transfer-encoding;
	bh=3M8Bo11VHQ24IavuVnC/x83pUUvWIfMak23sDvmfOJE=;
	b=itvh62GBdEujR+frnUv1B1ilEq2r334ck5ul5mlRzQESf9cMa34cXiFLUqoo/Cj9H3
	SNYbAdY0e8kxKvFwW3kt1twSxqTgrfcRwdhKsQG5A7n5HFfhIOnNceuWNuETvUfGt3Kf
	RQcvEEWvrRlGkl6F5tRwwLrNdaf3CWdrVdos9qNmyVPzDX/n0NqJi5J+89Nx6ZlvOJ8J
	oan053jGW/xHcrfzO7+vSJ8ce78qCxtx1TNvmsRGrrtWEVUvKPD69iPNgbBwynrM4LyG
	bXMABb3rF0kfelcZP33amOpdFVt4cQEuOym0KsoPhJlpiZSgrru7396LtsEAr8WRG/mm
	JUgg==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-transfer-encoding;
	bh=3M8Bo11VHQ24IavuVnC/x83pUUvWIfMak23sDvmfOJE=;
	b=o/dNxNZPk1RAfXiL3UhSBDd+S9ax/ADbruCAZwhKsn6UIY5ysiUl484w36xcy7TudX
	F6SH5w8WNa5sTOyoUnirSeIvEPM5u1EBhq2URpZgYpqGAFNHlJc+3C/aGM4t4HGKwXcX
	94AWIzGytsNUKAfFrFZP+IBaW2Erag4J6NFamFGbEombZ/mmnlkvMdUnTAsz5yOUIgQ/
	6r9CnIy9JgH/XqpHOqt1VSFjBRldYtGvV9m1rqrQEa72t4gN10IKKqaZXtsgBmLMQiuW
	0EBQX7QSs/Q/8yZT+7sFdQb3l8fNAEjsFx+Z72HeHttj0xrqFl6T90tDINkDVb9Ym34k
	Ghww==
X-Gm-Message-State:	AIkVDXLCFodTljF2Esw5iQiJbYK3YP/zO9Dj6Eq8kZJE7cIp/j4SQH6T7dVhytJc/7XT8VpGMyRZ+vtAdab80g==
X-Received:	by 10.28.127.13 with SMTP id a13mr5670627wmd.96.1486014814546;
	Wed, 01 Feb 2017 21:53:34 -0800 (PST)
MIME-Version:	1.0
In-Reply-To:	<2A68D8FB-6CAA-40E5-8265-571627133EE4@noqsi.com>
References:	<20170201190901 DOT 7796c45d AT debian> <2A68D8FB-6CAA-40E5-8265-571627133EE4 AT noqsi DOT com>
From:	"Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
Date:	Thu, 2 Feb 2017 08:53:34 +0300
Message-ID:	<CAMvDHVDdD=1inEuaMiwH2zACxJYEN6zFZDxoRAVRh019fv4y9Q@mail.gmail.com>
Subject:	Re: [geda-help] pinseq
To:	geda-help AT delorie DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id v125ra1N006233
Reply-To:	geda-help AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-help AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 2/1/17, John Doty <jpd AT noqsi DOT com> wrote:
> It depends on what your downstream flow is. Gnetlist uses pinseq in two
> incompatible ways:
>
> (1) For identifying pin functions in a multisection component like a quad
> gate.
>
> (2) For ordering connections in a netlist (like a SPICE simulation netlist)
> that depends on pin order to identify the pin.
>
> This appears to be a single section component, so (1) doesn’t apply. You
> haven’t said what you’re using downstream, but I suspect you’re doing PC
> board layout. Most (all?) PC board netlists use pinnumber, not pinseq, to
> identify the pin. So, (2) probably doesn’t apply either.
>
> You probably don’t need pinseq attributes at all.

Currently, pinseq= is processed in only two backends: spice-sdb
and vipec.  The latter is most likely non-functional as it can be
seen from tests added to geda-gaf in 2008 and development of the
program it was used for [1] seems to have stopped about 2003 so it
is most likely abandoned. So if spice-sdb is not planned to be
used there is no point in using pinseq=.

  Vladimir

[1] http://vipec.sourceforge.net/

- Raw text -