On Thu, Oct 19, 2006 at 01:06:13AM +, Michael Sokolov wrote:
> OK, let's review: buses on schematics are a documentation feature, i.e.,
> intended not for tools but for other engineers looking at the drawing,
> right? Now suppose I want to label my buses for the same purpose: as a
> documentat
[snip]
>> Now suppose I want to label my buses for the same purpose: as a
>> documentation aid for others looking at my schematics. Of course I can
>> just stick a text object next to it that isn't of name=value form, but
>> it seems to me that an attribute would be more appropriate, even if no
>>
> OK, let's review: buses on schematics are a documentation feature, i.e.,
> intended not for tools but for other engineers looking at the drawing,
> right?
Yes.
> Now suppose I want to label my buses for the same purpose: as a
> documentation aid for others looking at my schematics. Of course
DJ Delorie <[EMAIL PROTECTED]> wrote:
> A "bus" is purely decoration. Everything ignores it. All that
> matters is the nets that connect to it and THEY must have net names,
> as usual. Yes, each little connecting net has to be named. That's
> what does the actual work.
OK, thanks for the clar
> 1. There doesn't seem to be any way to indicate how wide a bus is in
>bits, i.e., how many nets should it turn into. Does gEDA not care?
>How can it not care? How many nets is the netlister going to
>generate for a bus?
A "bus" is purely decoration. Everything ignores it. All th
Hello again fellow gEDA users,
As my OSDCU design is a microprocessor system of moderate complexity, I
need to use buses on my schematics -- for my microprocessor's address
and data buses and everything connected to them. I haven't been able to
find any real documentation on buses in gEDA/gaf (al
6 matches
Mail list logo
