> >>> 1) a data gatherer on the OGD1 itself > >>> > >>> 2) a program to control the data gatherer and upload data > >>> > >>> 3) a program to display the data
> >>> We need a protocol for communication between 1 and 2. > >>> > >>> specify trigger condition > >>> specify capture window start and stop times relative to trigger > >>> specify which signals to capture > >>> > >> I think we would usually capture them all. The best you could do is > >> shave off a few bits. > >> > > > > I'm not familiar with the signals on the PCI bus. Would it always be > > necessary to look at the data bits, or would the control lines be > > sufficient in most cases? If you can eliminate 32 or 64 signals > > then the data would upload faster. And potentially allow storing more > > samples in memory. > > > > > You pretty much have to have the address, and probably the data too, but > since they are the same lines, if you are capturing one you get the > other "for free". Okay, let's move "specify which signals to capture" to the "probably not worth doing" list. > > 2 and 3 might be running on different machines. > > KISS. Properly written it would be reasonably straight forward to put a > network interface between 2 and 3. But we need working software more > than we need to cover every possible feature and use case. I think it will be possible to seperate 2 and 3 without violating KISS or making the project take longer. In fact, I think it will get us there faster and safer. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
