Subject: Reminder for 8/20/02 conference call
From: Yatin Trivedi (trivedi@pacbell.net)
Date: Tue Aug 20 2002 - 06:19:07 PDT
Hi Folks,
Since Joao is out of his office today, I am sending
this reminder for the call. I have also attached the minutes
of the last meeting and dial-in information. See you all on the call.
Regards
Yatin
Joao Geada wrote:
>
> ***************************************************************
>
> Next Meeting: Tuesday 08/20 at 12:00 noon east coast time
> Meetings Schedule and Call Info:
> PARTICIPANT INFORMATION:
> -----------------------
>
> All Participants should use the following information to reach the
> conference call:
> * PARTICIPANT CODE: 707131
> * Toll Free Dial In Number: (877)807-5706
> * International Access/Caller Paid Dial In Number: (225)383-8961
>
> SV-CC (08/06/2002)
> ****************************************************************
>
> Minutes of last meeting 08/06
>
> Attendees:
> [xxx] Ghassan Khoory (Synopsys, Co-Chair)
> [xxx] Kevin Cameron (NSC)
> [xxx] Simon Davidmann (Co-Design)
> [xx-] Peter Flake (Co-Design)
> [xxx] Joao Geada (Synopsys)
> [x--] Tayung Liu (Novas)
> [xxx] Andrzej Litwiniuk (Synopsys)
> [x--] Mike McNamara (Verisity)
> [xxx] Stuart Swan (Cadence)
> [--x] Francoise Martinole (Cadence)
> [-xx] Bassam Tabbara (Novas)
> [--x] ž+’Ä Yatin Trivedi
> [--x] Michael Rohleder (Motorola)
> [--x] Darryl (Sun)
>
> [editor note: I didn't catch Darryl's last name. Sorry]
>
> - Yatin introduced himself. He is now the chair for this committee.
> As stated in a prior email to the group, he stated that he is
> available for discussions/phone calls. He lives on the West coast,
> so any reasonable west coast time (after 8am, prior to 10pm) is OK.
>
> We went over the agenda and procedural issues. From now the standard
> procedure will be to review and approve previous minutes at the
> start of each meeting and then go through the agreed upon agenda.
>
> For each task to be handled by this group, the process will be:
> 1) obtain a requirements document for the task
> 2) discuss requirements via the email reflects and/or directly between
> the parties as appropriate
> 4) form group to create technical spec proposal
> 5) proposals given to committee
>
> - went over results of action items from previous week:
> * Ghassan/Yatin: Vassilious has restated that it is this committee's
> responsibility to deal with all the foreign language interfaces:
>
> direct foreign language interface
> assertion API
> coverage API
> PLI/VPI enhancements
>
> Specifically, the deliverable from this committee is to be the
> portions of the SystemVerilog standard proposal related to the
> above APIs Committee will generated the technical specifications,
> Yatin will edit these into the standards text. Yatin will be the
> central repository for any documents we generate.
>
> * Yatin/Simon communicated that Peter will not be able to complete
> the action item from last meeting (direct interface requirements)
> due to other work on his plate. Simon will take over this action
> item and provide comments/additions/differences over the
> requirements that Andrzej proposed (instead of creating an
> independent set of requirements).
>
> - Francoise asked if any priority on the 4 APIs given by the main
> SystemVerilog committee.
> Ghassan&Yatin stated that no, that priorities are to be established
> by us.
>
> We all agreed to continue with our existing priorities
> 1- direct interface
> 2- assertion/coverage API
> 3- vpi
>
> - Francoise asked how we were going to deak with the VPI task.
> * Joao suggested that this would best be achieved by having a
> sub-group create a proposal.
> * Francoise accepted to be lead for that sub-group, as long as we all
> first agree on VPI enhancement requirements
>
> - Francoise asked if there are any global requirements for all the APIs.
> eg that they all have to interoperate, abilitity to call one API from
> within another APIs context etc.
> Similarly, do we have requirements for all the APIs?
>
> ** ACTION: Joao: to create proposal for "global requirements" that are to
> be met by all the APIs
> ** ACTION: Joao: to create proposal for assertion API requirements
> ** ACTION: Joao: to create proposal for coverage API requirements
> ** ACTION: Francoise: create proposal for VPI enhancement requirements
>
> All action items above to be submited by 8/15, with goal of reaching
> approval for all the above by/on the 9/3 meeting.
>
> ** ACTION: Yatin: to create process by which requirements/spec
> proposals will be handled by this group. Process to be given to
> committee no later than 8/15
>
> ** VOTED: we all approved the minutes of the last (7/23) meeting
>
> - there were some questions raised about the donations deadline for
> the System Verilog standard. The deadline is either September 15 or
> end of September.
>
> ** ACTION: Yatin: to clarify what the real deadline is and communicate
> to group as soon as possible.
>
> Next meeting to be held Aug 20th, same time, same conference number.
> (details at top of this email)
>
> Yatin encouraged us all to discuss proposals via email, and to reach
> agreement and resolutions in as far as possible prior to the meetings,
> leaving the meetings primarily for prioritizing and recording official
> votes. At the moment there is a proposal for the direct foreign
> language interface requirements, so he'd like us all to discuss that
> and reach some resolution prior to next meeting.
>
> ==============================================================================
> Joao Geada, PhD Sr. Staff R&D Engineer Verif Tech Group
> Synopsys, Inc TEL: (508) 263-8083
> 154 Crane Meadow Road, Suite 300, FAX: (508) 263-8069
> Marlboro, MA 01752, USA
> ==============================================================================
This archive was generated by hypermail 2b28 : Tue Aug 20 2002 - 09:06:44 PDT