================================================================================ IBIS INTERCONNECT TASK GROUP https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibis.org_interconnect-5Fwip_&d=DwIGAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=DcQR-qLpQg5lIreuM6-NYECRIAFXt268PRNS5WO043M&m=2cLxXKHg9Z4U22BcvT5sLdzjmNKph_CNQ-cTrctDK7U&s=Arg55u1RJz26emnFLTRAurrIPG2zQjTuEI2e_NVLrB4&e= Mailing list: ibis-interconnect@freelists.org Archives at https://urldefense.proofpoint.com/v2/url?u=http-3A__www.freelists.org_archive_ibis-2Dinterconn_&d=DwIGAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=DcQR-qLpQg5lIreuM6-NYECRIAFXt268PRNS5WO043M&m=2cLxXKHg9Z4U22BcvT5sLdzjmNKph_CNQ-cTrctDK7U&s=Ibe9kZ_na9hzSH2P6WwtYC4fcDK6urdcDRsib9jp21Q&e= ================================================================================ Attendees from July 1, 2020 Meeting (* means attended at least using audio) ANSYS Curtis Clark* Intel Corp. Michael Mirmak* Ifiok Umoh Eric Edwards 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* Zuken USA Lance Wang* 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 June 24, 2020 meeting. Michael noted a typo where the word "need" should be "needed" on line 105. Arpad moved to approve the minutes with this correction. Randy seconded. The minutes were approved without objection. Review of ARs: - Randy to send out EMD draft15. - Bob asked if this was sent out. Randy replied he did not send this out yet, but he will do so now. Opens: - None. EMD Draft15 Review: Randy stated we had left off on the I/O pin_name rules for the power delivery network. We had started to discuss this but did not make any decision. Michael asked if there are similar pin_name rules elsewhere. Randy replied these are definitions. Bob commented the header is misleading, and this section should be covered by other rules. Michael commented these are nice crisp statements and asked where they are covered elsewhere. Bob noted that these are incorrect statements. Randy stated these could be useful as introductory information. Michael asked if these could be moved to the EMD Model section. Bob replied these should be covered elsewhere. What is not stated is that everything goes between one or more interfaces. Randy noted we have a list of cases in the EMD Model section and suggested to add the PDN modeling description below the combinations. He suggested to add the sentences below the combinations. Bob commented, if they are connection rules, they belong in the rules section. Michael suggested adding the first 4 yellow highlighted bullets to the EMD Model below the combinations. Bob stated moving this to the EMD Model section could work. Randy noted the fifth bullet is unrelated and may go somewhere else, as it discusses the reference. He moved the first 4 bullets as Michael suggested. Bob noted, in the Terminal_type section, we discuss the reference and A_gnd. Randy agreed with this and added the fifth bullet to the Terminal_type description. Arpad noted this is already stated a couple times in this section in terms of what A_gnd can be used for. Arpad asked why this applies to the I/O terminals. He suggested to delete this sentence. Randy agreed. Randy suggested the Terminal_type description has repeated text which can be deleted. Michael agreed. Randy noted the next yellow highlighted section relates to the EMD models and the supported terminals. This is already covered on page 21 with similar text, but he asked which is a better statement. Bob commented, when we talk about rails, we make reference to a signal_name rail that can be one terminal, but it may cover many pins. The rule should cover this case. Bob asked if it is correct to talk about pins in this context or if it is better to say terminals. Randy suggested to use the yellow text, which uses terminals. Curtis noted the yellow highlighted text also mentions one or more interfaces. Bob agreed this is true. Curtis suggested to change the phrase "can support" to "may contain". Randy noted a similar statement on page 26. He asked if this is needed to say terminals may be at the EMD or Designator pin interfaces. Randy suggested this can be deleted, as it is stated elsewhere. Arpad asked if these are the only two places we can have terminals. Bob thought this is correct, with the exception of A_gnd. Randy noted the terminal would be at the EMD or at the Designator and not at an undetermined location. Arpad suggested to change the sentence to say terminals can only be at these interfaces. Randy commented this is stated on page 21 already. Bob commented the subject of this section is the terminal names in the EMD Model. He suggested to add at the [EMD Pin List] and [Designator Pin List] interfaces. Randy made these changes. Randy stated the next yellow highlighted text is an example that we do not have a replacement for. Randy noted, for the text after the rule, we likely have a rule for this already. Bob agreed this should be covered. Randy noted it is in rule 2.a.iv. He asked if it is useful to have this example. Arpad noted this is an example of what not to do, and this is not our normal practice. Curtis noted this case is still legal, but you have to read the text to understand what the example is doing. Randy deleted this example. Randy noted the next section in yellow highlight is related to Aggressor_Only. He asked if there is a similar rule in 1.b. Bob replied there has to be a path without Aggressor_Only, and this case is covered in rule 1.b.iv. Randy suggested to delete the highlighted section. Arpad agreed. Randy asked if we want to use ATM time slot next week to work on the EMD draft. Michael stated he would be okay with this. He asked if we can use the same Webex meeting. Arpad replied this can work. Randy will send out EMD draft16 [AR]. Next Meeting: The next meeting will be July 7 at 12:00pm PT. Randy moved to adjourn. Arpad seconded. The meeting adjourned without objection. ================================================================================ Bin List: EMD Comments to be Resolved: (See BIRD202.1 tracking spreadsheet) IBIS-ISS Parser: - IBIS-ISS parser scope document