[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-user: Suggestions to handle buses
- To: geda-user@xxxxxxxx
- Subject: gEDA-user: Suggestions to handle buses
- From: "Samuel A. Falvo II" <sam.falvo@xxxxxxxxx>
- Date: Thu, 2 Jun 2005 12:58:36 -0700
- Delivered-to: archiver@seul.org
- Delivered-to: geda-user-outgoing@seul.org
- Delivered-to: geda-user@seul.org
- Delivery-date: Thu, 02 Jun 2005 15:57:43 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=DbUSNukCFDIAObVzyAms1wqnNdx6fMG4E7+eePyVRgZVtexMGluOAFqZcIloqKSGZ0hAS3ew8w18zI4ACpZLcfsYeAh4WkiyJDhw0OzVipmo0Dk8k31SGyPkMUPUEPwq9KN81l7gVnCi2NbNf14Z+Fxwb0rzXtf//wdxLTDOMcM=
- Reply-to: geda-user@xxxxxxxx
- Sender: owner-geda-user@xxxxxxxx
OK, gaining some experience with the schematic->pcb process. I've
gotten pcb to see all my physical components, and it even auto-routes
some of the point-to-point nets. But, it is not handling buses.
I did some research in the gschem documentation, and it seems that
buses aren't fully supported yet (the big issue is how to name them,
and how to name elements within a bus, it seems. This makes sense,
since a bus is a collection of nets).
So, am I left to handle buses manually? Or is there a prescribed way
of handling buses that I'm missing?
Also, the io component library has input-2 and output-2, which
references nets in the attributes. I suppose that the proper way of
handling buses across multiple schematic sheets is to manually list
each element of a bus with a separate input/output-2?
Thanks for the help.
--
Samuel A. Falvo II