[ibis-macro] IBIS-ATM teleconference - Agenda for 6/21/2011

  • From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
  • To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx>
  • Date: Tue, 21 Jun 2011 15:22:27 +0000

Time:  June 21, 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_tips.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:


Arpad:  Submit the two BIRD drafts which were voted on to the 
        IBIS Open Forum
        - done

Arpad:  Send an email to the IBIS-Editorial reflector to start
        the editorial process on the correction BIRDs
        - done

All:    Please send comments to Arpad by email on the topic
        of how Corner typ/slow/fast should be associated with
        typ/min/max in IBIS
        - in progress



Any other 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)  AMI_ParametersOut_BIRD draft (Row 51)                 (Arpad)
    - any final comments, questions on the BIRD draft?
    - vote to submit it to the Open Forum


5)  IBIS-AMI Section 6c Tables Update                     (Bob)
    (Table1_3_BIRD_draft_1.pdf)
    - is this ready for a vote to submit it to the Open Forum?


6)  AMI_CornerRange_BIRD draft (Row 54)                   (Arpad)
    - decide what to do about associating typ/slow/fast of
      Format Corner with legacy IBIS typ/min/max
      - leave it vague?
      - rely on a C_comp fix (Bob's BIRD, or similar)?


7a) BIRD 121, data management parameters (file support)  (Walter)
     - questions, comments?

7b) BIRD 122; Analog Buffer BIRD                         (Walter)
     - replaced with ISS_Buffer_BIRD.doc

7c) 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?

7d) BIRD 124.1, dependency table                         (Walter)
     - questions, comments?


8)  Info, Out, InOut BIRD                                 (Arpad)
    - changed words to include "in order to be compliant with this
      specification, Model_Specific parameters ... must not ..."
    - changed wording so that "simulation" is not used so it's
      meaning wouldn't have to be defined
    - any comments, questions on this draft?
    - is this ready for submission to the Open Forum?


9)  Backchannel BIRD draft                               (Walter/Ken)
     - questions, comments?





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 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 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 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: