From: Yonghao Chen (firstname.lastname@example.org)
Date: Thu May 05 2005 - 06:08:41 PDT
In the case where timing check event occurs before the limit,
the $skew check will not turn dormant, and it will continue
reporting violations for timing check events after the limit.
I'd think $timeskew in the event mode should behave the same.
But in timer based mode, $timeskew should turn dormant upon
the first timing check event within the limit.
> In $skew, if there is a timestamp event and then a series of timecheck
> events after expiration of the time limit, a violation is reported on
> each such timecheck event.
> If a timecheck event occurs before expiration of the time limit,
> a violation is not reported.
> What happens if there is a series of timecheck events, one or more
> before expiration of the time limit and one or more after the time limit.
> Does $skew turn dormant after a timecheck event within the time limit,
> or does it continue to check each timecheck event which follows the
> timestamp event, even if there was a timecheck event before the time
> limit expires?
> The LRM implies that $skew remains active even after a timecheck event
> within the time limit ("$skew shall report timing violations for all data
> events occurring beyond the limit after a reference event."), but I am
> not sure that was the intent.
> Presumably, $timeskew in event based mode with remain active flag set
> would work the same way.
> $fullcheck is different in any case, though.
> Shalom.Bresticker @freescale.com Tel: +972 9 9522268
> Freescale Semiconductor Israel, Ltd. Fax: +972 9 9522890
> POB 2208, Herzlia 46120, ISRAEL Cell: +972 50 5441478
> [ ]Freescale Internal Use Only [ ]Freescale Confidential Proprietary
This archive was generated by hypermail 2.1.4
: Thu May 05 2005 - 05:44:33 PDT
sponsored by Boyd Technology, Inc.