[sv-bc] RE: Agenda: Oct 25 SV-BC Meeting

Thanks. Minutes are here:

http://www.eda.org/sv-bc/minutes/sv-bc_10_09_27.txt

Matt

>-----Original Message-----
>From: Bresticker, Shalom
>Sent: Sunday, October 24, 2010 3:28 AM
>To: Maidment, Matthew R; SV-BC
>Subject: RE: Agenda: Oct 25 SV-BC Meeting
>
>The meeting minutes should be from September 27, not the 13th.
>
>I put in proposals for the following Mantis items:
>
>http://www.eda-stds.org/mantis/view.php?id=1133
>http://www.eda-stds.org/mantis/view.php?id=1170
>http://www.eda-stds.org/mantis/view.php?id=3080
>http://www.eda-stds.org/mantis/view.php?id=3137
>http://www.eda-stds.org/mantis/view.php?id=3210
>http://www.eda-stds.org/mantis/view.php?id=3225
>http://www.eda-stds.org/mantis/view.php?id=3230
>
>Thanks,
>Shalom
>
>> -----Original Message-----
>> From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of
>> Maidment, Matthew R
>> Sent: Friday, October 22, 2010 10:30 PM
>> To: SV-BC
>> Subject: [sv-bc] Agenda: Oct 25 SV-BC Meeting
>>
>> SV-BC Meeting
>> Date: Monday, October 25, 2010
>> Time: 9:00am-11:00am PDT
>>
>> Toll Free Dial In Number in North America: 1-888-813-5316
>> Caller Paid Dial In Number: 1-650-584-6338
>> Meeting ID: 7839818
>>
>> Agenda
>>
>> + Review IEEE patent policy
>> http://standards.ieee.org/board/pat/pat-slideset.ppt
>>
>> + Previous Meeting Minutes
>>
>> http://www.eda.org/sv-bc/minutes/sv-bc_10_09_13.txt
>>
>> + Feedback on proposal to add DPI calls as system tasks
>>
>> Wilson Snyder floated this concept to the SV-BC reflector:
>>
>> http://www.eda.org/sv-bc/hm/10502.html
>>
>> and there were responses from several BC members.
>> The SV-CC chair has again asked for feedback:
>>
>> http://www.eda.org/sv-bc/hm/10598.html
>>
>> BC should officially consider and respond.
>>
>> + Mantis 696 (http://www.eda.org/svdb/view.php?id=696)
>>
>> Need to address this feedback from Neil:
>>
>> http://www.eda.org/sv-bc/hm/10605.html
>>
>> and conduct final vote.
>>
>> + Review Mantis 1627 (http://www.eda.org/svdb/view.php?id=1627)
>>
>> SV-AC approved Mantis 1627. SV-BC was asked to review prior to
>> sending to Champions. Please review and prepare for discussion.
>>
>> + Progress/Discussion for Top 10
>>
>> Looking for proposal sketches or discussion for any of these issues.
>>
>> 696 - Champion: Tom
>> 2310(1084, 1201) - Participants: Eric, Tom, Shalom, Steven,
>> Wilson Snyder
>> 3053 - Participants: Francoise, Mark, Alex, Kaiming
>> 3055 - Participants: Gord, Mark
>> 2991 - Champion: Tom, Participants: Steven
>> 1566 - For future discussion
>> 2114 - Similar to 3053. Have same group look at it.
>> 210 - Participants: Shalom, Matt
>> 3056 - Champion: Shalom, Participants: Steven, Francoise
>>
>> Action Items
>>
>> Complete
>> 08/16/10 Tom write up class static method examples and explanation
>> for
>> inclusion in clause 8 and reference in clause 13 and 3.8.
>> 09/13/10 Shalom review 2318 and classifying issues as testbench or
>> design
>> See: http://www.eda.org/sv-bc/hm/10566.html
>>
>> Outstanding
>> 05/10/10 Matt create Master Issue for WG-approved SV-BC Top-25
>> 07/19/10 Matt follow-up about voting rules for technical sub-
>> committee.
>> Is there a limit on the number of reps from 1 entity?
>> 07/19/10 Dave to post request to reflectors for clarification of 2108
>> 07/19/10 Jonathan post some items for discussion related to 2114 to
>> reflector.
>> 08/02/10 Brad give SV-BC feedback on Mantis 2992 to Mehdi
>> 08/02/10 Eric start reflector thread on Mantis 2310
>> 08/02/10 Gord meet F2F with Mark when in Bay Area
>> 08/16/10 Brad update Mantis items passed by email vote.
>> 08/16/10 Matt to rethink 210 in terms of configuration and alias.
>> 08/16/20 All send Shalom feedback about prioritizing the issues
>> raised
>> in port declaration issue summary:
>> http://www.eda.org/sv-bc/hm/10498.html
>> 09/13/10 Jonathan show simple examples of virtual interfaces, sub-
>> interfaces
>> and base classes in modules to demonstrate different methods
>> for
>> connecting design and testbenches.
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.