Re: gEDA-user: gnetlist backend

[<frank@xxxxxxxxxxxxxxxx>]

>-------- Original Message --------
>Subject: Re: gEDA-user: gnetlist backend
>From: Dan White <dan@xxxxxxxxxxxxxx>
>Date: Thu, June 09, 2011 9:29 pm
>To: gEDA user mailing list <geda-user@xxxxxxxxxxxxxx>
>
>
>Since pins are only valid in symbols, give the xPADS component
>instances an attribute to key on. Check out the spice-sdb backend's
>`spice-sdb:get-spice-IO-pins'. The convention in that case is to only
>collect "i/o pins" if there is a component with a
>`device=spice-subcircuit-LL' present in the schematic. Components
>with a `device=spice-IO' attribute are collected for pin names.
>
>On my schematics for IC work (lots of hierarchy), the pin component
>attribute convention is:
>
>device=spice-IO
>port-type=foo
>refdes=PIN_NAME
>value=1
>
>A patch to spice-sdb sorts these by the `value=' attribute instead of
>the refdes.
>
>That and other mostly gnetlist-related patches are in my local fork at:
>http://repo.or.cz/w/geda-gaf/whiteaudio.git (whiteaudio branch)
>
>Dan
>
>-- 
>SDG
>www.whiteaudio.com

Thanks for the thoughts, I was hoping to avoid extra attributes but it
may
be the solution. I'll take a look at the spice-sdb backend and also at
your gEDA fork. Since you are also doing IC work, if you happen to know
of
an open source detail or maze router please let me know. 

-Frank



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