Randy, (and Everyone),
Thanks for the suggestion, I like it, so I made a draft 5 with your text
instead of mine (attached).
We still need to figure out how to go about “NC”, though. Any suggestions,
anyone?
Remember, the issue I stumbled on is that currently the spec says that for I/O
pins only two
columns are allowed, while the “NC” reserved word would go into the 3rd column
if we allowed
it… Should we allow three columns for I/O pins if (and only if) the 3rd column
contains “NC”?
Thanks,
Arpad
===============================================================================
From: Randy Wolff (rrwolff) <rrwolff@xxxxxxxxxx>
Sent: Wednesday, January 19, 2022 5:31 PM
To: Muranyi, Arpad <Arpad_Muranyi@xxxxxxxxxx>; ibis-macro@xxxxxxxxxxxxx;
IBIS-Interconnect <ibis-interconn@xxxxxxxxxxxxx>
Subject: RE: [EXT] [ibis-macro] BIRD draft 4 on relaxing the [Designator Pin
List] requirement
Hi Arpad,
Here is my attempt at shortening the [Designator Pin List] text from your BIRD
draft. I’m not sure the pin_name, signal_name, and bus_label mentions are
necessary, and I used less formal versions of the keywords, as is common in
these types of descriptions.
Your Draft 4 text:
“The keyword and the list of its subparameters shall be followed by at least as
many rows of information as needed to provide a matching designator pin_name,
signal_name or bus_label entry for each terminal line Qualifier_entry that
references a designator pin_name, signal_name or bus_label of all [EMD Model]
keywords which are contained by all those [EMD Set] keywords which are
referenced by all those [EMD Group] keyword which are enclosed by the [Begin
EMD] / [End EMD] keywords in which the [Designator Pin List] keyword is
located. Designator pin names which are not referenced by any terminal line
Qualifier_entries in any of the [EMD Model]s may optionally be listed under the
[Designator Pin List] keyword.”
My text:
“The keyword and the list of its subparameters shall be followed by rows of
information containing all designator pins referenced by terminal lines found
in all the EMD Models contained by EMD Sets and referenced by all EMD Groups
found in the .emd file. Designator pin names which are not referenced by any
terminal line Qualifier_entry in any of the EMD Models may optionally be listed
under the [Designator Pin List] keyword.”
Thanks,
Randy
From: ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>
<ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>> On
Behalf Of Muranyi, Arpad
Sent: Tuesday, January 18, 2022 12:57 PM
To: ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx>;
IBIS-Interconnect
<ibis-interconn@xxxxxxxxxxxxx<mailto:ibis-interconn@xxxxxxxxxxxxx>>
Subject: [EXT] [ibis-macro] BIRD draft 4 on relaxing the [Designator Pin List]
requirement
CAUTION: EXTERNAL EMAIL. Do not click links or open attachments unless you
recognize the sender and were expecting this message.
Hello Everyone,
Attached is draft 4 of the BIRD that I wrote for relaxing the requirement of
having to include all designator pin names in the [Designator Pin List] keyword.
The color coding is as follows: original BIRD draft text – no color. draft 2
= yellow,
draft 3 = green, draft 4 = cyan. The reason I made the changes in cyan is
because
the corresponding words were not correct in the previous draft. (Thanks for
Curtis to point that out). The sentence is still long and complicated, so I am
open
to suggestions on how to make it easier to read.
Note that I still didn’t add the text for making ‘NC’ available, since I am
waiting
for some discussions on that topic to answer some of my questions that I raised
in a previous email.
I hope we can discuss this in the Interconnect meeting tomorrow.
Thanks,
Arpad
=====================================================================
