X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 63.119.35.194 X-Authenticated-UID: jpd AT noqsi DOT com Content-Type: multipart/signed; boundary="Apple-Mail=_925CD069-F4D3-483A-B72C-0BC5362FB8C7"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [geda-user] first attempt at bus support in gnetlist for pcb X-Pgp-Agent: GPGMail 2.5.2 From: John Doty In-Reply-To: Date: Fri, 8 Jan 2016 07:38:25 -0500 Message-Id: References: <201601080714 DOT u087Ejj5032766 AT envy DOT delorie DOT com> To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.1878.6) 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 --Apple-Mail=_925CD069-F4D3-483A-B72C-0BC5362FB8C7 Content-Type: multipart/alternative; boundary="Apple-Mail=_EB71FDDF-6C5A-4ABE-A4EB-243977991AD4" --Apple-Mail=_EB71FDDF-6C5A-4ABE-A4EB-243977991AD4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Jan 8, 2016, at 6:41 AM, Peter Clifton = (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] = wrote: >=20 > On 8 Jan 2016 07:17, "DJ Delorie" wrote: > > >=20 > > The net result of this is that you can assign a net named = "nBL,A[8-2]" to > > a pin labelled "A[0-7]" and numbered "1-4,10-7" and they'll all get > > hooked up as appropriate. >=20 > Presumably this operates with "normal" nets and pins, not gschem buses = - which still (as far as I recall) don't netlist. >=20 > > You can also have a pin named "GND" and numbered "1,15,18" connected > > to net "GND" and it will connect all three pins to the one net. >=20 > > Constructive feedback welcome! >=20 > I think the solution you proposed looks useful and pragmatic. >=20 > One potential disadvantage of using this, (user choice of course), is = that until more work on applying new semantic rules is done in geda, = schematics using this new attribute semantics will be less easily reused = for other work like simulation. >=20 >=20 You can do this kind of thing with a plug-in that wraps the appropriate = gnetlist primitives. It=92s somewhat harder, but could apply to most = back ends, not just pcb. > Regarding bus pins & buses vs. Net pins and nets.... I start to wonder = if we should aim to reduce that distinction in the future, and make all = nets / pins / buses more equally handled in gEDA. (Up to the netlist = backend / resolver). >=20 >=20 Yes. And then, erase the distinction between nets, busses, pins, and = lines. Move that into attributes: a line with netname=3D is a net, a = line with pinnumber=3D is a pin =85 This would let the user decide the appropriate line style for nets, = busses, and pins. Keep the old method for backward compatibility, of = course. > Optional stronger port typing like VHDL / verilog would also be nice, = for schematics that drive hdl output. >=20 >=20 That kind of thing belongs in a DRC script, I think. > Please can anyone replying consider whether a new thread is = appropriate if addressing my comments, not DJ's new feature. >=20 >=20 > > DJ John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com --Apple-Mail=_EB71FDDF-6C5A-4ABE-A4EB-243977991AD4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252

On Jan 8, 2016, at 6:41 AM, Peter = Clifton (petercjclifton AT googlemail DOT co= m) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> = wrote:

On 8 Jan 2016 07:17, "DJ Delorie" <dj AT delorie DOT com> wrote:
>
> The net result of this is that you can = assign a net named "nBL,A[8-2]" to
> a pin labelled "A[0-7]" and numbered "1-4,10-7" and they'll all = get
> hooked up as appropriate.
Presumably this = operates with "normal" nets and pins, not gschem buses - which still (as = far as I recall) don't netlist.
> You can also have = a pin named "GND" and numbered "1,15,18" connected
> to net "GND" and it will connect all three pins to the one = net.
> Constructive feedback welcome!
I think the solution you proposed looks useful and = pragmatic.
One potential disadvantage of using this, = (user choice of course), is that until more work on applying new = semantic rules is done in geda, schematics using this new attribute = semantics will be less easily reused for other work like = simulation.

You can do = this kind of thing with a plug-in that wraps the appropriate gnetlist = primitives. It=92s somewhat harder, but could apply to most back ends, = not just pcb.

Regarding bus = pins & buses vs. Net pins and nets.... I start to wonder if we = should aim to reduce that distinction in the future, and make all nets / = pins / buses more equally handled in gEDA. (Up to the netlist backend / = resolver).

Yes. And then, = erase the distinction between nets, busses, pins, and lines. Move that = into attributes: a line with netname=3D is a net, a line with pinnumber=3D= is a pin =85

This would let the user decide = the appropriate line style for nets, busses, and pins. Keep the old = method for backward compatibility, of course.

Optional stronger port typing like VHDL / = verilog would also be nice, for schematics that drive hdl = output.

That kind of thing = belongs in a DRC script, I think.

Please can anyone replying consider whether a new thread is = appropriate if addressing my comments, not DJ's new = feature.

> DJ

John Doty Noqsi = Aerospace, Ltd.

http://www.noqsi.com/

jpd AT noqsi DOT com

= --Apple-Mail=_EB71FDDF-6C5A-4ABE-A4EB-243977991AD4-- --Apple-Mail=_925CD069-F4D3-483A-B72C-0BC5362FB8C7 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWj63CAAoJEF1Aj/0UKykRAegP/j6+RNOP2hlVrQge1AxYne3w yH2YlbZUPh40Q6VAid1uvu3oc0KoYPh2j+BT7rd3yRiZhi8SprF28C6gQPHBPnx0 +RJsi5wDVG3Dbe0IVgQdx6SYmQSvkkF5mFHvWyJTfleH9iKcTfpRaiVSb+iqG4Xv 6ZXxMgJ/wyxFeoMdqOXkZkLDOINX5+qaTGa2rgeJQHrgmb4l7wTNn8y7fjPgS+Z+ G5PJcCGP2EZXLDzBrA11pP/rpyK2oq8jhG2qqn77DLOGJCPLUgu7HBAnKIuSXS89 x3GYJrN7KqsqD1oGOftIoVQOTC0TTxADUTgkDvfcZYRNmmroFXbfl/QgPIwGMkd+ 3Hlrw6+tEPNXEHdEBn8/lMnaH19Lrt29ZBDmywPu0mqyfWRiA1xIIqd7FGHr7jaG 6uvhrSbSdI3KXuUmWvp8QmXbPTIwSyUs2knJ0VupQVOFAHyd5EozJdUgJSb0z68W iWVA0zqPNEWFJ0XO8mlt5xjzfh7ZLFM+8UW2dR4P1HWHhTkF2uG1gbpfKOiPdtJ0 E28OgqGmvlhiCoxSWPZ4blP5VuXaIOhuLwh2leheyDqDuuWktorJ1oolLcwQ90h7 0yG0SLjCwczhbGR5HVE513rFBw52U8dkGvIfwE19nEpiNQbhxUVYbd8KKRcPv9Eo 6vnCW21MXQ1e9+TXDhGy =1jT7 -----END PGP SIGNATURE----- --Apple-Mail=_925CD069-F4D3-483A-B72C-0BC5362FB8C7--