Re: [Emc-developers] latency results table on wiki

2013-09-03 Thread Anders Wallin
> Anders: > > I like the idea of scripting the transmission and acquisition of the > test results. It fits with previous noodling on this list about a > standard system information-gathering and reporting scheme which, among > other things, would improve our ability to help people debug their > ins

Re: [Emc-developers] latency results table on wiki

2013-08-29 Thread Kent A. Reed
On 8/29/2013 2:34 AM, Anders Wallin wrote: > How difficult would it be to automatically gather information about the > system (rt-patch, versions, etc.) along with the jitter values and format > them into a standard message (email, whatever). > The website could then have a database which is auto-u

Re: [Emc-developers] latency results table on wiki

2013-08-28 Thread Anders Wallin
How difficult would it be to automatically gather information about the system (rt-patch, versions, etc.) along with the jitter values and format them into a standard message (email, whatever). The website could then have a database which is auto-updated whenever it receives a correctly formatted e

[Emc-developers] latency results table on wiki

2013-08-28 Thread Chris Morley
I am thinking we are going to need to add a column for type of realtime patch with UB coming along soon. I am also thinking that the two columns showing max interval are less useful. removing them would give more room for other text and also help people to concentrate on what is important - jitter