Attendees:
Mark Hahn, Cadence (Chair)
Dave Barton,
Bob Dilly, IBM
Jim Swift, IBM
New action items:
Who When What
---------- ------ --------
1. Mark 3/30 Check on DAC demo participation from
Mentor, Synopsys, Synplicity
Open action items:
Who When What
---------- ------ --------
1. Jim 1/19 Investigate whether IBM could provide the
-> 2/16 Einstimer educational material as a reference
-> 3/2
-> 3/30
2. Greg 2/16 Provide a list of PVT-dependent commands from
-> 3/2 BuildGates.
-> 3/30
3. Mark 3/2 Add operating conditions to the taxonomy
-> 3/30
4. Mark 3/2 Look into a working group meeting at DAC
-> 3/30
Closed action items:
Who When What
---------- ------ --------
1. Tom 3/10 Look into providing an internal Mentor
document on describing name spaces
Next Meeting:
The next meeting will be a teleconference on 3/30
from 9-11 am (PDT).
Details:
1. Review action items
Jim Swift hasn't heard back from IBM's legal department
yet on the Einstimer educational material.
Tom Dewey sent Mark a copy of a Mentor document describing
name mapping. The document covered rules for transforming
names (character substitutions, truncation, etc.), rather
than rules for interpreting names (character set, escaping
mechanism, delimiters, etc.), so it isn't applicable to DCDL.
We talked about DAC attendance; since it's in New Orleans
this year attendance may be lower than usual. Mark Hahn and
Dave Barton will attend, Bob Dilly wasn't sure, and Jim Swift
won't.
2. Discuss DAC demo
Bob Dilly investigated how feasible it looks to adapt the
IBM constraints translator to support the DAC subset of DCDL,
and it looks ok.
We discussed the overall flow of the DAC demo. The intent
is to illustrate the primary use models for DCDL, including
a. embedding DCDL commands within application-specific TCL
scripts
b. exchanging constraint data in DCDL files
c. translating DCDL to application-specific formats
d. translating application-specific formats to DCDL
From Cadence, BuildGates should cover a, b, and c. Pearl
should cover a-d.
From IBM, the Einstimer constraint translator should cover a
and b.
Mentor and Synopsys haven't indicated whether they plan to
participate. Mark suggested that Synplicity might be another
possibility.
We talked about the test case to use for the demo. There are
two main choices:
- the design being used for the OLA/VSI demo
- a public domain design of a MIPS 4000 processor, DLX
It is probably better to use the public domain design, to
avoid synchronization problems that are likely as the OLA/VSI
demo gets finalized close to DAC.