X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
From:	geda AT psjt DOT org (Stephan =?utf-8?Q?B=C3=B6ttcher?=)
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] first attempt at bus support in gnetlist for pcb
References:	<201601080714 DOT u087Ejj5032766 AT envy DOT delorie DOT com>
Date:	Fri, 08 Jan 2016 10:12:35 +0100
In-Reply-To:	<201601080714.u087Ejj5032766@envy.delorie.com> (DJ Delorie's
	message of "Fri, 8 Jan 2016 02:14:45 -0500")
Message-ID:	<s6negdsige4.fsf@blaulicht.dmz.brux>
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version:	1.0
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

DJ Delorie <dj AT delorie DOT com> writes:

> 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.

Nice!

I guess this works well with non-numeric pin numbers as well?

How would I backannotate a swap of two pin numbers?  The netname cannot
be different on two ends of a simple net.  Is the idea to route from the
bus-pins to a graphical bus, and have the netnames ripped from the bus
in the appropriate order?

If gnetlist would treat connected net segments with different netname=
attribute as not connected the visual distraction of bus rippers could
be avoided for simple busses that need to be reorderd an the ends.

-- 
Stephan

- Raw text -