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=MChsRG/XCJctlc2YdkoEKgAevzWtRvx2xHuF38lZ7yo=; b=ychUXZM8qvhghaECyLKKgbnY2U5TgKCX25C5flMke3CT/0RVLkEgwXY+hgUIZmq7rR poH8tUbJqmweD3tSywcSnhvV4rtLPfPj2KDR+kItnk/FbdMQ/xiaXOf9+npd6MSHxHj3 w6Qpq6bop7YP31uTFYVapMxMU9RWGLMGqm88Bv7XPoRr5GbrpiQiUDCWY7nhliGUU3v9 to/BgwIYugUwH9oOI34/CXJj0QQlNaGImx59eXvIHVoXE52OosEBUepG/QB1Yhp7AphC G20TBKgRhhi7/Nj+KBedS6G16faxazIyhAAhv9bOia2VrFlj6hoA0GkcsvdT4LT7LcwR GrNQ== MIME-Version: 1.0 X-Received: by 10.112.209.4 with SMTP id mi4mr8412616lbc.7.1445518747506; Thu, 22 Oct 2015 05:59:07 -0700 (PDT) In-Reply-To: <20151022023002.GA25952@recycle.lbl.gov> References: <73ED29DA-968B-4675-9B00-125E03683C9B AT noqsi DOT com> <201510220112 DOT t9M1Ccfq013731 AT envy DOT delorie DOT com> <201510220136 DOT t9M1a5Uw015222 AT envy DOT delorie DOT com> <201510220149 DOT t9M1nrIe016145 AT envy DOT delorie DOT com> <20151022023002 DOT GA25952 AT recycle DOT lbl DOT gov> Date: Thu, 22 Oct 2015 08:59:07 -0400 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 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 Thu, Oct 22, 2015 at 2:30 AM, Larry Doolittle wrote: > Guys -0 > > On Thu, Oct 22, 2015 at 02:03:43AM +0000, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: >> On Thu, Oct 22, 2015 at 1:49 AM, DJ Delorie wrote: >> > It would be great if you could just connect two >> > nets like that and have the system remember the topology long enough >> > to DTRT in layout. But in gEDA, this type of connection only results >> > in an error. >> >> Well I was approaching that with the stuff I was talking about in the >> other thread but I realized there were fundamental issues with it. >> This is kind of why I was thinking about star grounds. Really this is >> a type of star topology. > > I don't think this failing is unique to gEDA. I just had a > board laid out in PADS (schematic in gschem), and some analog > stuff had to be left hand-wired, non-design-rule-checked, because > of this exact issue. Just like in PCB, there seemed to be no way > to communicate to the layout tool that two nets are supposed to > touch in a defined spot, but be independent. > > I think it's easy enough to create a "star" component in gschem; > getting a layout tool to deal with it seems harder. I've heard > of hacks involving extra layers to make it happen in PCB. The > team of PADS experts (not sure if a smiley face belongs there or > not) couldn't even imagine a way to make it happen for that tool. > Other than adding a bunch of zero Ohm resistors, which I rejected. What if you want to make a star with more than 2. I feel like we ether need a progamatically generated star symbol or a way to recognize when someone has drawn a star. The issue that hit me was if you have a multipage design or something more involved and you use a star how do you know even with a more involved netlist format where the star. There are also issues with PCB and it's understanding of this. > - Larry -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/