Re[2]: Bird38

Text item:

Bob,
     An enhancement needs to be made to RAIL. I propose we simply add a width
column to [Budgets] and a width parameter to [Clocks] that has a max of 6
characters. The WIDTH parameter would simply state the maximum time a signal
could overshoot high or low at the already specified level. Would you like me
to type up another ROAD?
John Keifer

John and Ahmed:

We have all had a "vacation" from IBIS committee discussions and
need to get restarted in our discussions. I do not have answers
to your questions, but this will be subject for discussion at the
Friday Meeting. Along with Egg12, Ahmed Omera also submitted
a dynamic noise proposal a long while ago which also in in the
Specification enhancement category.

Jon Powell had proposed a Specification sub-committee to consider
all proposals together, but we have not acted on this yet.

My preference is that any enhancement be simple. While some of the
proposals involve tables, I suspect that the practical reality is
that (1) there is too much data for anyone to really specify, and
(2) very few vendors will consider processing that specific
enhancement. Also, I favor consistency with the existing conventions
and structure rather than adding very specific, special purpose,"warts".
By this, any extension needs to work with all of the technologies and
be meaningful for all of the columns.

Anyway, this is what we can consider on Friday.

Bob Ross,
Interconnectix, Inc.

> To: ibis@vhdl.org
> Subject: Bird38

> Hello all,

> Since proposing bird 38, I have received little comment. As I was not
> able to attend the last two meetings, this is probably my fault.

> This bird is closely associated with egg12 i.e. it is a
> specification addition.

> Bird38 is basically a way to specify under- and overshoot limits.

> A simplification of this bird would be to just give two numbers,
> max_undershoot and max_overshoot. This is what a lot of simulators
> do, and there is a place to stick these numbers into a RAIL file.

> But in this case, over what time span is the over/undershoot allowed
> to be present. I have read through the RAIL doc, but cannot find an
> answer to this question.

> What do people out there understand by over/undershoot limits, as
> used in present simulators?

> All feedback appreciated.
>
> Cheers,
> John

>
> --
> John Fitzpatrick <John.Fitzpatrick@ln.cit.alcatel.fr>
> Alcatel CIT, 4 rue de Broglie, 22304 Lannion, France
> Tel: (+33)96.04.79.33 Fax: (+33)96.04.85.09

Text item: External Message Header

The following mail header is for administrative use
and may be ignored unless there are problems.

***IF THERE ARE PROBLEMS SAVE THESE HEADERS***.

Cc: rail@vhdl.org
Subject: Re: Bird38
To: John.Fitzpatrick@ln.cit.alcatel.fr, ibis@vhdl.org,
        omera@trailblazer.sps.mot.com
From: bob@icx.com ( Bob Ross)
Date: Thu, 5 Sep 96 13:01 PDT
Message-Id: <m0uykbt-000GjSC@icx.com>
Received: by icx.com (/\==/\ Smail3.1.28.1 #28.14)
     id <m0uykbt-000GjSC@icx.com>; Thu, 5 Sep 96 13:01 PDT
Received: by icx.com (/\==/\ Smail3.1.28.1 #28.14)
     id <m0uykZa-000FVYC@icx.com>; Thu, 5 Sep 96 12:58 PDT
Received: by icx.com (/\oo/\ Smail3.1.29.1 #29.2)
     id <m0uykZd-001s04C@icx.com>; Thu, 5 Sep 96 12:58 PDT
Received: from icx.com (root@fw.icx.com [205.238.6.33]) by vhdl.vhdl.org (8.7.3/
8.7.3) with SMTP id NAA11975; Thu, 5 Sep 1996 13:09:15 -0700 (PDT)
Received: from vhdl.vhdl.org (VHDL.VHDL.ORG [198.31.14.3]) by mailbag.jf.intel.c
om (8.7.4/8.7.3) with ESMTP id OAA04146; Thu, 5 Sep 1996 14:55:21 -0700 (PDT)
Received: from mailbag.jf.intel.com (root@mailbag.jf.intel.com [134.134.248.4])
by fmmail.fm.intel.com (8.7.4/8.7.3) with ESMTP id OAA18904; Thu, 5 Sep 1996 14:
56:27 -0700 (PDT)
Return-Path: owner-rail@vhdl.vhdl.org
Received on Mon Sep 16 10:18:42 1996