From markk@sagredo.West.Sun.COM Thu Sep 15 09:36:45 1994 Date: Thu, 15 Sep 1994 09:35:54 -0700 From: markk@sagredo.West.Sun.COM (Mark K.) To: psarc@Eng Subject: DRAFT OPINION PSARC 1994/302 PPC Boot Cc: Steven.Z.@West, Abe.Ellenberg@West Content-Length: 6231 sun microsystems Systems Architecture Committee _________________________________________________________________ Subject: Power PC Booting Submitted by: Steven Z. File: psarc/1994/302/opinion.ms Date: 09/07/94 Committee: Mark K., Steve C., Bruce D., Robert H., Yousef K., Joseph Kowal- ski, Terrence M., Bill Shannon. 1. Summary It is expected that many Power PC platforms will have Open Boot Prom support. The current reference platform (XXX XXX- XXXXXXX), however, does not yet support OBP. Moreover, it is expected that there will be other Power PC platforms that will not have OBP. This project proposes a standard frame- work for the booting and auto-configuration of non-OBP plat- forms. The crux of this proposal is that the interface to platform specific I/O and configuration functions will be that defined by IEEE P1275 - whether or not the machine actually has OBP PROMs. The main body of the proposal[3] is a description of how platforms without Open Firmware can pro- vide the required IEEE P1275 services. 2. Decision & Precedence Information The project is accepted, and can be included in a minor release. 3. Opinion ___________________________________________________________________ | Interfaces Exported | |_____________________________________|________________|__________| |Interface | Classification| Comments| |_____________________________________|________________|__________| |IEEE P1275[1] | standard | | |Power PC binding to Open Firmware[2]| standard | | |DOS FAT 12 file system | standard | | |Extensible Linking Format | standard | | |bootstrap location/format | public | | |sample CIF implementation | uncommitted | | |_____________________________________|________________|__________| psarc/1994/302 Copyright 1994 Sun Microsystems, Inc. - 2 - ___________________________________________________________________ | Interfaces Exported | |_____________________________________|________________|__________| |Interface | Classification| Comments| |_____________________________________|________________|__________| |_____________________________________|________________|__________| In order to load a Solaris kernel into memory the bootstrap may need to be able to do I/O to several devices (the specific list is platform dependent, but the obvious candi- dates are keyboard, display, CD, network, disk and diskette). On systems with Open Firmware, these I/O ser- vices are provided according to a standard interface. On systems without Open Firmware, auxiliary (platform specific) drivers must be supplied to provide these services. The manner in which these drivers are supplied and the interface they provide to the Solaris bootstrap is a fundamental ques- tion to be answered for any non-OBP platform or architec- ture. Other projects (e.g. Solaris/x86) chose an interface that paralleled that provided by the standard ROMs on those machines. This project proposes that the interface to those services should be the same one specified by the Open Firmware standard. This makes it much easier to use exist- ing bootstrap code (which is already implemented to that interface). This leaves, however, the problem of how to implement that interface on a particular platform. This project proposes a general form for that implementa- tion, but very few actual interfaces. 1. A platform specific Client InterFace module (CIF) must be supplied. The CIF module includes device drivers for all of the boot devices, and code to handle the identification/autoconfiguration of those devices. These functions may be implemented in terms of ROM ser- vices available on the platform ... but that is a platform-specific implementation detail. 2. Upon booting, a platform specific mechanism finds and loads the CIF module into memory. 3. The CIF module constructs a device information tree (for at least the boot devices). 4. The CIF module locates and loads the standard Solaris bootstrap (an ELF file in an standard place) into memory and transfers control to it. 5. The Solaris bootstrap accesses configuration informa- tion and I/O services through the P1275 client inter- faces. psarc/1994/302 Copyright 1994 Sun Microsystems, Inc. - 3 - 6. Later after Solaris has been installed, a platform specific script will be run in order to turn the system disk into a bootable device. The project proposes to provide the XXXXXXXXXX code as a sample CIF implementation for OEMs who need to do CIF imple- mentations for new platforms. It is expected that implemen- tations will be heavily based on this sample code ... but the platform developers are free to use, modify or discard this code in any way they deem appropriate. The sample code will contain numerous interfaces, but most of them are com- pletely internal to the sample and carry no commitment level. The only external interfaces to the CIF are the IEEE P1275 standard and the location and format of the Solaris bootstrap. 4. Minority Opinion(s) 5. Advisory Information The committee found this to be an elegant solution to a recurring problem, and recommends that the same solution be employed in future ports to non-OBP platforms. 6. Appendices 6.1. Appendix A: Technical Changes Required 6.2. Appendix B: Technical Changes Advised 6.3. Appendix C: Reference Material 1. IEEE P1275 Open Firmware Services 2. Power PC ISA Bindings to Open Firmware 3. PSARC/1994/302/materials/bootconf.ps psarc/1994/302 Copyright 1994 Sun Microsystems, Inc. From markk@sagredo.West.Sun.COM Wed Sep 28 17:52:54 1994 Date: Wed, 28 Sep 1994 17:52:02 -0700 From: markk@sagredo.West.Sun.COM (Mark K.) To: sac-review@sac.Eng.Sun.COM Subject: Draft Opinion: PSARC 1994/302 (Power PC Boot) Content-Length: 6231 sun microsystems Systems Architecture Committee _________________________________________________________________ Subject: Power PC Booting Submitted by: Steven Z. File: psarc/1994/302/opinion.ms Date: 09/07/94 Committee: Mark K., Steve C., Bruce D., Robert H., Yousef K., Joseph Kowal- ski, Terrence M., Bill Shannon. 1. Summary It is expected that many Power PC platforms will have Open Boot Prom support. The current reference platform (XXX XXX- XXXXXXX), however, does not yet support OBP. Moreover, it is expected that there will be other Power PC platforms that will not have OBP. This project proposes a standard frame- work for the booting and auto-configuration of non-OBP plat- forms. The crux of this proposal is that the interface to platform specific I/O and configuration functions will be that defined by IEEE P1275 - whether or not the machine actually has OBP PROMs. The main body of the proposal[3] is a description of how platforms without Open Firmware can pro- vide the required IEEE P1275 services. 2. Decision & Precedence Information The project is accepted, and can be included in a minor release. 3. Opinion ___________________________________________________________________ | Interfaces Exported | |_____________________________________|________________|__________| |Interface | Classification| Comments| |_____________________________________|________________|__________| |IEEE P1275[1] | standard | | |Power PC binding to Open Firmware[2]| standard | | |DOS FAT 12 file system | standard | | |Extensible Linking Format | standard | | |bootstrap location/format | public | | |sample CIF implementation | uncommitted | | |_____________________________________|________________|__________| psarc/1994/302 Copyright 1994 Sun Microsystems, Inc. - 2 - ___________________________________________________________________ | Interfaces Exported | |_____________________________________|________________|__________| |Interface | Classification| Comments| |_____________________________________|________________|__________| |_____________________________________|________________|__________| In order to load a Solaris kernel into memory the bootstrap may need to be able to do I/O to several devices (the specific list is platform dependent, but the obvious candi- dates are keyboard, display, CD, network, disk and diskette). On systems with Open Firmware, these I/O ser- vices are provided according to a standard interface. On systems without Open Firmware, auxiliary (platform specific) drivers must be supplied to provide these services. The manner in which these drivers are supplied and the interface they provide to the Solaris bootstrap is a fundamental ques- tion to be answered for any non-OBP platform or architec- ture. Other projects (e.g. Solaris/x86) chose an interface that paralleled that provided by the standard ROMs on those machines. This project proposes that the interface to those services should be the same one specified by the Open Firmware standard. This makes it much easier to use exist- ing bootstrap code (which is already implemented to that interface). This leaves, however, the problem of how to implement that interface on a particular platform. This project proposes a general form for that implementa- tion, but very few actual interfaces. 1. A platform specific Client InterFace module (CIF) must be supplied. The CIF module includes device drivers for all of the boot devices, and code to handle the identification/autoconfiguration of those devices. These functions may be implemented in terms of ROM ser- vices available on the platform ... but that is a platform-specific implementation detail. 2. Upon booting, a platform specific mechanism finds and loads the CIF module into memory. 3. The CIF module constructs a device information tree (for at least the boot devices). 4. The CIF module locates and loads the standard Solaris bootstrap (an ELF file in an standard place) into memory and transfers control to it. 5. The Solaris bootstrap accesses configuration informa- tion and I/O services through the P1275 client inter- faces. psarc/1994/302 Copyright 1994 Sun Microsystems, Inc. - 3 - 6. Later after Solaris has been installed, a platform specific script will be run in order to turn the system disk into a bootable device. The project proposes to provide the XXXXXXXXXX code as a sample CIF implementation for OEMs who need to do CIF imple- mentations for new platforms. It is expected that implemen- tations will be heavily based on this sample code ... but the platform developers are free to use, modify or discard this code in any way they deem appropriate. The sample code will contain numerous interfaces, but most of them are com- pletely internal to the sample and carry no commitment level. The only external interfaces to the CIF are the IEEE P1275 standard and the location and format of the Solaris bootstrap. 4. Minority Opinion(s) 5. Advisory Information The committee found this to be an elegant solution to a recurring problem, and recommends that the same solution be employed in future ports to non-OBP platforms. 6. Appendices 6.1. Appendix A: Technical Changes Required 6.2. Appendix B: Technical Changes Advised 6.3. Appendix C: Reference Material 1. IEEE P1275 Open Firmware Services 2. Power PC ISA Bindings to Open Firmware 3. PSARC/1994/302/materials/bootconf.ps psarc/1994/302 Copyright 1994 Sun Microsystems, Inc. From roland.mainz@nrubsig.org Wed May 6 19:54:41 2009 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 n472sd2C008114 for ; Wed, 6 May 2009 19:54:40 -0700 (PDT) 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 n472sXGC029298; Thu, 7 May 2009 03:54:38 +0100 (BST) 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 <0KJ900E0J6QXUH00@nwk-avmta-2.sfbay.sun.com>; Wed, 06 May 2009 19:54:33 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJ900BSP6QX2670@nwk-avmta-2.sfbay.sun.com>; Wed, 06 May 2009 19:54:33 -0700 (PDT) Received: from relay15i.sun.com (ip125.net129179-4.block1.us.syntegra.com [129.179.4.125]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n472lgI1023995; Thu, 07 May 2009 02:54:32 +0000 (GMT) Received: from mmp14es.mmp.us.syntegra.com ([160.41.208.14] [160.41.208.14]) by relay15i.sun.com with ESMTP id BT-MMP-1721496; Thu, 07 May 2009 02:54:32 +0000 (Z) Received: from relay14i.sun.com (relay14i.sun.com [129.179.4.124]) by mmp14es.mmp.us.syntegra.com with ESMTP id BT-MMP-524814; Thu, 07 May 2009 02:54:32 +0000 (Z) Received: from mail-in-09.arcor-online.net ([151.189.21.49] [151.189.21.49]) by relay1i.sun.com with ESMTP id BT-MMP-5769081; Thu, 07 May 2009 02:54:32 +0000 (Z) Received: from mail-in-10-z2.arcor-online.net (mail-in-10-z2.arcor-online.net [151.189.8.27]) by mx.arcor.de (Postfix) with ESMTP id E20561AF2FA; Thu, 07 May 2009 04:16:49 +0200 (CEST) Received: from mail-in-11.arcor-online.net (mail-in-11.arcor-online.net [151.189.21.51]) by mail-in-10-z2.arcor-online.net (Postfix) with ESMTP id CA18723D2B5; Thu, 07 May 2009 04:16:49 +0200 (CEST) Received: from jupiterb48.nrubsig.org (dslb-094-219-212-156.pools.arcor-ip.net [94.219.212.156]) by mail-in-11.arcor-online.net (Postfix) with ESMTPS id 27B9EE38FE; Thu, 07 May 2009 04:16:48 +0200 (CEST) Received: from nrubsig.org (localhost [127.0.0.1]) by jupiterb48.nrubsig.org (8.13.8+Sun/8.13.8) with ESMTP id n472GkrR002190; Thu, 07 May 2009 04:16:47 +0200 (CEST) Date: Thu, 07 May 2009 04:16:46 +0200 From: Roland Mainz Subject: Requesting ARC cases 1993/685, 1994/188, 1994/196, 1994/197, 1994/302, 1995/077, 1995/082, 1995/153 Sender: gisburn@jupiterb48.nrubsig.org To: opensolaris-arc@opensolaris.org Cc: Bonnie Corwin , "PSARC-EXT@sun.com" , emerging-platforms-discuss@opensolaris.org Message-id: <4A02448E.1AC9B6BA@nrubsig.org> MIME-version: 1.0 X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.11 sun4u) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-11.arcor-online.net 27B9EE38FE X-Antispam: No, score=0.0/5.0, scanned in 0.057sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ x_sac_archived: PSARC/1993/685 x_sac_archived: PSARC/1994/188 x_sac_archived: PSARC/1994/196 Status: RO Content-Length: 704 hi! ---- I'd like to request to open the following ARC cases for publish access: PSARC 1993/685 PowerPC_ABI PSARC 1994/188 Solaris Kernel for PowerPC PSARC 1994/196 PowerPC Header Files PSARC 1994/197 PowerPC Commands PSARC 1994/302 PowerPC_Booting PSARC 1995/077 processor_info(2) binding for PowerPC and future ISAs PSARC 1995/082 PowerPC sysconfig parameters PSARC 1995/153 PPC installboot We need this materials as template for a set of ARC casess to specify support for a new architecture/hardware platform... ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;)