X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient: geda-help AT delorie DOT com
X-Authority-Analysis: v=2.1 cv=Gfm35VjL c=1 sm=1 tr=0
 a=cDnmOZVFPq8wHbkBZXyVTw==:117 a=cDnmOZVFPq8wHbkBZXyVTw==:17
 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10
 a=pGLkceISAAAA:8 a=Mj1Xp5F7AAAA:8 a=ZNzOqGV4AAAA:8 a=FP58Ms26AAAA:8
 a=XdFrpnGkIR3JTC_o_0sA:9 a=QEXdDO2ut3YA:10 a=6kGIvZw6iX1k4Y-7sg4_:22
 a=OCttjWrK5_uSHO_3Hkg-:22 a=E-7ZDB97qVM_U7m9UvkO:22 a=6LVbBl2NLSWPyIBDCKCu:22
Message-ID: <58936E2E.1090905@videotron.ca>
Date: Thu, 02 Feb 2017 12:36:46 -0500
From: "Ian Chapman (ichapman AT videotron DOT ca) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: geda-help AT delorie DOT com
Subject: Re: [geda-help] pinseq
References: <20170201190901 DOT 7796c45d AT debian> <2A68D8FB-6CAA-40E5-8265-571627133EE4 AT noqsi DOT com> <ZAblcTuoh3wDaZAbmcm7ML AT videotron DOT ca>
In-Reply-To: <ZAblcTuoh3wDaZAbmcm7ML@videotron.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfOCXFka8uoqgXmeFTun34QLJ8spZ3mNJ6zfXxRQshXYSIov06x/u1G+ZGsyV4a3NA5aptjqsY2S24Cb9IavPIya8+Hk1h6wA0f8WS0mUCx6EzaQZCXUx
 xhDe0Jr2lPIzvP8V/k17hHnFj/NYyM5+G0A25jsOlTK6ze9785RMOEq3
Reply-To: geda-help AT delorie DOT com

I always wondered what pinseq was all about so for PCB layout only use I 
can forget it?
         Regards Ian.
On 02/02/17 12:53 AM, Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via 
geda-help AT delorie DOT com] wrote:
> 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/
>
>