Audio ===== Voice dial-in: 877-384-0543 Passcode: 1371-5030 Web === Click Here to Join Live Meeting https://www.livemeeting.com/cc/sisoft/join?id=NKQQN3&role=attend&pw=TP8j%23-%25%7E5 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) Review of ARs: 2) The world's first (?) PDA model and simulation in VHDL-AMS (by Arpad) 3) Continue the discussion on the Cadence API proposal. Still looking for a way out of the gridlock in which we are finding ourselves. Our main question seems to be whether we want to make it easier on the model maker or the tool. This is related to the question whether we should ask tools to support many languages and do the compilation or whether the model should do the compilation (most likely on multiple OS-s, etc...) What makes this decision harder is that model makers seem to have different favorite languages, and some times there are existing infrastructures which are difficult to change or leave behind. The summary from before still seems to be valid: o API for compiled vs. ASCII readable model - compiled models not desirable because separate compilations would have to be generated for each OS and compiler switch settings can make things incompatible very quickly - binary format not sufficient for IP protection - encrypted (and/or obfuscated) ASCII models may be the best o C vs. *-AMS or linear vs. non-linear simulation engine? - the 10 million bits per hour capability is due to using a linear simulation engine, not because of the choice of the C language - no linear simulators exist today which can use *-AMS - the assumption of linearity may not be sufficient - existing infrastructure: it is too big of a burden to rewrite existing libraries in another language or request model makers to learn a new language. Should both C and *-AMS be supported? o Is there a need for a new API in IBIS? - there are numerous (standard) API-s on the market already - the existing [External Model] or [Extern Circuit] keywords may be used for this purpose (with small modifications) o Specification related questions - do not standardize methodologies, it prevents evolution - prefer flexible definitions which are extendable later - should this be part of the IBIS specification, or a new, independent specification? --------------------------------------------------------------------- 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