All,
Regarding "the legacy IBIS model name,"
We only use "legacy" once here in the IBIS Version 7.0 specification and in
the V7.1 drafts.
"Legacy" is not defined. Moreover, the contest is with Reserved_Parameter
Model_Name.
Its definition is below:
Parameter: Model_Name
Required: No, and illegal before AMI_Version 6.1
Direction: Rx, Tx
Descriptors:
Usage: In
Type: String
Format: Value
Default: <string_literal>
Description: <string>
Definition: Name of the IBIS [Model] keyword that is being used.
Usage Rules: Value specified in the .ami file is a placeholder and is
ignored. The EDA tool must pass the name of the IBIS [Model] keyword that is
being instantiated by the EDA tool through the input parameter strings to
AMI_Resolve and AMI_Init functions as the value of this parameter.
-------
This definition excludes "reserved model names" such as POWER, GND, NC, and
CIRCUITCALL. These last four entries can be placed in the model_name
column of the [Pin] keyword, but they are not described as [Model]
model_name entries.
So "legacy IBIS model name" is too ambiguous.
Bob
From: ibis-editorial-bounce@xxxxxxxxxxxxx
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad
Sent: Wednesday, September 8, 2021 2:00 PM
To: ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-editorial] Re: Draft 2 of the Bit Time BIRD
Thanks Mike for sending this out, and for editing it during the meeting this
morning.
Just so everyone knows, we changed the wording of the "UI paragraph" to:
"UI
Unit Interval. 1 UI is the inverse of the symbol rate. For example, 1 UI
of 100 ps for an NRZ channel transmits 10 Gbit/s, while the same 100 ps UI
for a PAM4 channel transmits 20 Gbit/s (or 10 Gsymbols/s). UI parameter
values are in units of UI (symbol time). The parameter may take on either
floating point or integer values."
to make it easier to read (this was already discussed in last week's meeting
a little).
With a few other minor changes made this morning we feel this BIRD is ready
to be
submitted to the IBIS Open Forum, but we would like to give everyone a
chance to
review it before we do so. Please let us know if you can think of any other
related
areas in the IBIS v7.0 specification that should be included in this BIRD,
or if you find
anything that should be changed in this draft.
Thanks,
Arpad
=======================================================================
From: ibis-editorial-bounce@xxxxxxxxxxxxx
<ibis-editorial-bounce@xxxxxxxxxxxxx> On Behalf Of Mirmak, Michael
Sent: Wednesday, September 8, 2021 3:37 PM
To: ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-editorial] Draft 2 of the Bit Time BIRD
Per my AR from today's meeting, here is the revised draft of Arpad's bit
time BIRD.
* MM
