From sacadmin Tue Dec 9 18:26:21 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBA2QLWD022736 for ; Tue, 9 Dec 2008 18:26:21 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBA2QHJn006807; Tue, 9 Dec 2008 18:26:21 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBN00H0N2RVEY00@brm-avmta-1.central.sun.com>; Tue, 09 Dec 2008 19:26:19 -0700 (MST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBN00AD92RU1K60@brm-avmta-1.central.sun.com>; Tue, 09 Dec 2008 19:26:18 -0700 (MST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mBA2QIgM016548; Tue, 09 Dec 2008 18:26:18 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBN005012O0SA00@fe-sfbay-10.sun.com> (original mail from Hitendra.Zhangada@Sun.COM); Tue, 09 Dec 2008 18:26:18 -0800 (PST) Received: from [129.150.37.223] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBN002R92RRYD10@fe-sfbay-10.sun.com>; Tue, 09 Dec 2008 18:26:16 -0800 (PST) Date: Tue, 09 Dec 2008 18:26:16 -0800 From: Hitendra Zhangada Subject: fast-track : 2008/761 - Supernova Platform Binding Sender: Hitendra.Zhangada@sun.com To: Firmware ARC , Pingchun Lee Cc: us-staff@sun.com Message-id: <493F28C8.6020901@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_JDNHG/RkrxdDwI63rlKjhA)" X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) Status: RO Content-Length: 19335 This is a multi-part message in MIME format. --Boundary_(ID_JDNHG/RkrxdDwI63rlKjhA) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT I am sponsoring this fast-track case for Pingchun Lee. This case describes platforms bindings, interface changes in MD, PRI and OpenBoot device node for Supernova platforms. The details are in the attached one-pager. I have also attached sample output of PRI, MD and device tree. I will ask Ping to update PRI specification to include the changes proposed in this case. The updated PRI specification will be added to this case upon approval of this case. Timer for this case expires on December 16, 2008. This case is seeking following release bindings, Release Binding: firmware: minor/micro firmware release OS: minor/micro/patch OS release. -- Hitendra Zhangada ============================================= SPS Common SW Features Engineering Software Group, Sun Microsystems, Inc. Work Ph# (858) 625 3757, Ext. x53757 SUN Internal homepage http://esp.west/~hitu --Boundary_(ID_JDNHG/RkrxdDwI63rlKjhA) Content-type: text/plain; name=SNOne-pager.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=SNOne-pager.txt 1. Introduction 1.1. Project/Component Working Name: Supernova Platform Binding 1.2. Name of Document Author/Supplier: Pingchun Lee 1.3. Date of This Document: 12/09/2008 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: HEES PAC 1.4.2. The ARC(s) you expect to review your project: FWARC 1.4.3. The Director/VP who is "Sponsoring" this project: Ravi.Subbarao@sun.com - Director: Enterprise Systems Software 1.4.4. The name of your business unit: Systems - Enterprise Software 1.5. Email Aliases: 1.5.1. Responsible Manager: Umesh.Sharma@sun.com 1.5.2. Responsible Engineer: Pingchun.Lee@sun.com 1.5.3. Marketing Manager: N/A 1.5.4. Interest List: us-staff@sun.com 2. Project Summary 2.1. Project Description: This project registers the "banner-name" and root node "name" property values used on the Supernova platforms. OpenBoot extracts these values from the guest MDs and creates the properties for Solaris to use. It also describes the platform specific properties for io devices on the Supernova platforms. 2.2. Risks and Assumptions: None. 3. Business Summary 3.1. Problem Area: Although marketing (and not engineering) dictates these property values, they constitute a cross-consolidation software/firmware interface, and therefore must be registered with an ARC body. 3.2. Market/Requester: Enterprise Systems 3.3. Business Justification: N/A 3.4. Competitive Analysis: N/A 3.5. Opportunity Window/Exposure: Required for Supernova RR. 3.6. How will you know when you are done?: When the required SysFW changes are integrated into the 7.x gate. 4. Technical Description: 4.1. Details: 4.1.1. Supernova platform names Supernova platforms will have the following root node "name" and "banner-name" properties. "name" Type: Prop-encoded-string Contents: Root node name property for Supernova platforms Values: Value: "SUNW,SPARC-Enterprise-AT7480" for Silver-II Value" "SUNW,SPARC-Enterprise-AT7880" for Platinum-II "banner-name" Type: Prop-encoded-string Contents: Banner name for Supernova platforms Values: Value: "SPARC Enterprise AT7480" for Silver-II Value: "SPARC Enterprise AT7880" for Platinum-II 4.1.2. Root-port Device Node Supernova RootComplex supports Root-port(s) which is implemented via p2p bridge(s). The device tree representation of the root-port node is very similar to the PCI-Express bindings. Solaris needs the root-port device node from OpenBoot to attach a driver in Solaris (Solaris depends on OpenBoot device tree for IO). The root-port device node allows Solaris client to handle the PCIe fabric errors in hardware neutral manner. This is the direction future platform are taking. Without this node, a huge amount of redundant code will have to be delivered specifically for Supernova RootComplex and will not be usable for future RootComplex implementations. The root-port node described in below is expected to be created by future products. Supernova is first to implement it. 4.1.2.1. Root-port Support in Physical Resource Inventory (PRI) The Physical Resource Inventory is specified in FWARC 2006/700, and updated in FWARC 2007/138, then extended in FWARC 2008/467 (v1.4). The material in Section 1.11 (IO Device node) of 2008/467 is copied from the same context of Machine Description (MD) in FWARC/2007/070. This case proposes the following change: - Add a new io device node with generic device-type value = "pciex" or an optional value = "pcie-root-port" that indicates the node is a pci-express root-port. This node is directly underneath its sun4v host bridge node. - Typo correction, the "device-type" values "pci-switch-upstream" should be "pcie-switch-upstream", and "pci-switch-downstream" should be "pcie-switch-downstream". With these changes both a root nexus device (device-type="pciex") and a root port(device-type="pcie-root-port") node will exist in the device tree. 4.1.2.2. Root-port Support in Machine Description (MD) The Machine Description IO device node is specified in FWARC 2007/070. This case proposes changes for Supernova RootComplex. It contains both a root nexus device and a root port This case proposes the following changes: - A new optional value for "device-type" property, 'pcie-root-port' is added to values defined in 2007/070. 4.1.2.3. Root-port Support in OpenBoot device tree The required properties are followed from the FWARC case 2003/637 and 2005/565 (PCI Express Bus Binding) which is extended from PCI Binding to IEEE P1275 (under http://noho.eng/1275/home.html#OFDbussupps). This case makes the following changes: - The value of the compatible property for root-port node is "pciexclass,060400". - Add a new optional property "port-type" to the PCI Express Bus Bindings prop-encoded-array : string Read in "Device/Port Type" field (bit:7-4) from PCI express capabilities register (offset 2 in PCI express capability structure). This hardware initialized field indicates the type of PCI express logical device. Defined strings of port-type are: "PCIE-Endpoint" - PCI express endpoint device "Legacy-PCIE-Endpoint" - Legacy PCI express endpoint device "Root-Port" - Root Port of PCI express root complex "Upstream-Port" - Upstream port of PCI express switch "Downstream-Port" - Downstream port of PCI express switch "PCIE-PCI/PCIX-Bridge" - PCI express to PCI or PCIX bridge "PCI/PCIX-PCIE-Bridge" - PCI or PCIX to PCI express bridge 4.1.3. Onboard Neptune on Platinum-II The FCode is derived from its FCode whose binding is specified in FWARC 2006/652. For this case proposes the following property changes: "compatible" Type: Prop-encoded-array of prop-encoded-strings Contents: Standard property to define alternate "name" property values Value: "SUNW,rock-pciex108e,abcd" which is derived from Machine Description pci-network node. 4.1.4. PCI slot-names property for PCIe slots which support hotplug The property is imported from the IEEE 1275 PCI device binding. "slot-names" Type: Prop-encoded-string Contents: Slot label names for hotplug slots on Supernova platforms Value (format for Bronze): "PCIe", where slot# is from 0 to 5. Value (format for Silver): "iob_PCIe, Where boat# is 0 or 1 and slot# is from 0 to 7. Value (format for Platinum): "iob_PCIe, Where boat# is from 0 to 3 and slot# is from 0 to 7. Value (format for Silver-II): "PCIe2-EM", Where slot# is from 00 to 19. Value (format for Platinum-II): "PCIe-EM.", Where board# is from 0 to 7 and slot# is from 0 to 3. 4.2. Bug/RFE Number(s): N/A 4.3. In Scope: N/A 4.4. Out of Scope: N/A 4.5. Interfaces: Imported Interfaces : Interface Name Classification Description ==================== ============== ================================ "name" Standard FWARC/1998/392 (Standard IEEE 1275 property) "banner-name" Stable FWARC/1998/392 (Legacy property) "compatible" Evolving Standard OpenBoot property PCI-E bindings Evolving FWARC/2003/637, 2005/565 Machine Description Committed FWARC/2007/070 Neptune FCode Driver Uncommitted FWARC/2006/652 Platform Resource Uncommitted FWARC/2008/467 Inventory (PRI) Exported Interfaces : Interface Name Classification Description ==================== ============== ================================ "SUNW,SPARC-Enterprise-AT7480" Uncommitted "name" property value "SPARC Enterprise AT7480" Uncommitted "banner-name" property value "SUNW,SPARC-Enterprise-AT7880" Uncommitted "name" property value "SPARC Enterprise AT7880" Uncommitted "banner-name" property value "pcie-root-port" Uncommitted "device-type" property value in PRI and in MD "port-type" property Uncommitted Property in PCI Express device bindings "SUNW,rock-pciex108e,abcd" Uncommitted "compatible" property value in Onboard network device nodes "slot-names" property Uncommitted Standard "slot-names" property values values defined in sec 4.1.4 4.6. Doc Impact: The information covered in this case shall be included in Supernova technical documents. 4.7. Admin/Config Impact: N/A 4.8. HA Impact: N/A 4.9. I18N/L10N Impact: N/A 4.10. Packaging & Delivery: N/A 4.11. Security Impact: N/A 4.12. Dependencies: None 5. Reference Documents: Supernova Platinum-II System Specification Supernova Silver-II (or R10) System Specification 6. Resources and Schedule: 6.1. Projected Availability: TBD 6.2. Cost of Effort: N/A 6.3. Cost of Capital Resources: N/A 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: SysFW 6.4.3. Type of CPT Review and Approval expected: FastTrack 6.4.4. Project Boundary Conditions: 6.4.5. Is this a necessary project for OEM agreements: No 6.4.6. Notes: 6.4.7. Target RTI Date/Release: TBD 6.4.8. Target Code Design Review Date: 6.4.9. Update approval addition: 6.5. ARC review type: FastTrack 7. Prototype Availability: 7.1. Prototype Availability: N/A 7.2. Prototype Cost: N/A --Boundary_(ID_JDNHG/RkrxdDwI63rlKjhA) Content-type: text/plain; name=root-port.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=root-port.txt \ ***** PRI device nodes related with root-port example***** \ Sun4v host-bridge node in PRI iodevice (0x11314858) { address-ranges={ 00 00 c4 20 00 00 00 00 - 00 00 00 00 10 00 00 00 00 00 84 00 00 00 00 00 - 00 00 00 00 7f ff 00 00 00 00 84 00 00 00 00 00 - 00 00 00 03 ff ff 00 00 }; disabled=0x00000000; rcid=0x00000001; cfg-handle=0x00000600; device-type="pciex"; pseudonym="/CP0/CPUIO0/IOBR0"; name="pci"; fwd->iodevice (0x11314a60); back->phys_io (0x1130ce80); } \ Root-port node in PRI iodevice (0x11314a60) { function-number=0x00000000; device-number=0x00000000; device-type="pcie-root-port"; fwd->iodevice (0x1130ca68); back->iodevice (0x0x11314858); } \ PLX switch behind Root-port node in PRI iodevice (0x1130ca68) { function-number=0x00000000; device-number=0x00000000; device-type="pcie-switch-upstream"; fwd->iodevice (0x1130f000); fwd->iodevice (0x1130e498); fwd->iodevice (0x1130d6f8); fwd->iodevice (0x1130d120); back->iodevice (0x1130c828); } iodevice (0x1130f000) { function-number=0x00000000; device-number=0x0000000d; device-type="pcie-switch-downstream"; fwd->iodevice (0x11310948); back->iodevice (0x1130ca68); } ========================================================== \ ***** MD device nodes related with root-port example***** \ Similar to PRI. \ Skip host-bridge and just shows Root-port node and the node behind it. node iodevice node_6e70 { function-number = 0x0; device-number = 0x0; device-type = "pcie-root-port"; fwd -> node_6ee0; back -> node_88b0; } node iodevice node_6ee0 { function-number = 0x0; device-number = 0x0; device-type = "pcie-switch-upstream"; fwd -> node_6f70; fwd -> node_7310; fwd -> node_74e0; back -> node_6e70; } ========================================================== \ ***** OpenBoot device nodes related with root-port example***** \ Sun4v to pcie host bridge {8} ok cd /pci@600 {8} ok .properties available 81000000 00000000 04000000 00000000 0c000000 82000000 00000000 00120000 00000000 000e0000 82000000 00000000 25000000 00000000 5aff0000 c3000000 00000001 00000000 00000003 ffff0000 level2-hotplug-slot-count 00000006 level1-hotplug-slot-count 00000008 #interrupt-cells 00000001 interrupt-map-mask 00 ff f0 00 00 00 00 00 00 00 00 00 00 00 00 07 interrupt-map 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 ... interrupts 0000003e 0000003f dma-sync-options ffffffff reg c0000600 00000000 00000000 00000000 ranges 01000000 00000000 00000000 8000c020 00000000 00000000 10000000 02000000 00000000 00000000 80008000 00000000 00000000 7fff0000 03000000 00000000 00000000 80008000 00000000 00000003 ffff0000 msi-eq-to-devino 00 00 00 00 00 00 00 3a 00 00 00 04 #msi-eqs 0000003a msix-data-width 00000020 msi-eq-size 00000080 msi-ranges 00 00 00 00 00 00 08 00 msi-data-mask 000007ff #msi 00000800 msi-address-ranges 00 00 00 00 7f ff 00 00 00 01 00 00 00 00 00 03 ... bus-range 00 00 00 00 00 00 00 ff bus-parity-generated #address-cells 00000003 #size-cells 00000002 name pci compatible SUNW,sun4v-pci device_type pciex virtual-dma 80 00 00 00 80 00 00 00 {8} ok ----------------------------------------------------------------------------- {8} ok cd pci@0 \ Root port node in OpenBoot device tree. {8} ok .properties ranges 81000000 00000000 00000000 81000000 00000000 00000000 00000000 00001000 82000000 00000000 00000000 82000000 00000000 00000000 00000000 80000000 bus-range 00 00 00 01 00 00 00 ff port-type Root-Port cache-line-size 00000010 class-code 00060400 revision-id 00000011 device-id 00008100 vendor-id 0000108e reg 00000000 00000000 00000000 00000000 00000000 compatible pciexclass,060400 #address-cells 00000003 #size-cells 00000002 device_type pciex name pci {8} ok --------------------------------------------------------------------------- {8} ok cd pci@0 \ PCI express switch upstream node behind root port node {8} ok .properties assigned-addresses 82010010 00000000 00100000 00000000 00020000 ranges 81000000 00000000 00000000 81000000 00000000 00000000 00000000 04000000 82000000 00000000 00200000 82000000 00000000 00200000 00000000 24e00000 bus-range 00 00 00 02 00 00 00 7b compatible pciex10b5,8548.aa pciex10b5,8548 pciexclass,060400 pciexclass,0604 reg 00010000 00000000 00000000 00000000 00000000 #address-cells 00000003 #size-cells 00000002 device_type pciex name pci port-type Upstream-Port interrupts 00000001 cache-line-size 00000010 class-code 00060400 revision-id 000000aa device-id 00008548 vendor-id 000010b5 {8} ok ---------------------------------------------------------------------------- {8} ok cd pci@9 \ PCI express switch downstream node {8} ok .properties available 82000000 00000000 10320000 00000000 000e0000 ranges 81000000 00000000 02000000 81000000 00000000 02000000 00000000 02000000 82000000 00000000 10300000 82000000 00000000 10300000 00000000 10100000 bus-range 00 00 00 3f 00 00 00 7a compatible pciex10b5,8548.aa pciex10b5,8548 pciexclass,060400 pciexclass,0604 reg 00024800 00000000 00000000 00000000 00000000 #address-cells 00000003 #size-cells 00000002 device_type pciex name pci port-type Downstream-Port interrupts 00000001 cache-line-size 00000010 class-code 00060400 revision-id 000000aa device-id 00008548 vendor-id 000010b5 {8} ok pwd /pci@600/pci@0/pci@0/pci@9 {8} ok --Boundary_(ID_JDNHG/RkrxdDwI63rlKjhA)-- From sacadmin Wed Dec 10 07:08:52 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBAF8qLX024765 for ; Wed, 10 Dec 2008 07:08:52 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBAF8ocw011011; Wed, 10 Dec 2008 08:08:51 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBO00B1522QYK00@nwk-avmta-2.sfbay.sun.com>; Wed, 10 Dec 2008 07:08:50 -0800 (PST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBO001H622NM6D0@nwk-avmta-2.sfbay.sun.com>; Wed, 10 Dec 2008 07:08:48 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBAF8lJA023006; Wed, 10 Dec 2008 15:08:47 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBO007011OP0800@mail-amer.sun.com> (original mail from Stephen.Ehring@Sun.COM); Wed, 10 Dec 2008 08:08:12 -0700 (MST) Received: from dhcp-ubur03-184-216.East.Sun.COM ([129.148.184.216]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBO00A1121IL6D0@mail-amer.sun.com>; Wed, 10 Dec 2008 08:08:06 -0700 (MST) Date: Wed, 10 Dec 2008 10:08:06 -0500 From: Stephen Ehring Subject: Re: fast-track : 2008/761 - Supernova Platform Binding In-reply-to: <493F28C8.6020901@sun.com> Sender: Stephen.Ehring@sun.com To: Hitendra Zhangada Cc: Firmware ARC , Pingchun Lee , us-staff@sun.com Message-id: <493FDB56.3070706@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <493F28C8.6020901@sun.com> User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) Status: RO Content-Length: 1476 4.1.2.1 Is the rcid MD node property that you are adding to the pciex node defined anywhere? I know it's currently in the HV MDs (which have never been ARC'ed). Also, can you update the iodevice node spec with these new properties and nodes you are defining with this case (i.e. it will need to have all of the pcie-root-port definitions)? http://sac.eng/FWARC/Specifications/iodevice.txt Also, Is it really necessary to change "pci-switch-up/downstream" to "pcie-switch-up/downstream"? Are we going to change it in the generic driver, which means we'll need to update all platforms' MDs? This needs to be added to the iodevice spec, too, with whatever we decide. 4.1.2.3 You are updating the PCI Express Bus Bindings. Do you have an updated version of the binding? Once we have an updated binding, can we add it to the approved specifications directory? 4.1.3 The compatible property "SUNW,rock-pciex108e,abcd" for the onboard Neptune PCI device seems to diverge from the standard PCIE compatible property convention used on all other PCIE devices. In the binding you mention (2006/652) the "model" property is used to differentiate various pieces of hardware. Is there a reason we're not continuing that with Supernova? Is it because a different Neptune driver is being used or something? 4.1.4 Isn't this just re-implementing (in a different format) the information that is defined in section 1.3 of the iodevice.txt file mentioned above? Steve From sacadmin Wed Dec 10 08:35:17 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBAGZHmA013837 for ; Wed, 10 Dec 2008 08:35:17 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBAGZBTj004666; Wed, 10 Dec 2008 08:35:16 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBO0070762R8T00@brm-avmta-1.central.sun.com>; Wed, 10 Dec 2008 09:35:15 -0700 (MST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBO00FJF62Q7PD0@brm-avmta-1.central.sun.com>; Wed, 10 Dec 2008 09:35:14 -0700 (MST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBAGZDEU000056; Wed, 10 Dec 2008 16:35:14 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBO0080155S2500@mail-amer.sun.com> (original mail from Eric.Sharakan@Sun.COM); Wed, 10 Dec 2008 09:35:11 -0700 (MST) Received: from [192.168.100.100] (c-24-62-231-112.hsd1.ma.comcast.net [24.62.231.112]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBO00BL661IOA10@mail-amer.sun.com>; Wed, 10 Dec 2008 09:34:32 -0700 (MST) Date: Wed, 10 Dec 2008 11:34:30 -0500 From: Eric Sharakan Subject: Re: fast-track : 2008/761 - Supernova Platform Binding In-reply-to: <493FDB56.3070706@sun.com> Sender: Eric.Sharakan@Sun.COM To: Stephen Ehring Cc: Hitendra Zhangada , Firmware ARC , Pingchun Lee , us-staff@Sun.COM Message-id: <63512B91-EAA3-4040-9899-E199312E621B@Sun.COM> MIME-version: 1.0 X-Mailer: Apple Mail (2.929.2) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <493F28C8.6020901@sun.com> <493FDB56.3070706@sun.com> Status: RO Content-Length: 1874 On Dec 10, 2008, at 10:08 AM, Stephen Ehring wrote: > 4.1.2.1 > > Is the rcid MD node property that you are adding to the pciex node > defined anywhere? I know it's currently in the HV MDs (which have > never been ARC'ed). Also, can you update the iodevice node spec with > these new properties and nodes you are defining with this case (i.e. > it will need to have all of the pcie-root-port definitions)? The rcid node doesn't belong in the iodevice node of the PRI, unless we want to expose that to the guest MD, which I don't believe is the case. We're still trying to figure out where that property belongs; see CR 6769852 for more info. -Eric > > > http://sac.eng/FWARC/Specifications/iodevice.txt > > Also, Is it really necessary to change "pci-switch-up/downstream" to > "pcie-switch-up/downstream"? Are we going to change it in the > generic driver, which means we'll need to update all platforms' MDs? > This needs to be added to the iodevice spec, too, with whatever we > decide. > > 4.1.2.3 > > You are updating the PCI Express Bus Bindings. Do you have an > updated version of the binding? Once we have an updated binding, can > we add it to the approved specifications directory? > > 4.1.3 > > The compatible property "SUNW,rock-pciex108e,abcd" for the onboard > Neptune PCI device seems to diverge from the standard PCIE > compatible property convention used on all other PCIE devices. In > the binding you mention (2006/652) the "model" property is used to > differentiate various pieces of hardware. Is there a reason we're > not continuing that with Supernova? Is it because a different > Neptune driver is being used or something? > > 4.1.4 > > Isn't this just re-implementing (in a different format) the > information that is defined in section 1.3 of the iodevice.txt file > mentioned above? > > Steve > > From sacadmin Wed Dec 10 10:21:41 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBAILedx018755 for ; Wed, 10 Dec 2008 10:21:41 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mBAILTdH028958; Wed, 10 Dec 2008 18:21:39 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBO00M2VB029B00@nwk-avmta-2.sfbay.sun.com>; Wed, 10 Dec 2008 10:21:38 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBO00M06AZX9W00@nwk-avmta-2.sfbay.sun.com>; Wed, 10 Dec 2008 10:21:33 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mBAILXQN011057; Wed, 10 Dec 2008 10:21:33 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBO00B01AJN8J00@fe-sfbay-09.sun.com> (original mail from Hitendra.Zhangada@Sun.COM); Wed, 10 Dec 2008 10:21:33 -0800 (PST) Received: from [129.153.85.35] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBO004SLAZQUED0@fe-sfbay-09.sun.com>; Wed, 10 Dec 2008 10:21:27 -0800 (PST) Date: Wed, 10 Dec 2008 10:21:26 -0800 From: Hitendra Zhangada Subject: Re: fast-track : 2008/761 - Supernova Platform Binding In-reply-to: <493FDB56.3070706@sun.com> Sender: Hitendra.Zhangada@sun.com To: Firmware ARC Cc: Pingchun Lee , us-staff@sun.com Message-id: <494008A6.4040102@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <493F28C8.6020901@sun.com> <493FDB56.3070706@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 2715 On 12/10/08 07:08, Stephen Ehring wrote: > 4.1.2.1 > > Is the rcid MD node property that you are adding to the pciex node > defined anywhere? I know it's currently in the HV MDs (which have > never been ARC'ed). Also, can you update the iodevice node spec with > these new properties and nodes you are defining with this case (i.e. > it will need to have all of the pcie-root-port definitions)? > > http://sac.eng/FWARC/Specifications/iodevice.txt "rcid" property is NOT part of the specification. I do see that in the example MD/PRI output but it is not in the one-pager and hence not part of this case. Yes, iodevice.txt can and will be updated. I will work with Ping to make that happen along with updated PRI specification and PCI-express bindings before this case is approved. > > Also, Is it really necessary to change "pci-switch-up/downstream" to > "pcie-switch-up/downstream"? Are we going to change it in the generic > driver, which means we'll need to update all platforms' MDs? This > needs to be added to the iodevice spec, too, with whatever we decide. > I was told that this was a typo in the specification. I did grep under vBSC "md" directory and see that it is implemented as "pcie", For example, turgo/io.cfg:node iodevice pcie-switch-downstream3 { turgo/io.cfg: device-type = "pcie-switch-downstream"; > 4.1.2.3 > > You are updating the PCI Express Bus Bindings. Do you have an updated > version of the binding? Once we have an updated binding, can we add it > to the approved specifications directory? Sure, will do. > > 4.1.3 > > The compatible property "SUNW,rock-pciex108e,abcd" for the onboard > Neptune PCI device seems to diverge from the standard PCIE compatible > property convention used on all other PCIE devices. In the binding you > mention (2006/652) the "model" property is used to differentiate > various pieces of hardware. Is there a reason we're not continuing > that with Supernova? Is it because a different Neptune driver is being > used or something? Ping will have to answer this question. > > 4.1.4 > > Isn't this just re-implementing (in a different format) the > information that is defined in section 1.3 of the iodevice.txt file > mentioned above? Well the "slot-names" property and value comes from MD. This section spells them out as it will be seen in the device tree. May be this section can be deleted as the strings are unstable and platform specific anyway. Thanks for the review and comments. > > Steve > > -- Hitendra Zhangada ==================================== SPS Common SW Features Engineering Systems Group, Sun Microsystems, Inc. Sun Ph# (858) 625 3757, Sun Ext. x53757 Internal homepage http://esp.west/~hitu From sacadmin Wed Dec 10 10:44:55 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBAIisGo019482 for ; Wed, 10 Dec 2008 10:44:55 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mBAIiosh013022; Wed, 10 Dec 2008 18:44:51 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBO0000JC2PFT00@nwk-avmta-2.sfbay.sun.com>; Wed, 10 Dec 2008 10:44:49 -0800 (PST) Received: from uask4it.sfbay.sun.com ([10.7.80.228]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBO00MJMC2O9W10@nwk-avmta-2.sfbay.sun.com>; Wed, 10 Dec 2008 10:44:48 -0800 (PST) Received: from [129.145.155.62] (sr1-usca-35.SFBay.Sun.COM [129.145.155.62]) by uask4it.sfbay.sun.com (8.13.7+Sun/8.13.7) with ESMTP id mBAIilip010790; Wed, 10 Dec 2008 10:44:48 -0800 (PST) Date: Wed, 10 Dec 2008 10:44:47 -0800 From: Pingchun Lee Subject: Re: fast-track : 2008/761 - Supernova Platform Binding In-reply-to: <493FDB56.3070706@sun.com> To: Stephen Ehring Cc: Hitendra Zhangada , Firmware ARC , us-staff@sun.com Message-id: <49400E1F.7010308@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <493F28C8.6020901@sun.com> <493FDB56.3070706@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 2412 On 12/10/08 07:08 AM, Stephen Ehring wrote: > 4.1.2.1 > > Is the rcid MD node property that you are adding to the pciex node > defined anywhere? I know it's currently in the HV MDs (which have > never been ARC'ed). Also, can you update the iodevice node spec with > these new properties and nodes you are defining with this case (i.e. > it will need to have all of the pcie-root-port definitions)? > > http://sac.eng/FWARC/Specifications/iodevice.txt > I didn't know it's not ARC'ed, but this case focused more on OpenBoot related area. Do we need to include it in this case? > Also, Is it really necessary to change "pci-switch-up/downs-tream" to > "pcie-switch-up/downstream"? Are we going to change it in the generic > driver, which means we'll need to update all platforms' MDs? This > needs to be added to the iodevice spec, too, with whatever we decide. > Or can we just add "pcie-switch-up/downstream" equivalent to "pci-switch-up/downstream" to make it simple? > 4.1.2.3 > > You are updating the PCI Express Bus Bindings. Do you have an updated > version of the binding? Once we have an updated binding, can we add it > to the approved specifications directory? > Not yet. I can create one if it's better. > 4.1.3 > > The compatible property "SUNW,rock-pciex108e,abcd" for the onboard > Neptune PCI device seems to diverge from the standard PCIE compatible > property convention used on all other PCIE devices. In the binding you > mention (2006/652) the "model" property is used to differentiate > various pieces of hardware. Is there a reason we're not continuing > that with Supernova? Is it because a different Neptune driver is being > used or something? The "model" property is more for Plugin cards (or EMs). We just adopted the way used by NIU. Platinum-II contains 8 cpuio boards, each board contains a Neptune chip with two ports of 10Gb fiber and two ports of 1Gb RJ45 configuration. It needs a compatible property to support this configuration for Solaris nxge driver. > > 4.1.4 > > Isn't this just re-implementing (in a different format) the > information that is defined in section 1.3 of the iodevice.txt file > mentioned above? > No. We chose to implement slot-names properties in OpenBoot instead of slot-name properties in PRI or MD because it was more convenient. Either way, this case defines the label format as a reference document. Regards, Ping > Steve > > From sacadmin Wed Dec 10 13:05:13 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBAL5DNc008880 for ; Wed, 10 Dec 2008 13:05:13 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBAL54Qp051860; Wed, 10 Dec 2008 14:05:13 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBO0081TIKO3500@nwk-avmta-2.sfbay.sun.com>; Wed, 10 Dec 2008 13:05:12 -0800 (PST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBO00MTVIKN9T80@nwk-avmta-2.sfbay.sun.com>; Wed, 10 Dec 2008 13:05:11 -0800 (PST) Received: from dtmail.sfbay.sun.com (pkg.SFBay.Sun.COM [129.146.90.56]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mBAL5Ace007423; Wed, 10 Dec 2008 13:05:10 -0800 (PST) Received: from [127.0.0.1] (noho.SFBay.Sun.COM [10.6.92.101]) by dtmail.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id mBAL59kS002809; Wed, 10 Dec 2008 13:05:10 -0800 (PST) Date: Wed, 10 Dec 2008 13:05:09 -0800 From: David Kahn Subject: Re: fast-track : 2008/761 - Supernova Platform Binding To: Pingchun Lee Cc: Stephen Ehring , Hitendra Zhangada , Firmware ARC , us-staff@Sun.COM Message-id: <49402F05.2070100@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) Status: RO Content-Length: 296 I don't understand why we need those port type properties at all for switches/root ports. That info is available (for standard devices) in config space registers. And the way these things were designed, common software can just treat them as a pci-pci bridge with it's type 1 header. -David From sacadmin Wed Dec 10 13:14:22 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBALEMi4009047 for ; Wed, 10 Dec 2008 13:14:22 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBALEH4Q003237; Wed, 10 Dec 2008 13:14:20 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBO00A07IZWQP00@brm-avmta-1.central.sun.com>; Wed, 10 Dec 2008 14:14:20 -0700 (MST) Received: from uask4it.sfbay.sun.com ([10.7.80.228]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBO0037VIZVQ470@brm-avmta-1.central.sun.com>; Wed, 10 Dec 2008 14:14:19 -0700 (MST) Received: from [129.145.155.62] (sr1-usca-35.SFBay.Sun.COM [129.145.155.62]) by uask4it.sfbay.sun.com (8.13.7+Sun/8.13.7) with ESMTP id mBALEIWr025263; Wed, 10 Dec 2008 13:14:19 -0800 (PST) Date: Wed, 10 Dec 2008 13:14:18 -0800 From: Pingchun Lee Subject: Re: fast-track : 2008/761 - Supernova Platform Binding In-reply-to: <49402F05.2070100@sun.com> To: David Kahn Cc: Stephen Ehring , Hitendra Zhangada , Firmware ARC , us-staff@sun.com Message-id: <4940312A.2070700@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49402F05.2070100@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 576 That is useful for debugging purpose. It's easier to check if hardware is configured correctly by checking the property instead of 'selecting device to read register and decode it' when something doesn't work. Ping On 12/10/08 01:05 PM, David Kahn wrote: > > I don't understand why we need those port > type properties at all for switches/root ports. > > That info is available (for standard > devices) in config space registers. > > And the way these things were designed, > common software can just treat them as a > pci-pci bridge with it's type 1 header. > > -David > From sacadmin Wed Dec 10 13:18:05 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBALI5Cr009111 for ; Wed, 10 Dec 2008 13:18:05 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBALI4fL019650; Wed, 10 Dec 2008 13:18:04 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBO00E0FJ64JM00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 10 Dec 2008 13:18:04 -0800 (PST) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBO00APMJ627T20@nwk-avmta-1.sfbay.Sun.COM>; Wed, 10 Dec 2008 13:18:02 -0800 (PST) Received: from dtmail.sfbay.sun.com (pkg.SFBay.Sun.COM [129.146.90.56]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mBALI1jA054593; Wed, 10 Dec 2008 13:18:01 -0800 (PST) Received: from [127.0.0.1] (noho.SFBay.Sun.COM [10.6.92.101]) by dtmail.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id mBALI094003726; Wed, 10 Dec 2008 13:18:00 -0800 (PST) Date: Wed, 10 Dec 2008 13:18:00 -0800 From: David Kahn Subject: Re: fast-track : 2008/761 - Supernova Platform Binding In-reply-to: <4940312A.2070700@Sun.COM> To: Pingchun Lee Cc: Stephen Ehring , Hitendra Zhangada , Firmware ARC , us-staff@sun.com Message-id: <49403208.5060506@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49402F05.2070100@sun.com> <4940312A.2070700@Sun.COM> User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) Status: RO Content-Length: 475 Pingchun Lee wrote: > That is useful for debugging purpose. It's easier to check > if hardware is configured correctly by checking the property > instead of 'selecting device to read register and decode it' when > something doesn't work. Can we get rid of them? Properties create an interface, and they really aren't needed for debug only. I'm sure we can write a macro to get the port type displayed alphanumerically in either OBP or with the OS debug tools. -David From sacadmin Wed Dec 10 14:28:57 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBAMSuJq010771 for ; Wed, 10 Dec 2008 14:28:57 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mBAMSobk004728; Wed, 10 Dec 2008 22:28:55 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBO00D0BMG54600@nwk-avmta-2.sfbay.sun.com>; Wed, 10 Dec 2008 14:28:53 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBO00MJ9MG49ND0@nwk-avmta-2.sfbay.sun.com>; Wed, 10 Dec 2008 14:28:52 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mBAMSqlo013546; Wed, 10 Dec 2008 14:28:52 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBO00D01ME4EM00@fe-sfbay-10.sun.com> (original mail from Hitendra.Zhangada@Sun.COM); Wed, 10 Dec 2008 14:28:52 -0800 (PST) Received: from [129.153.85.35] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBO00HXBMFV6U10@fe-sfbay-10.sun.com>; Wed, 10 Dec 2008 14:28:44 -0800 (PST) Date: Wed, 10 Dec 2008 14:28:42 -0800 From: Hitendra Zhangada Subject: Re: fast-track : 2008/761 - Supernova Platform Binding In-reply-to: <49403208.5060506@sun.com> Sender: Hitendra.Zhangada@sun.com To: Firmware ARC Cc: Pingchun Lee , us-staff@sun.com Message-id: <4940429A.3040306@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49402F05.2070100@sun.com> <4940312A.2070700@Sun.COM> <49403208.5060506@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 980 On 12/10/08 13:18, David Kahn wrote: > > > Pingchun Lee wrote: >> That is useful for debugging purpose. It's easier to check >> if hardware is configured correctly by checking the property >> instead of 'selecting device to read register and decode it' when >> something doesn't work. > > Can we get rid of them? Properties create an interface, > and they really aren't needed for debug only. FYI. I am working with Ping to remove this property and also take care of comment related to slot-names property. New updated specification will be available in next few hours and timer will reset to another week. Thanks. > > I'm sure we can write a macro to get the port type > displayed alphanumerically in either OBP or with the > OS debug tools. > > -David > > -- Hitendra Zhangada ==================================== SPS Common SW Features Engineering Systems Group, Sun Microsystems, Inc. Sun Ph# (858) 625 3757, Sun Ext. x53757 Internal homepage http://esp.west/~hitu From sacadmin Wed Dec 10 18:08:04 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBB283h4001365 for ; Wed, 10 Dec 2008 18:08:04 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBB283BO004954; Wed, 10 Dec 2008 19:08:03 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBO00409WLE8D00@nwk-avmta-2.sfbay.sun.com>; Wed, 10 Dec 2008 18:08:02 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBO00FDFWLEYZ80@nwk-avmta-2.sfbay.sun.com>; Wed, 10 Dec 2008 18:08:02 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mBB2823k002904; Wed, 10 Dec 2008 18:08:02 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBO00C01WFWKZ00@fe-sfbay-09.sun.com> (original mail from Hitendra.Zhangada@Sun.COM); Wed, 10 Dec 2008 18:08:02 -0800 (PST) Received: from [129.153.85.35] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBO004AHWLC8XE0@fe-sfbay-09.sun.com>; Wed, 10 Dec 2008 18:08:01 -0800 (PST) Date: Wed, 10 Dec 2008 18:08:00 -0800 From: Hitendra Zhangada Subject: Re: fast-track : 2008/761 - Supernova Platform Binding In-reply-to: <4940429A.3040306@Sun.COM> Sender: Hitendra.Zhangada@sun.com To: Firmware ARC Cc: Pingchun Lee , us-staff@sun.com Message-id: <49407600.1020101@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49402F05.2070100@sun.com> <4940312A.2070700@Sun.COM> <49403208.5060506@sun.com> <4940429A.3040306@Sun.COM> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 1610 On 12/10/08 14:28, Hitendra Zhangada wrote: > On 12/10/08 13:18, David Kahn wrote: >> >> >> Pingchun Lee wrote: >>> That is useful for debugging purpose. It's easier to check >>> if hardware is configured correctly by checking the property >>> instead of 'selecting device to read register and decode it' when >>> something doesn't work. >> >> Can we get rid of them? Properties create an interface, >> and they really aren't needed for debug only. > > FYI. I am working with Ping to remove this property > and also take care of comment related to slot-names > property. New updated specification will be available > in next few hours and timer will reset to another week. Updated specification has been copied to the case directory at, http://sac.sfbay.sun.com/Archives/CaseLog/arc/FWARC/2008/761/Materials/UpdatedSpec_SNBindings.txt The changes includes, #1 Removal of "port-type" property #2 Removal of "slot-names" property from specification since there are no changes to the definition of this property. The property will still be created using existing interfaces (from values provided in MD). The values of the property itself are platform specific. The timer has been extended to Dec 17th, 2008 (week from today). Updated PCI Express bindings, PRI and iodevice.txt files will be copied to the case directory prior to approval of this case. Thanks. -- Hitendra Zhangada ==================================== SPS Common SW Features Engineering Systems Group, Sun Microsystems, Inc. Sun Ph# (858) 625 3757, Sun Ext. x53757 Internal homepage http://esp.west/~hitu From sacadmin Wed Dec 17 17:49:19 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBI1nIJo028077 for ; Wed, 17 Dec 2008 17:49:18 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mBI1nFmD001943; Thu, 18 Dec 2008 01:49:17 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KC100M09UE3X600@nwk-avmta-2.sfbay.sun.com>; Wed, 17 Dec 2008 17:49:15 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KC100JUAUE2QW10@nwk-avmta-2.sfbay.sun.com>; Wed, 17 Dec 2008 17:49:14 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mBI1nEmp002600; Wed, 17 Dec 2008 17:49:14 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KC100801UCOIU00@fe-sfbay-10.sun.com> (original mail from Hitendra.Zhangada@Sun.COM); Wed, 17 Dec 2008 17:49:14 -0800 (PST) Received: from [129.153.85.35] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KC100B6IUE16R90@fe-sfbay-10.sun.com>; Wed, 17 Dec 2008 17:49:14 -0800 (PST) Date: Wed, 17 Dec 2008 17:49:13 -0800 From: Hitendra Zhangada Subject: Re: fast-track : 2008/761 - Supernova Platform Binding In-reply-to: <49407600.1020101@Sun.COM> Sender: Hitendra.Zhangada@sun.com To: Firmware ARC Cc: Pingchun Lee , us-staff@sun.com Message-id: <4949AC19.5050206@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49402F05.2070100@sun.com> <4940312A.2070700@Sun.COM> <49403208.5060506@sun.com> <4940429A.3040306@Sun.COM> <49407600.1020101@Sun.COM> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 2473 On 12/10/08 18:08, Hitendra Zhangada wrote: > On 12/10/08 14:28, Hitendra Zhangada wrote: >> On 12/10/08 13:18, David Kahn wrote: >>> >>> >>> Pingchun Lee wrote: >>>> That is useful for debugging purpose. It's easier to check >>>> if hardware is configured correctly by checking the property >>>> instead of 'selecting device to read register and decode it' when >>>> something doesn't work. >>> >>> Can we get rid of them? Properties create an interface, >>> and they really aren't needed for debug only. >> >> FYI. I am working with Ping to remove this property >> and also take care of comment related to slot-names >> property. New updated specification will be available >> in next few hours and timer will reset to another week. > > Updated specification has been copied to the case directory at, > http://sac.sfbay.sun.com/Archives/CaseLog/arc/FWARC/2008/761/Materials/UpdatedSpec_SNBindings.txt > > > > The changes includes, > > #1 Removal of "port-type" property > #2 Removal of "slot-names" property from specification since there > are no changes > to the definition of this property. The property will still be > created using existing > interfaces (from values provided in MD). The values of the > property itself are > platform specific. > > The timer has been extended to Dec 17th, 2008 (week from today). > > Updated PCI Express bindings, PRI and iodevice.txt files will be copied > to the case directory prior to approval of this case. I have copied updated PRI and PCI Express bindings as well as updated iodevice.txt (includes some corrections) in the case directory. You can access it at, Updated PRI Specification : http://sac.sfbay.sun.com/Archives/CaseLog/arc/FWARC/2008/761/Materials/PRI_Specification_16.txt Updated PCI Express Bindings : http://sac.sfbay.sun.com/Archives/CaseLog/arc/FWARC/2008/761/Materials/pcie_bindings_111.txt Updated iodevice.txt : http://sac.sfbay.sun.com/Archives/CaseLog/arc/FWARC/2008/761/Materials/iodevice_12.txt I have also updated the links from the main FWARC page too. PCI Express bindings were not available from main page, I have added that too. This case is approved for, Release Binding: firmware: minor/micro firmware release OS: minor/micro/patch OS release. -- Hitendra Zhangada ==================================== SPS Common SW Features Engineering Systems Group, Sun Microsystems, Inc. Sun Ph# (858) 625 3757, Sun Ext. x53757 Internal homepage http://esp.west/~hitu