Re: gEDA-dev: Broken slotting

[Stuart Brorson <sdb-at-NOSPAMcloud9_dot_net>]

> Ok, so how about this fix for now...
>
> Keep pinseq as always was in libgeda + gschem, and not update it.
>
> But have spice-sdb take into account slot=? when assigning pin order.
> The only thing I can think which might need adding is guile-accessible
> API to retrieve the slot number and pin-count on the component. These
> may already be do-able though.

IIRC, the original problem was this:  gnetlist did not provide a way
to get the net attached to a pin using pinseq for slots 2, 3, 4....
Spice-sdb needs to get the nets using pinseq since it needs to emit
the pins in a particular order dictated by the ordering of the net
connections in SPICE.  That is, spice-sdb loops over pinseq, and asks
gnetlist for the name of the net attached to pinseq when outputting
netnames.

The code I wrote provided a simple way to get the pin's net by asking
for pinseq modulo the slot number.  That is, if the slotted device
had 14 pins, and the SPICE model required 5 connections, I could ask
for pinseq=7 to get slot=2, pinseq=2.  Or something like that.

If you have a better way to do it, that's fine.  But I'm not sure that
this scheme is broken in any way.  (I am happy to be shown wrong, of
course.)

Stuart


_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev