1. Introduction
   1.1. Project/Component Working Name:

        Congo Platform Binding.
	
   1.2. Name of Document Author/Supplier:

        Yu Kong	
	
   1.3. Date of This Document:

	02/07/08

   1.4. Name of Major Document Customer(s)/Consumer(s):
	1.4.1. The PAC or CPT you expect to review your project:
		HS 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:
		Mike.Sanfratello@Sun.com
		
	1.4.4. The name of your business unit:
		Systems Group

   1.5. Email Aliases:
    	1.5.1 Responsible Manager:	chad.solomon@sun.com
    	1.5.2 Responsible Engineer:	yu.kong@sun.com
        1.5.3 Platform program Manager  anja.seibt@sun.com
        1.5.4 Engineering Manager:      marv.wexler@sun.com
        1.5.5 Interest list:            congo-eteam@sun.com

2. Project Summary

   2.1. Project Description:

	Congo 4U AC/DC server are the next generation CMT 19" rack
	servers for Telecom market. Congo is based on Victoria Falls
	processors, and it is leveraged from Maramba motherboard.
 
	This project registers the "banner-name" and root node "name" 
	property values used on the Congo platform. OpenBoot extracts
	these values from the guest MDs and creates the properties for
	Solaris to use.

	Minor changes are also required to the vBSC/POST interface to
	allow POST to return information relevant to I/O devices found
	on Congo.


   2.2  Risks and Assumptions:

	Assumptions:
	------------
	- Congo OepnBoot code will be leverage from Maramba OpenBoot.
        There is no OpenBoot code change.

	- All Maramba related FWARC cases are reviewed and approved
	prior to Congo release.


3. Business Summary
   3.1. Problem Area:

        This one pager provides information about properties and name 
	provided by Congo at the system firmware level, which must be
	registered with FWARC.

   3.2. Market/Requester:

        NSN

   3.3. Business Justification:

        N/A

   3.4. Competitive Analysis:

        N/A

   3.5. Opportunity Window/Exposure:

        Required for Congo RR

   3.6. How will you know when you are done?:

        When the related code changes are integrated into 4.x gate.

4. Technical Description:

   4.1 New Development

   4.1.1 OpenBoot properties
 
	Congo will have the following root name "name" and
	"banner-name" properties.

	"name"
	   Type: Prop-encoded-string
	   Contents: Root node name property for Congo
	   Value: "SUNW,Netra-T5440"

	"banner-name"
	   Type: Prop-encoded-string
	   Contents: Banner name for Congo
	   Value: "Sun Netra T5440"


   4.1.2 vBSC/POST interface

	vBSC/POST interface for Congo is identical to the one defined for
	Maramba (FWARC/2007/605 section 7) with a very minor change in 
	"IO Device Results" field. The unused bit 9 (in Maramba) is used
	in Congo.

   4.1.2.1  IO device Results

	Bit	Maramba Devices		Congo Devices
        -----   -------------------     --------------------------------

	0	XAUI0			XAUI0
	1	XAUI1			XAUI1
	2	PCISWITCH0		PCISWITCH0
	3	PCISWITCH1		PCISWITCH1
	4	PCISWITCH2		PCISWITCH2
	5	PCISWITCH3 		PCISWITCH3
	6	GBE			GBE
	7	PCIEIO			PCIEIO
	8	SASHBA			SASHBA
	9	Unused			PCIE Bridge	(New for Congo)


   4.2  Interfaces:

	Imported Interfaces:

	Interface		Classification	Comments

	"name"			Standard	FWARC/1998/392
						(Standard IEEE 1275 Property)

	"banner-name"		Stable		FWARC/1998/392
						(Legacy Property)

	vBSC/POST Interface	Uncommitted	FWARC/2007/605


	Exported Interfaces:

	"SUNW,Netra-T5440"	Uncommitted	"name" property value

	"Sun Netra T5440"	Uncommitted	"banner-name" property value

	"IO Device Results"	Uncommitted	Section 4.1.2
	field for Congo
	


5. Reference Documents:

	[1] FWARC 2007/651  Maramba Host Type Definitions

            http://sac.eng/Archives/CaseLog/arc/FWARC/2007/651/

        [2] FWARC 2007/605 Sun4v VBSC to POST Interface

            http://sac.eng/Archives/CaseLog/arc/FWARC/2007/605/


6. Resources and Schedule:
   6.1. Projected Availability:

        Q2 FY08

   6.2. Cost of Effort:

        4 man month

   6.3. Cost of Capital Resources:

	Need access to a dedicated Congo system for OpenBoot/vBSC development 
	during P0, P0.1 and P1 stages.

   6.4. Product Approval Committee requested information:
        6.4.1. Consolidation or Component Name:
               OpenBoot

        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:

        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:

   7.2. Prototype Cost: