Timothy Miller wrote:
There have been a number of you who have looked at the schematic,
found some bugs, and commented on it, and we're very grateful for the
help.
Howard has quite a lot more experience with PCB design, so it's no
surprise that he's managed to find a number of additional bugs on his
own since the release. What concerns me is leaving him as a
bottleneck. The great likelihood is that he, being one person,
working on this in his spare time, is going to miss a LOT of bugs, and
if we were to produce that board, it could be disasterous.
Does anyone here have any ideas as to how we might attract some more
experienced PCB designers to the project?
And I have another idea. We have a great deal of highly intelligent
software people on this list. Unfortunately, it's a huge learning
barrier for them to try to make sense of the schematic. Maybe we
should try to break it down, page by page. With enough people
discussing it and asking what the heck things mean and all that, it
could be a fun learning experience (not to mention valuable for your
resume).
In one sense, this project is going to take as long as it takes.
We're all contributing in our spare time, and it's difficult. But on
the other hand, I'm anxious to have an open-architecture graphics card
in my computer, and anything we can do to enhance the rate of progress
will be a boon for the project.
Any suggestions?
A large part of the schematic really doesn't show a circuit. At least
this isn't the type of circuit schematic that I usually draw or look at,
my experience with schematics is mostly analog circuits.
It would probably be easier to verify a net list for much of this.
--
JRT
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
