IEEE 1364 PLI Task Force (PTF) Mailing List Archives
By Subject
248 messages sorted by:
[ author ]
[ date ]
[ thread ]
[ attachment ]
Previous Folder, Subject view | Next Folder, Subject view | List of Folders
Other mail archives
Starting: Fri Nov 22 2002 - 11:43:34 PST
Ending: Tue Oct 04 2005 - 16:11:36 PDT
- (no subject)
- (POSTED) Minutes of the February 23, 2004 IEEE 1364 WG meeting
- 398 proposal
- [Fwd: errata/578: PROPOSAL - -ptf/286: version=2.63]
- [Fwd: PTF meeting minutes for 12/15/2003]
- Accellera's decision on Two Verilogs
- Agenda of IEEE 1364 Meeting of February 23, 2004
- Are save/restart/reset defined?
- BOUNCE etf@wa.boyd.com: Non-member submission from ["Fitzpatrick, Tom" <tom_fitzpatrick@mentorg.com>]
- Cadence is completely off the net!!!
- Call for nominations for 1364 VSG officer positions
- Call for participation: IEEE 1800 CC - errata committee
- Clarification needed for vpi_control(vpiFinish) and $finish
- Comments on events at NesCom meeting
- Comments on proposal to 342
- Corrected Minutes for June 14, 2000: IEEE-1364 Working Group
- Corrected proposal for uwire
- Diagram for PTF 623
- election of officers P1364 is now ended.
- enhancement/342: PROPOSAL - Deprecate the PLI 1.0 sections
- enhancement/576: add tables of object, method and property references in 26.6
- enhancement/579: 26.6: return subsections to table of contents
- errata/284: PROPOSAL - errata/284: vpiUseBinding not defined in Annex G
- errata/284: PROPOSAL - vpiUseBinding not defined in Annex G
- errata/286: 26.6: vpiBitSelect is not defined
- errata/286: PROPOSAL - 26.6: vpiBitSelect is not defined
- errata/320: ANALYZED - 26.6: Should memories be of type vpiMemory or vpiRegArray?
- errata/320: PROPOSAL - 26.6: Should memories be of type vpiMemory or vpiRegArray?
- errata/329: PROPOSAL - 27.29: vpi_put_data not used in example
- errata/329: Tested example
- errata/341: errata/341: How are two dimensional arrays of regs to be treated in VPI?
- errata/341: errata/341: problems with passed proposal
- errata/341: How are two dimensional arrays of regs to be treated in VPI?
- errata/341: PROPOSAL - How are two dimensional arrays of regs to be treated in VPI?
- errata/341: PROPOSAL - How are two dimensional arrays of regsto be treated in VPI?
- errata/365: PROPOSAL - 26.6.6 vpiLeftRange/vpiRightRange from net bit makes no sense
- errata/366: PROPOSAL - 26.6.8: Variables should clarify use of range iteration
- errata/398: errata/398: 2nd try for proposal of vpi_handle_multi_index
- errata/398: errata/398: 3rd try for proposal 398
- errata/398: errata/398: new proposal for vpi_handle_muti_index
- errata/398: errata/398: suggested wording for vpi_handle_by_index()
- errata/398: friendly amendment for proposal 398
- errata/398: PROPOSAL - 27.18: Description of return value is incorrect
- errata/512: PROPOSAL - 27.33 index field for s_cb_data struct won't work for MDAs
- errata/516: PROPOSAL - 27.13 and 27.31 doesn't talk about what happens with a save/restart/reset
- errata/517: No discussion on what to return if there is no value for an object version=2.63
- errata/518: PROPOSAL - 26.6.40 no discussion of how vpi_get_time() and vpiTimeQueue works
- errata/518: PROPOSAL - Modifying vpi_get_time description
- errata/523: Memory for callback routine's structures should be allocated by simulator
- errata/523: PROPOSAL - Memory for callback routine's structures should be allocated by simulator version=2.63
- errata/524: 27.7 vpi_get_cb_info() - who owns the data structure memory?
- errata/524: PROPOSAL - 27.7 vpi_get_cb_info() - who owns the data structure memory?
- errata/525: Memory for callback routine's structures should be allocated by simulator
- errata/525: PROPOSAL - Memory for callback routine's structures should be allocated by simulator
- errata/530: 26.6.17 expr class does not contain vpiTchkTerm - should model different
- errata/530: comments
- errata/530: PROPOSAL - 26.6.17 expr class does not contain vpiTchkTerm - should model different
- errata/530: PROPOSAL - 26.6.17: expr class does not contain vpiTchkTerm - should model different
- errata/533: Some PLI NOTES should be normative
- errata/534: 27.14: Last sentence on page 676 - should be for vpi_register_cb()
- errata/550: 27.10 static buffer should be implementation specific
- errata/562: Need to have a vpiTimeConst in the vpi_user.h file
- errata/562: PROPOSAL - Need to have a vpiTimeConst in the vpi_user.h file
- errata/567: 398: 2nd try for proposal of vpi_handle_multi_index
- errata/578: -ptf/286:
- errata/578: PROPOSAL - -ptf/286: version=2.63
- errata/591: two or more tag names on the same arrow in diagrams 26.6.15 and 26.6.16
- errata/592: The diagram for tchks
- errata/605: describe better which condifion trigger action callbacks
- errata/606: vpiReset is normative but $reset is information (same issue with $save)
- errata/622: Return value for left/right range of unsize parameter
- errata/623: 26.6.15 should not be modeled with multiple labels on one transition
- errata/623: PROPOSAL - 26.6.15 should not be modeled with multiple labels on one transition
- FINAL CALL for nominations for 1364 VSG officer positions
- Fwd: Generate proposal again (fwd)
- IEEE 1364 Meeting today.
- IEEE 1364 Meeting underway
- January 1364 meeting - if needed
- Minutes of BTF meeting on May 17, 2004, 11:05 AM PDT.
- Minutes of the April 19, 2004 IEEE 1364 Working Group Meeting
- Minutes of the August 16, 2004 IEEE-1364 Working Group
- Minutes of the February 23, 2004 IEEE 1364 WG meeting
- Minutes of the January 26th, 2004 1364 Meeting
- Minutes of the July 13, 2004 IEEE-1364 Working Group
- Minutes of the June 14, 2004 IEEE-1364 Working Group
- Minutes of the March 22nd, 2004 IEEE 1364 WG meeting
- Minutes of the May 18, 2004 IEEE-1364 Working Group
- Model operationg proceudres for review
- Never received Generates draft document
- New 512 wording
- Operating Procedures for P1364
- P1800 consideration at NESCOM
- P1800 meeting
- P1800 SystemVerilog WG F2F Meeting Agenda for August 9th
- Proposal to (almost) deprecate TF and ACC routines
- PTF 342 PDF of proposal
- PTF 517 - Preliminary Proposal
- PTF agenda for 1/12/2004
- PTF agenda for 1/26/2004
- PTF agenda for 10/04/2004
- PTF agenda for 10/18/2004
- PTF agenda for 2/23/2004
- PTF agenda for 2/9/2004
- PTF agenda for 3/22/2004
- PTF agenda for 3/8/2004
- PTF agenda for 4/5/2004
- PTF agenda for 5/17/2004
- PTF agenda for 5/3/2004
- PTF agenda for 6/14/2004
- PTF agenda for 6/28/2004
- PTF agenda for 7/12/2004
- PTF agenda for 7/26/2004
- PTF agenda for 8/23/2004
- PTF agenda for 9/20/2004
- PTF meeting minutes for 1/12/2004
- PTF meeting minutes for 1/26/2004
- PTF meeting minutes for 10/04/2004
- PTF meeting minutes for 2/23/2004
- PTF meeting minutes for 2/9/2004
- PTF meeting minutes for 3/22/2004
- PTF meeting minutes for 3/8/2004
- PTF meeting minutes for 4/5/2004
- PTF meeting minutes for 5/17/2004
- PTF meeting minutes for 5/3/2004
- PTF meeting minutes for 6/14/2004
- PTF meeting minutes for 6/28/2004
- PTF meeting minutes for 7/25/2004
- PTF meeting minutes for 8/23/2004
- PTF meeting minutes for 9/20/2004
- PTF meeting on 5/31/2004 is cancelled
- PTF meeting on Monday is cancelled
- PTF meeting today is cancelled
- PTF-341 diagram, updated
- PTF-342 proposal diagram
- questions on SV-CC 303/PTF 342
- questions on SV-CC 303/PTF 342 and SV-CC 313/PTF 296
- Reminder ** IEEE 1364 Meeting Monday Jan 26th at 8:30 am **
- Requesting datatypes feedback
- Retirement
- Rewording proposal for 398
- spam trap tweak
- spam trap tweak (this time for sure)
- Updated - Minutes of the August 16, 2004 IEEE-1364 Working Group
Last message date: Tue Oct 04 2005 - 16:11:36 PDT
Archived on: Tue Oct 04 2005 - 16:11:52 PDT
248 messages sorted by:
[ author ]
[ date ]
[ thread ]
[ attachment ]
Previous Folder, Subject view Next Folder, Subject view List of Folders
Other mail archives
This archive was generated by hypermail 2.1.4
: Tue Oct 04 2005 - 16:11:52 PDT
and
sponsored by Boyd Technology, Inc.