Minutes of the September 28, 2022 Editorial task group meeting are attached.
Randy
IBIS Editorial Task Group Minutes
September 28, 2022
Attendees:
Intel Corp. Michael Mirmak*
Micron Technology Randy Wolff*
Siemens EDA Arpad Muranyi*, Weston Beal
Teraspeed Labs Bob Ross*
Minutes by Randy Wolff
--------------------------------------------------------------------------------
Call for Patents: none
Review of Minutes:
Minutes from September 21, 2022 were reviewed. Arpad moved to approve. Bob
seconded the motion. Minutes were approved.
Review of Actions Required:
Michael reviewed ARs from the September 21, 2022 minutes.
Michael to research if a collection of sections in individual documents
could later be collated into a larger final document [AR]
- Michael looked into taking the original 7.2 document, deleting portions
down to individual chapters, and accepting deletions. Chapters 8 and 11
caused issues with change tracking enabled. Michael concluded the concept
is implementable, but it will be harder to see cross references and do
searches. Bob asked how the page numbering will work once the master
document with separate chapters is put together. It's unsure if the figure
numbers as well will be numbered properly. We may also need to compress
some figures to reduce the KB/page.
Agenda:
Review Draft Tree:
Bob showed there is no change to the tree diagram in the IBIS specification,
since there are no new keywords. There is a change in the [IBIS Ver] notes to
show support for 7.2 for all file types.
The IBIS evolution document renamed the "7.1" column to "7.1/7.2" and added a
brief description of changes in IBIS 7.2. Arpad suggested adding "redriver"
to "reference flow changes".
Review Clock Times Clarifications:
Arpad started a BIRD draft to clarify the clock_times definition section when
Rx_Use_Clock_Input is used in a Rx AMI model.
Randy had commented that "single input" and "dual input" concepts were first
used here, so they should be explained. Section 10.2.2 "Application
Scenarios" does mention "dual" models. This is the other use of the "dual"
description.
Some text is added to describe the change in sampling time when a Data model
gets clock_times as an input from a Clock model.
Randy had added a comment about the sampling time being subject to multi-UI
delays within the Clock or Data DLLs. A sentence describing this may need to
be added.
Arpad wanted to clarify the rule about usage of "-1" in the clock_times
vector. Michael thought the use of "shall" vs. "may" (as in "tool" vs.
"model") was ok in its current usage.
Review of the word "continuous" describing the waveform continuity between
GetWave calls seemed to be the most appropriate word.
Arpad will prepare a version of the BIRD draft that modifies the clock_times
text already edited in the 7.2 draft document [AR].
Next Meeting Scheduling:
October 5, 2022
Bob moved to adjourn. Arpad seconded.
Meeting adjourned at 9:00 a.m. PT.
