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; bh=M1l4MMYyndixrSl0Lr7bpYAO0C6te/HUcdDA6vyCsWs=; b=jAvA2NA0N4v6Px3M06vqZAnYyMC5uq+AxR/XyLqv/njEC4iy+F/9DRxh9jeGE9lVyG yLSuRURugTd5i7q8/QeYqi3vcBJ9F6SUT2mXQyuGsk8XYJUJvHrIJFVK5zyheNoFQrMO pf+Mw1UvY67AfyG11X4oJeyKZhEoe6DQNwYMG+z2v2ULmAtykvl28YaPtiHzTXlDWTWv 5s4z/S92L2CKh38CqXarZn5vT8VU1WKFTt76KB9u5VSylLaBNGtwAXqlPXWMBAXoXD2f xIYMJXqkbQKlD6N/+acNEcj5vvt6W88eWCmaqpcClgQzEkNk3eA3qVb9ajOEMX5J18bj TNcw== MIME-Version: 1.0 X-Received: by 10.112.62.133 with SMTP id y5mr8164553lbr.120.1441029138077; Mon, 31 Aug 2015 06:52:18 -0700 (PDT) In-Reply-To: <201508310341.t7V3fcfh022966@envy.delorie.com> References: <201508301802 DOT t7UI2twS031311 AT envy DOT delorie DOT com> <201508310341 DOT t7V3fcfh022966 AT envy DOT delorie DOT com> Date: Mon, 31 Aug 2015 09:52:17 -0400 Message-ID: Subject: Re: [geda-user] back annotation proposal (RFC) From: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 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, Aug 31, 2015 at 3:41 AM, DJ Delorie wrote: > >> That makes a lot of sense for the netlist but what if you change a >> footprint? I think there should be another tool that you run in >> parallel to gnetlist to handle that. > > I assume a much more intelligent netlister. > > The netlister maps what it knows about each symbol to a list of > candidate options for "heavifiing" the symbol into a full component. > One of these options is the package, and once you somehow choose a > package, there's one or more footprints that go with it. See to me that is 2 different tools 1. To handle migration of the netlist into gschem (I think more of this might happen in gschem than Igor2 expects right now but I have to sleep on my ideas before saying more) 2. To handle changes in symbols and their properties (footprint and etc) Tool #1 is doing the same thing as gnetlist but in reverse implementing something like minicut from pcb-rnd. I think that is at least a fork if not a whole other tool from gnetlist. > Part of my idea is that pcb takes all the choices it knows about and > gives them to the netlister, so that the netlister can use that to > narrow down the options it's left with after dealing with the > constraints in the symbol. > > I.e. if you have a generic AND gate symbol, there's lot of options for > the netlister. But if this is a future iteration, pcb might already > know that you picked a 74ALS00 in a SDIP-14 package with the SDIP14M > footprint. It can tell the netlister this when it does an > update-import. It can also tell the netlister what pin mappings were > used. > > If the information in pcb is no longer valid for the device (i.e. you > changed a 2-in AND to a 3-in AND), then the netlister would discard > pcb's choices and start fresh. I have to think about this more. A lot of stuff (like slots in symbols) only works for things like 7400 series logic. > So, there's a lot of back-annotation information being sent from pcb > to the netlister, which lets you do package, gate, and pin swapping in > pcb, but none of it ends up back in gschem unless you do something > specific to make that happen. -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/