X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=mbMwS4H3yfEzm+sNiggUvv/GXknTzpkYjIgoKbpYdH8=; b=W7dixdsnS1f2++Wys4cE1H1cZ8Eh1r6i5SDLz7RjYQ6Y2ySLW/XUFsSsXDp3RY5wV3 nDgbGQg86+wKmfavdXEF0sHd+Yz2k8MrIqYW6qeWN/Q+F94pPNbkG5bpZU7AmyA+8Xq9 PWG5KduB+zX7fiNJbCaiox5er3WBhmK7W5ABXmDZYyvOR/PYof4BjHV+QLMRcWlFrdZJ ObMhMNOmNd7oPnrNhDztGtHg41d/DU9iiSqqhDYwvPeYw6be6bW1Bl0QpIYyhoEAl5H3 Ud5O4U2q7z+wc6/WvSN2iBSsJyfYnssYIdE1g4FaXQLt8EzlObYPt3IMvItUPg1/VuTz 6Y1g== MIME-Version: 1.0 X-Received: by 10.25.43.80 with SMTP id r77mr7425864lfr.120.1444708570302; Mon, 12 Oct 2015 20:56:10 -0700 (PDT) In-Reply-To: <88EA58F5-2B23-498A-9E5B-84054976DBED@noqsi.com> References: <1042003D-82E2-40F0-AB60-8186580C46AD AT noqsi DOT com> <201510121905 DOT t9CJ5T9W026297 AT envy DOT delorie DOT com> <88EA58F5-2B23-498A-9E5B-84054976DBED AT noqsi DOT com> Date: Tue, 13 Oct 2015 03:56:10 +0000 Message-ID: Subject: Re: [geda-user] A lesson from gnet-makefile From: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" To: gEDA users mailing list Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t9D3uGsv014740 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 On Mon, Oct 12, 2015 at 11:04 PM, John Doty wrote: > > On Oct 12, 2015, at 1:42 PM, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > >> >> This is related to what we were talking about earlier here. >> https://bugs.launchpad.net/geda/+bug/698771 > > That’s about pcb. I have little interest in pcb-specific discussions. Ok at my stuff at the end. I posted a concept of what I thought it should look like in gschem. I would like to revise part of it. You have a point about pins but I feel like it would get very hard to read if all those net attributes were stacked onto the symbols instead of the nets. Plus it is kind of bending the way we have always made things direct honest relations from gschem to gnetlist output. >> (I have since realized there are things in the example sch file that >> could use tweeking) >> >> I also had some off list talk with John Griessen who was looking even >> farther out than we are (RF layout and verilog-ams). >> The output format for gnetlist is an interesting question. > > To start, we should think about how to represent the additional data in a schematic. If there are downstream tools that can handle this data, the way they encode it may be of interest. Generally, though, this is a gschem issue: how do we devise symbols and attributes that represent what we want? Do we need changes in the core (I hope not)? Translation to the various layout and simulation tools is then a job for gnetlist or xorn. Pcb, having no mechanism to do anything with this data, isn't terribly relevant at present. Well there needs to be something that works like s_conn and it's partners in gnetlist that walks the list mapping the nets but with this added metadata. > What we need is knowledge of layout programs that *can* handle this sort of extra data. Without tools to export to, what good is it? Finding out this information seems difficult. Good points although I would be happy to just have notations in pcb in the short term. We should also keep back notation of this in mind since a lot of layout architecture can change after you go to your pcb program. > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd AT noqsi DOT com > > -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/