JosephBlack poked me and told me to contribute to the PCI analyzer discussion -- I have a backlog of about 450 emails from the list so there might be some things I've missed.
Anyway... On Fri, 2007-01-05 at 17:21 -0500, Timothy Miller wrote: > Not convenient. Absolutely necessary. From a usability standpoint, > there's no good reason to have them separate. You are /quite/ right. > > 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. Then to be able to specify which ones you DO > have could cost you more bits. I agree completely. > > We need a file format for the data files. > > > > magic string > > format version number > > data, including user specified strings for signal names > > checksum > > allow for comments (e.g '#' ) > > allow for demand paging (how?) > > We should look at VCD format to see if it serves our purposes well. As far as I can see, it does. It is easy to output VCD and it naturally handles "delta encoded" data, i.e. only signal changes get represented in the file. The file creator is free to save the status of all signals all the time, too. > > We need setup/rc type file for 2 > > > > specify trigger condition > > specify capture window start and stop times relative to trigger > > specify which signals to capture > > specify resolution (samples per second) > > user specified strings for signal names > > comments > > Some stuff needs to go into an rc file. We should also be able to let > the user load some of these (like trigger conditions) in separate > files. And most importantly, there should be an intuitive way to > enter them into the GUI. If it needs to go to a file (and not be a set of gconf settings), please make it a simple KEY=VALUE format. My preference is to use gconf (or whatever one the KDE equivalent is). > > Are there existing protocols or file formats that we could use > > and gain compatibility? > > VCD is the only one I know about. But it may not be appropriate. One > option is to use VCD, and for any metadata that we want but can't > store conveniently in the file, we can add as signals that people > wouldn't typically view. VCD is fine. If we need metadata, we can hide them in comments. -Peter _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
