Thanks Mike for confirming that. The reason I asked is because I wanted
make sure I was not commenting on an older version which might have been
cleaned up already regarding the following.
I tried to respond to Bob's proposed syntax, and fulfill my AR to make
a proposal illustrating my comments from the meeting today. In order
to do that correctly, I wanted to make sure that I understand what we
have in the v21 draft, so I wouldn't propose something totally wrong.
So I started to read this area of v21 in detail to understand the meaning
of the various items that go in the Terminal line. I am sorry to say
this, but this area of the v21 draft is basically "all over the place"
making not much sense at all. I think we need to clean this up before
we can have any meaningful discussion on the syntax of Terminal.
Let's start with the 2nd paragraph under "Terminal rules" on pg. 7 in v21.
It says:
"The Terminal subparameter is followed by at least three arguments:
Terminal_number, Terminal_ID and Terminal_Location. An unlimited number of
Qualifiers may optionally follow each of these three required arguments."
Based on this, I put a commented "column header" above the first example
like this so that I don't forget what each of these columns mean:
| Terminal_number Terminal_ID Terminal_Location Qualifiers (optional)
Terminal 1 Pin_A_signal D1
Terminal 2 Pin_A_signal D2
Terminal 3 A_signal D1
Terminal 4 A_signal D2
I think we are OK with the "Terminal_number" paragraph, although I think we
should use a capital "N" for "Terminal_Number" to be consistent with the
capital "L" in "Terminal_Location".
The next section "Terminal_ID" starts making me wonder. It says:
Terminal_ID is a string, which shall match one of the following:
a [Pin] name
a signal_name
a model_name
"Default"
The example above doesn't seem to have any of these items in the
Terminal_ID column, it seems to be using reserved names. The next
section "Terminal_Locations" says the following:
Terminal_Location
Terminal_Location is a string, and shall have one of the values:
Pin_A_signal
Pad_A_signal
A_signal
Pin_Signal_name
Pad_Signal_name
A_Signal_name
A_puref
A_pdref
A_pcref
A_gcref
A_extref
It seems that the example uses these in the Terminal_ID column. Similarly,
the Terminal_Location Rules section and the example is mismatched the same
way. Here is just the first one of them for illustration:
"Pin_A_signal indicates this terminal is the buffer's A_signal_terminal and is
connected to a specific pin. Terminal_ID shall be a Pin_name, Model_name or
Default."
Either the example(s) is(are) wrong or the text. Also, what is
"A_signal_terminal"? Is that defined anywhere?
Then we have the Qualifiers which I am skipping over for now. After the
Qualifiers comes the "Pre-layout Terminals" section. The first sentence
says:
"If a terminal uses either Default or Model_name qualifiers..."
Well, "Default" or "Model_name" are listed above as "Terminal_ID", not as
"Qualifier"-s. (Also we should decide how these items are capitalized,
because they seem to be spelled totally randomly).
Then it goes on to say "If a "Pre-Layout" terminal is connected to a
differential model,"
with a list of the differential version of the reserved names listed
under the Terminal_Location items. I don't see anything about single
ended buffers here. Does that imply that we can only support differential
buffers for pre-layout? Also, why is this placed after the Qualifiers
section when it deals with the strings which are related to Terminal_Location
that was discussed before the Qualifiers?
I think this section (and/or the examples) need a little bit of scrubbing...
Thanks,
Arpad
===============================================================================
-----Original Message-----
From: Mike LaBonte [mailto:mlabonte@xxxxxxxxxx]
Sent: Wednesday, July 22, 2015 1:55 PM
To: Muranyi, Arpad
Cc: 'IBIS-Interconnect'
Subject: RE: [ibis-interconn] Re: Possible Terminal Reformat
Revision 21 of the Interconnect BIRD is the latest online and also the
last one I have received by email.
Mike
-----Original Message-----
From: ibis-interconn-bounce@xxxxxxxxxxxxx
[mailto:ibis-interconn-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad
Sent: Wednesday, July 22, 2015 1:15 PM
To: Bob Ross; IBIS-Interconnect
Subject: [ibis-interconn] Re: Possible Terminal Reformat
Guys,
What is the latest revision of the Interconnect proposal?
I have rev21, is there a newer one?
Thanks,
Arpad
==========================================================
-----Original Message-----
From: ibis-interconn-bounce@xxxxxxxxxxxxx
[mailto:ibis-interconn-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross
Sent: Wednesday, July 22, 2015 12:08 PM
To: IBIS-Interconnect
Subject: [ibis-interconn] Possible Terminal Reformat
All,
Attached is a proposed revision for terminals.
I added Pin_A_rail (or Pad_A_rail) for supply descriptions at the pin or
pad.
Bob
--
Bob Ross
Teraspeed Labs
http://www.teraspeedlabs.com
bob@xxxxxxxxxxxxxxxxx
Direct: 503-246-8048
Office: 971-279-5325
------------------------------------------------------------------
The IBIS Ad Hoc Interconnect Task Group Mailing List
Archives are available at:
//www.freelists.org/archives/ibis-interconn
TO UNSUBSCRIBE:
Send a message to "ibis-interconn-request@xxxxxxxxxxxxx"
with a subject of "unsubscribe"
To administer your subscription status from the web, visit:
//www.freelists.org/list/ibis-interconn
Meeting minutes and files are available; visit:
http://www.eda.org/ibis/interconnect_wip/
------------------------------------------------------------------
The IBIS Ad Hoc Interconnect Task Group Mailing List
Archives are available at:
//www.freelists.org/archives/ibis-interconn
TO UNSUBSCRIBE:
Send a message to "ibis-interconn-request@xxxxxxxxxxxxx"
with a subject of "unsubscribe"
To administer your subscription status from the web, visit:
//www.freelists.org/list/ibis-interconn
Meeting minutes and files are available; visit:
http://www.eda.org/ibis/interconnect_wip/
