[ibis-macro] IBIS-ATM teleconference - Agenda for 5/24/2011
- From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
- To: "IBIS-ATM" <ibis-macro@xxxxxxxxxxxxx>
- Date: Tue, 24 May 2011 06:10:41 -0700
Time: May 24, 2011 Noon US Pacific Time
=====
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
Web
===
Click Here to Join Live Meeting:
http://tinyurl.com/yvmesj
or:
https://www.livemeeting.com/cc/sisoft/join?id=NKQQN3&role=attend&pw=TP8j
%23-%25%7E5
Mentor Global Crossing Teleconference commands:
http://www.globalcrossing.com/customer/collaboration/cust_ready_access_t
ips.aspx
FIRST TIME USERS: To save time before the meeting, check your
system to make sure it is compatible with Microsoft Office Live
Meeting.
---------------------------------------------------------------------
Agenda
======
1) Opens
2) Call for any related patent disclosures
3) Review of ARs:
Did we have any AR-s?
Old ARs:
Arpad: Review the documentation (annotation) in the macro libraries.
- deferred until a demand arises or we have nothing else to do
4) (Format) Table Syntax Clarification (Row 21, 22) (Bob)
- last minute questions, comments?
- vote for submitting it to the Open Forum
- finish the BIRD draft(s) which are on hold
(#13?, #14? below)
5) AMI_BooleanBNF_BIRD draft (Row 55) (Arpad)
- last minute questions, comments?
- vote for submitting it to the Open Forum
6) AMI_CornerRange_BIRD draft (Row 54) (Arpad)
- discussion on the content of the BIRD draft
- BIRD 127.1 update (fix example on pg. 147) (attached)
7) AMI_ParametersOut_BIRD draft (Row 51) (Arpad)
- discussion of the content of the BIRD draft
(this defines/clarifies the rules for the
**AMI_parameter_*** and **msg function arguments)
- BIRD 127.1 update (fix example on pg. 190) (attached)
8) AMI_FunctionReturnValue_BIRD draft (Row 61) (Arpad)
- is the verbiage on sending feedback to the tool
and user sufficient, or do we need more specifics
(msg...)?
9) Info, Out, InOut BIRD (Walter)
- Presentation describing Compliance, as related to
Model Specific parameters
10) Out/InOut BIRD draft (Arpad)
- discussion on the latest revision posted on the
ATM website
11a) BIRD 121, data management parameters (file support) (Walter)
- questions, comments?
11b) BIRD 122; Analog Buffer BIRD (Walter)
- replaced with ISS_Buffer_BIRD.doc
11c) BIRD 123.2.2, jitter parameters (includes Row 37) (Walter)
- review latest changes and graphics
- do these changes answer the questions raised before:
- remove Usage Out from the BIRD? or
- specify which function (Init or GetWave) can return values?
- specify what the EDA tool should do with the returned values?
11d) BIRD 124.1, dependency table (Walter)
- questions, comments?
12) Backchannel BIRD draft (Walter/Ken)
- questions, comments?
13) IBIS-AMI Section 6c Tables Update (Table1_3_BIRD_draft_1.pdf)
- this is on hold until all related items are defined
14) Define relationship between Type and Format (Row 25 in Task List
Type_Format_Table_BIRD_02.pdf)
- this is on hold until all related items are defined
Remaining Task List items:
==========================
Row 21: According to the BNF, the Format = Table syntax is invalid.
- If Format is removed, this s not a problem, but if Format
is there the problem still exists. Do we need to fix this?
- we will address this when talking about Table
Row 22: The syntax for a leaf is:
(Row 22 in Task List)
<leaf>: ( <parameter name> whitespace <value list> )
So in a Table which is written like this: (-50 -0.1 1e-35),
-50 is actually a parameter name, i.e. a string, not a value.
-deprecate Table back to List?
- we will address this when talking about Table
Row 23/24: Fix the two tables to reflect what is in the text
- Bob started a BIRD draft which will be finalized
as other BIRDs are completed
Row 25: Define relationship between Type and Format
- Ambrish started a BIRD draft which will be finalized
as other BIRDs are completed
Row 35: Clarify questions about impulse response
- this needs to be discussed
Row 37: Usage Out for reserved (jitter) parameters
- which function (Init or GetWave) can return these?
Row 46/47: Remove certain parameters and keywords
- this needs to be discussed
Row 51: AMI_parameters_out
- optional for AMI_GetWave only?
- specify that if not returned the pointer should be a valid NULL
pointer
- do the same for AMI_parameters_in (NULL pointer)
Row 52: What should the tool do without clock times?
(postponed)
- need to specify how the tool should sample the waveform
- address other SERDES protocols which use external clocking
Row 53: Labels BIRD draft from Walter?
(postponed)
Row 54: Format Corner and Range interpretation
- spell out what makes the selection for Corner and Range
- is it the tool's corner setting?
- if so, how does typ/min/max align with typ/slow/fast for Corner?
- is it supposed to be shown in a GUI for the user to make a selection?
Row 55: Add Boolean to the BNF
Row 56: Should (Usage Out) parameters have Default or a Value at all?
Row 57: Existing Reserved_Parameters of (Usage Out) need
definition for which function returns them (Init or GetWave)
(postponed)
Row 58: Model_Specific parameters should not be (Usage Out)
or (Usage InOut)
(postponed)
Row 59: Make sure Table 1 on pg. 148 doesn't show
Ignore_Bits as Out
(this is just a reminder for Row 23)
Row 60: Clarify what kinds of failures should result in
"0" in the function's return value (Section 3.1.3 and 3.3.3)
- function call failure
- model cannot operate properly (CDR getting out of lock)
Row 61: Are the **AMI_parameters_out arguments of AMI_Init
and AMI_GetWave the same or different memory locations?
- if it is the same, this is inconsistent with **msg
- if not the same, **msg should only be available to AMI_Init...
Row 62: Clarify the **msg argument
- who allocates/deallocates its memory (DLL)?
- IF it is the DLL, it is allocated in AMI_Init.
Will this be available to AMI_GetWave too?
Row 63: Should AMI_Close always be required?
- should the spec say that all memory deallocations
are done in AMI_Close?
- is that possible? (What if AMI_Init or GetWave
allocates memory that is not visible to AMI_close)?
- Currently AMI_Close is not required with AMI_Init,
therefore when AMI_Close is not present AMI_Init
has to do memory deallocations also...
- goal is to make the model maker's life easier,
and this is kind of confusing...
Thanks,
Arpad
=====================================================================
---------------------------------------------------------------------
IBIS Macro website : http://www.eda.org/pub/ibis/macromodel_wip/
IBIS Macro reflector: //www.freelists.org/list/ibis-macro
To unsubscribe send an email:
To: ibis-macro-request@xxxxxxxxxxxxx
Subject: unsubscribe
Other related posts:
- » [ibis-macro] IBIS-ATM teleconference - Agenda for 5/24/2011 - Muranyi, Arpad
