[ibis-macro] Re: Lets go all the way!
- From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
- To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx>
- Date: Mon, 27 Aug 2012 04:07:00 +0000
Walter,
I think you may have misunderstood my comment last Friday,
because I don't remember saying what you write below. I
don't even see myself saying it, because I don't think there
is really a "problem that legacy IBIS combines both package and die
models in .ibs files", because the most accurate package modeling
syntax that is available in IBIS currently allows the [Define
Package Model] keyword (and its content) to be either in the
.ibs or the (separate) .pkg file. Either way, I am really
not very concerned about having things in one or multiple
files.
My comment last Friday was about the mechanism by which the
IBIS specification defines and instantiates [Model]s using
the [Pin] keyword. This was OK in the days when the number
of pins were the same as pads and the package had a one-to-one
pin to pad path. But now that we are talking about arbitrary
pin and pad relations, and now that we are talking about
adding to this an also arbitrary pad to buffer terminal on-die
interconnect modeling capability, we can no longer rely on
defining and instantiating [Model]s using the pin names. I
made the suggestion on Friday, that if we "overhaul" IBIS
with significant changes as you suggested in your presentation,
we should also consider this and instantiate [Model]s the
right way. Doing this the right way might make the rest of
the package and on-die interconnect syntax cleaner.
Thanks,
Arpad
================================================================
From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]
On Behalf Of Walter Katz
Sent: Sunday, August 26, 2012 2:03 PM
To: IBIS-ATM
Subject: [ibis-macro] Lets go all the way!
All,
In the Friday Open Forum meeting Arpad raised a question that reflects the
problem that legacy IBIS combines both package and die models in .ibs files. I
believe the answer to this question is to split up "components" into a package
EMD file and a die IBISx file.
The enclosed presentation illustrates this using the example legacy IBIS file
in my last presentation.
Walter
Walter Katz
wkatz@xxxxxxxxxx<mailto:wkatz@xxxxxxxxxx>
Phone 303.449-2308
Mobile 303.335-6156
Other related posts:
