Attila Kinali wrote: > Well, that's normal with schematics. Ok, the OGD1 schematics > are not the nicest, but they are clean and not badly structured. > The schematics are in the complexity of maybe a program with 10-30k loc > of C code. You don't expect to read that like a book and imediatly > know which function is calling which and where they finaly end up, do you?
There are *two* purposes, or rather audiences, for the schematics: There are engineers who need the schematic in order to build and/or modify the fine structure of the design, and ultimately to generate a PCB layout for assembly. Then there are users and programmers, who want a schematic to tell them how the device works in concept. This can also be useful to engineers as an introduction to the more detailed schematic. This is sometimes served by a "block diagram" rather than a schematic. In such a diagram, you omit all of the power-supply and ground connections, and just focus on buses, chips, and the most important control/enable lines. Also, pin numbers are totally unimportant, so you omit those too. (The only ones that might matter are the ones on the PCI interface connector). That's what I was thinking about attempting, though I haven't really gotten started (I started doing chip pinouts instead). Also, I got kind of frustrated with Dia, which is what I was going to use for that. There isn't really a mode for it -- I think I might be able to use some of the flow chart objects. But I'm disappointed. I can do the whole thing in Inkscape, of course, but that's more tedious during the discovery process (I don't know exactly what I'm drawing). Cheers, Terry -- Terry Hancock ([EMAIL PROTECTED]) Anansi Spaceworks http://www.AnansiSpaceworks.com _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
