Attendees:
Mark Hahn, Cadence
Tom Dewey, Mentor
Bob Dilly, IBM
Jim Engel, IBM
Jim Swift, IBM
New action items:
Who When What
---------- ------ --------
1. Mark 10/12 Send GCF 2.0 draft to Tom
2. Bob 10/12 Prepare a proposal for DCDL operating conditions
commands
3. Mark 10/12 Prepare a proposal for DCDL commands to specify
physical supply names and the relationship between
them and logical/library rails
4. Tom 10/12 Try to get permission to use diagrams from the
Velocity documentation
Open action items:
Who When What
---------- ------ --------
1. Bob, Vikas 5/25 Review the GCF 2.0 draft on operating conditions
-> 7/6
-> 8/10
-> 9/28
-> 10/12
2. Mark 7/27 Prepare Microsoft Project schedule for the
-> 10/12 second half of '99.
3. Tom 10/12 Prepare skeleton for the DCDL spec
Closed action items:
Who When What
---------- ------ --------
1. Mark 9/28 Sent Tom the Frame template files
2. Mark 9/28 Get access to the eda.org machine set up
for Tom and Bob
3. Tom 9/28 Update table of contents
4. All 9/28 Discussion on reflector of OLA and
operating conditions
Next Meeting:
The next meeting will be a teleconference on 10/12
from 9-11 am (PDT).
Details:
1. Review action items
Tom has been making good progress on the DCDL skeleton,
pulling together information from the taxonomy, the DAC
subset syntax, the GCF spec, and some Mentor documentation.
The Mentor documentation has some waveform diagrams that
would be useful, while the GCF spec has fairly precise
semantics descriptions.
2. Discuss revised table of contents
We didn't spend much time on this, as people hadn't had a
chance to study it.
3. Discuss operating conditions
Mark had reviewed the sections in the OLA 1.0.2 spec related
to operating conditions, and Jim Engel from IBM attended most
of the phone conference, so we were able to make significant
progress.
OLA does provide support for both on-chip variation and a
numerical process point (instead of simply best, worst, and
nominal calc modes), which were concerns that we raised in
the past. It also has named operating points, which describe
combinations of process point, rail voltage, and temperature
supported by the library. These additions to P1481 make it
possible for DCDL to include a set of commands that can be used
consistently with both OLA and text-based library flows.
There are also ways in OLA to specify the legal ranges of
process, voltage, and temperature from the library standpoint;
we agreed that DCDL should provide similar commands that
specify tighter design-specific restrictions.
The main things that we thought that OLA doesn't include are
ways to specify the OLA rail that should be used for particular
parts of the design (on a hierachical scoping, master, or
instance basis), and a way to specify the relationship between
logical rails and the physical power distribution structure.
There are still questions about how OLA would be used to calculate
all three fields (min:typ:max) in SDF triplets (and what DCDL commands
are necessary to support this), and whether it's appropriate to
provide user-specified delay and slew scaling factors in DCDL.
Thanks,
Mark
-- Mark Hahn phone: (408) 428-5399 Senior Architect fax: (408) 428-5959 Cadence Design Systems email: mhahn@cadence.com