Time: Tuesday, November 20, 2018 at Noon US Pacific Time
=====
WebEx:
======
https://sisoft.webex.com/sisoft/j.php?MTID=m1775c35b7d9a55735fbb2c67876222ba
Meeting Number: 735 161 627
Meeting Password: IBIS
Audio:
======
Voice dial-in: (800) 637-5822
International: +1 (647) 723-3937 <--- (For Canada)
0114501530 <--- (For Sweden)
0201400572 <--- (For Sweden Toll Free)
069509594672 <--- (For Germany)
08001014542 <--- (For Germany Toll free)
Access Code: 685-0440
Mentor Global Crossing Teleconference commands for audio:
http://www.globalcrossing.com/customer/collaboration/cust_ready_access_tips.aspx
---------------------------------------------------------------------
---------------------------------------------------------------------
Agenda
======
1) Opens
2) Roll call
3) Review of ARs:
Randy: Investigate if/why/how a clock waveform input might be used
- in progress
Michael M.: Investigate if/why/how a clock waveform input might be used
- in progress
Arpad: Re-send the email about seeking input from redriver vendors on
the AMI redriver flow corrections to the SI-LIST.
- done (no responses so far)
Walter: Send draft2 of the DC_Offset BIRD to ATM. Mike L. to post it.
- done
Any other AR-s?
4) Call for any IBIS related patent disclosures
5) Approval of minutes
- Dependency example in current IBIS spec. Ambiguity?
Need better example?
6) DC_Offset BIRD draft (Walter)
- discussion
7) IBIS-AMI improvements (All)
- Walter's Summary of DDR5 Issues email
- discussion
9) Complex C_comp modeling (Randy)
- discussion?
10) Motion to adjourn?
Topic bin list:
===============
- Removing the single-ended input threshold requirements for
differential buffers
- Removing the single-ended characterization load requirements for
differential buffers
- Guidance for power-aware vs. AMI models - do we have rules for
how a power-aware (and therefore potentially non-LTI) buffer
analog data set should be used with IBIS-AMI algorithmic data?
- Fix all the referencing problems in the current specification
(after Randy's C_comp proposal and BIRD189 are done)
- IBIS-AMI Post Simulation Processing (FEC) (Mike L.)
Tabled topics:
==============
11) New BIRDs from Editorial Task Group? (Bob/Radek)
a) Specify buffer reference terminals for pins ([Pin Reference])
b) Simulation (aka DIA) vs. DUT (depends on #a)
c) C_comp and package reference in simulation clarifications
(depends on #a)
d) Make changes to the [Receiver Threshold], once a) and b) are
resolved
12) 166.4 Resolving problems with Redriver Init Flow (Walter)
13) BIRD190 (Ambrish)
14) Fangyi's Redriver flow BIRD draft (Fangyi)
- add equations
- consider rewriting the AMI "front end" in the spec (flows)
(when this proposal is added to the spec)
15) How to handle missing min/max data? (Arpad)
- what should be the governing rule for synchronizing
typ/min/max data?
Pending BIRDs awaiting discussion:
==================================
166.4 Resolving problems with Redriver Init Flow
181.1 I/V Table Clarifications
190 Clarification for Redriver Flow
TBD New proposal for Redriver Flow (may replace BIRD166)
TBD C_comp modeling with IBIS-ISS
Thanks,
Arpad
=====================================================================
