X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Message-ID: <50A3C9D4.6090109@laserlinc.com> Date: Wed, 14 Nov 2012 11:41:56 -0500 From: Joshua Lansford User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] slotting References: <50A2B84F DOT 4080204 AT laserlinc DOT com> <50A3AAA6 DOT 1080704 AT laserlinc DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com On 11/14/2012 10:55 AM, Peter C.J. Clifton wrote: > In the gEDA world, this isn't slotting per-se, but having multiple > symbols to connect different parts of a complex chip is common practice. > > What I would do is to ignore slots, and make two separate symbols (if > you want to separate transmit and receive). Each will be instantiated > with the same refdes (e.g. OPTO1 or something like that), and the > netlist will "just work". Each symbol can just use the pins it requires. > > This probably won't play well with the renumber tools out there, and > I'm not sure it is a good idea to try and trick them by invoking > slotting. Just for the record, refdes_renum_slots intentionally support this too. I have an FPGA in which is split into multiple banks. If --force is specified on refdes_renum_slots, any symbols in a group stay in the same group even if it gets assigned a new refdes number. Then gattrib_csv can be used to edit the properties of the FPGA using LibreOffice and when imported back in it duplicates the data into every symbol (bank) in the group.