Re: [IBIS] BIRD161.1: Supporting Incomplete and Buffer-only [Component] Descriptions

From: Todd Westerhoff <twesterh@sisoft.com>
Date: Tue May 14 2013 - 15:52:55 PDT
You could also use something like "Pre-route" and "Post-route", which provides a clearer indication of intended use.

Todd.


-- 

Todd Westerhoff
VP, Software Products
SiSoft
6 Clock Tower Place, Suite 250
Maynard, MA 01754
(978) 461-0449 x24
twesterh@sisoft.com
www.sisoft.com
 
 
“I want to live like that"
                                             -Sidewalk Prophets
 

On May 14, 2013, at 3:31 PM, Mike LaBonte <mike@labonte.com> wrote:

> The Scope sub-parameter here has values "Partial" and "Complete". I
> believe these are intended to denote the case where an IBIS file
> includes only enough data to model something like one interface for
> early analysis, and the case where the file is ready to be dropped in
> for full post-layout simulation. We may however want to define the
> term "Complete" a little more carefully though, preferably stating
> what the file can be used for.
> 
> For example, some might wonder whether a [Pin] section with no
> power/ground or JTAG pins can be called "complete". Each model maker
> decides what subset of pins they will support, and at the end of the
> day whatever they decide is as complete as the model will ever be. The
> fear is that some may not be sure when to use "Complete", particularly
> where automation is used to make the models. A simple check of [Pin]
> count against the full pin list may not be helpful.
> 
> Might a term like "EntireDevice" work better than "Complete"? Or is
> this no better?
> 
> Mike
> 
> On Mon, May 13, 2013 at 1:20 PM, Mirmak, Michael
> <michael.mirmak@intel.com> wrote:
>> BIRD161.1, Supporting Incomplete and Buffer-only [Component] Descriptions,
>> has been posted.  This revises BIRD161 to include fixes to the statement of
>> [Pin] keyword rules.
>> 
>> 
>> 
>> The text may be found at http://www.eda.org/ibis/birds/bird161.1.docx (the
>> text is not attached here due to a reflector policy prohibition on
>> attachments). The BIRD will be discussed at the next IBIS Open Forum
>> teleconference.
>> 
>> 
>> 
>> A complete list of BIRDs, including the status of each, is available at:
>> http://www.eda.org/ibis/birds/
>> 
>> 
>> 
>>      Michael Mirmak
>> 
>>      Intel Corp.
>> 
>>      Chair, IBIS Open Forum
>> 
>> 
>> 
>> 
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> --------------------------------------------------------------------
> |For help or to subscribe/unsubscribe, e-mail mikelabonte@eda-stds.org
> |or ibis-request@eda-stds.org
> |
> |IBIS reflector archives exist under:
> |
> |  http://www.eda-stds.org/ibis/email_archive/ Recent
> |  http://www.eda-stds.org/ibis/users_archive/ Recent
> |  http://www.eda-stds.org/ibis/email/         E-mail since 1993

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail mikelabonte@eda-stds.org
|or ibis-request@eda-stds.org
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/ibis/email_archive/ Recent
|  http://www.eda-stds.org/ibis/users_archive/ Recent
|  http://www.eda-stds.org/ibis/email/         E-mail since 1993
Received on Tue May 14 15:53:41 2013

This archive was generated by hypermail 2.1.8 : Tue May 14 2013 - 15:55:45 PDT