================================================================================ IBIS INTERCONNECT TASK GROUP http://www.ibis.org/interconnect_wip/ Mailing list: ibis-interconnect@freelists.org Archives at http://www.freelists.org/archive/ibis-interconn/ ================================================================================ Attendees from February 5, 2020 Meeting (* means attended at least using audio) ANSYS Curtis Clark Cadence Design Systems Bradley Brim Intel Corp. Michael Mirmak*, Ifiok Umoh* Keysight Technologies Radek Biernacki Mentor, A Siemens Business Arpad Muranyi* Micron Technology Justin Butterfield*, Randy Wolff* SiSoft Walter Katz*, Mike LaBonte Teraspeed Labs Bob Ross* Michael Mirmak convened the meeting. No patents were declared. Justin Butterfield took minutes. Review of Minutes: - Michael called for review of the minutes from the January 22, 2020 meeting. Randy Wolff moved to approve the minutes. Bob Ross seconded. The minutes were approved without objection. Review of ARs: - Michael to submit the EMD draft 31 as a BIRD to the IBIS Open Forum with the changes discussed in the last meeting. - Michael reported this is done and EMD is now posted as BIRD202. Opens: - Walter suggested an AR from Randy and himself to take a Registered DIMM board file and create an EMD [AR]. We can use this as a test case and publish the resulting EMD file. Randy stated he can send a JEDEC board file. Michael asked if we can also use this tool to check against the examples in the specification. Walter noted his parser is not yet ready. Randy noted the IBIS parser will be able to check this as well. EMD Editorial Review: Michael reviewed the editorial process that was used for IBIS 7.0. The process used a spreadsheet to track the changes by page numbers. The process allows the group to review and approve any changes to the document. He asked if we want to use this review format for EMD. Randy asked if this would be in place of using comments in the document. Michael stated it is a question on the approach, and we could run into issues with different people working on different parts of the BIRD. Bob noted our goal is to work toward a BIRD202.1, and there are specific issues to address. Walter suggested there should be one owner of the document changes every week. He suggested to make a separate spreadsheet with the comments, and we can track the status of the comments. Bob noted one issue is who would be the technical editor, and he suggested Michael take this role. Michael stated there should be only one person to make the changes. Walter commented we can update the spreadsheet based on the minutes. Michael asked if we should track finalization steps as well. Walter suggested to treat the task list spreadsheet as a brainstorming document, where we can track suggestions to follow up on. Michael started a spreadsheet to track the comments. Randy asked how we want to name the document, and suggested to reflect BIRD202.1 draft1. Michael added items to the list based on the agenda topics. Bob suggested to add discussion topics to this list, such as the term "connected" should be clarified. Walter thought the usage of "connected" is okay. Bob noted one detail is the usage of signal_name and how it relates to the connection. Randy stated he is working to create some figures. Michael added the EMD Model and supply pin connections issue from Bob, where we have grayed out text that needs to be resolved. The list of key terms and definitions was assigned to Michael. Michael added the checking of the syntax examples throughout the document and assigned this task to Walter. Walter noted generating an EMD example from an RDIMM board design file is an additional task. Bob noted we can add more examples to show the syntax throughout the BIRD. Walter noted he does not plan to add any additional examples beyond the RDIMM case. Bob noted one area we have left undetermined is on page 26 where we have the grayed out section, and he would like to have a more complete set of rules for the connections. Walter suggested to add a task for this stating to replace "pins may be terminals..." on page 26. Bob commented one issue is to move the rules to a different section and out of the EMD group section, as these rules are using terms which have not yet been defined. Michael asked which rule text this applies to. Bob replied this is on page 14. Bob also noted the example for EMD group is very simplistic. He suggested to reorder the sections and rules. Michael noted a typo in the phrase "the all" on page 2. Michael stated he has not received any feedback on the current BIRD. Randy had also not received any feedback. Michael asked if the BIRD has been introduced in the IBIS Open Forum. Bob replied it has not yet been introduced. Michael asked if we can have the task list spreadsheet posted to the website. Randy suggested to send it out over email. Michael noted Freelist does not include attachments. Michael to send out the task list tracking spreadsheet [AR]. Ifiok Umoh introduced himself as a member of Intel's Data Center Group. Michael asked everyone to think about what this group should tackle next after EMD. We will need to decide our next set of topics. Walter suggested to get through these EMD changes, before exploring these topics. Bob stated one topic is the IBIS-ISS parser, and he would like to get a better quote and scope of the project. Michael asked if we should discuss this in the IBIS Open Forum. Bob noted we need to decide if we want to move forward. The concern is if anyone will use the parser. Bob also stated that Eric Bogatin was not interested in improving the Touchstone specification. Walter asked about item #3 in the spreadsheet regarding the EMD model and supply pin connection issue. He asked why this is an issue. Michael asked if this was a duplicate of item #7. Bob noted that two signal_names are connected. He noted for rails the routing can be split with bus_labels at a different interface and these may not be connected. Walter noted we have to be clear between the terms "connected" and "shorted". Two pins may be connected, but not necessarily shorted. Michael combined these items in the task list. Next Meeting: The next meeting will be February 12. Randy moved to adjourn. Arpad seconded. The meeting adjourned without objection. ================================================================================ Bin List: EMD Comments to be Resolved: IBIS-ISS Parser: - IBIS-ISS parser scope document