From sac-owner Fri Jul 24 17:19:10 2009 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 n6P0JAYl020268 for ; Fri, 24 Jul 2009 17:19:10 -0700 (PDT) Received: from sunmail2sca.sfbay.sun.com (localhost [127.0.0.1]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n6P0JAkF008157 for ; Fri, 24 Jul 2009 17:19:10 -0700 (PDT) Received: (from noaccess@localhost) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/Submit) id n6P0J9G7008155 for one-pager-not-2b-used-directly; Fri, 24 Jul 2009 17:19:09 -0700 (PDT) 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 n6P0J8Ga008115 for <@sunmail2sca.sfbay.sun.com:one-pager@sun.com>; Fri, 24 Jul 2009 17:19:09 -0700 (PDT) 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 <0KNB00L17A7WX800@nwk-avmta-1.sfbay.Sun.COM> for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 24 Jul 2009 17:19:08 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KNB00FJIA7WRZ70@nwk-avmta-1.sfbay.Sun.COM> for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 24 Jul 2009 17:19:08 -0700 (PDT) Received: from [129.146.226.114] (smack.SFBay.Sun.COM [129.146.226.114]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n6P0J7UA290387 for ; Fri, 24 Jul 2009 17:19:07 -0700 (PDT) Date: Fri, 24 Jul 2009 17:19:07 -0700 From: Jan Setje-Eilers Subject: [2009/415]VESA Console To: one-pager@sun.com Message-id: <4A6A4F7B.1040301@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.21 (X11/20090623) Status: RO Content-Length: 4546 Template Version: @(#)onepager.txt 1.35 07/11/07 SMI Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: VESA Console 1.2. Name of Document Author/Supplier: Jan Setje-Eilers 1.3. Date of This Document: 07/24/09 1.3.1. Date this project was conceived: 11/08 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: // This should match the spelling used in PLCtool, as this will be // used to cross-reference the information 1.4.2. The ARC(s) you expect to review your project: PSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Robert Lavender 1.4.4. The name of your business unit: Systems (Solaris Kernel) 1.5. Email Aliases: 1.5.1. Responsible Manager: Michael Pogue Michael.Pogue@Sun.COM 1.5.2. Responsible Engineer: Jan Setje-Eilers setje@sun.com 1.5.3. Marketing Manager: 1.5.4. Interest List: 2. Project Summary 2.1. Project Description: Support for higher resolutions and color depth than the current VGA 640x480 16-color console on x86 systems. 2.2. Risks and Assumptions: GRUB 2 merge, this project and feature-complete for .next are poorly aligned and pose a scheduling risk. 3. Business Summary 3.1. Problem Area: Console support for linear frame buffers is needed for EFI support. Better graphics during boot and shutdown are desired to surpass the 1970s first visual impression that Solaris currently presents. 3.2. Market/Requester: Sales / Marketing Systems and x86 OEMs 3.3. Business Justification: Sales / Marketing need the console appearance fixed in order to be able to present Solaris as a modern product. Systems and x86 OEMs would like to move from BIOS to native EFI systems and require Solaris to support them. 3.4. Competitive Analysis: Both Windows and Linux are ahead of us in this space. This project closes the gap. 3.5. Opportunity Window/Exposure: 3.6. How will you know when you are done?: Working high resolution console support integrates and active by default in Solaris.next. 4. Technical Description: 4.1. Details: The loader will automatically chose an appropriate video mode, activate it, then load the OS as before and hand a description of that mode to the OS. The early boot_console code will use that description to map the frame buffer and use it as a bitmapped console device. At consconfig gfx_private (which vgatext becomes a consumer of) will take over this role and the coherent console (tem) support will be used to display the console on this frame buffer. During a typical non-interactive boot the current "happy face" soothing image will remain however with more pixels and colors, and hence better (the current code is 640x480 with 16 colors or 4bit, we really do need better here). 4.2. Bug/RFE Number(s): 6803028 4.3. In Scope: 4.4. Out of Scope: 4.5. Interfaces: Public command to configure console size (rows/columns of text, resolution is chosen automatically). 4.6. Doc Impact: Man page for new command. Console screen shots could potentially be updated. However the actual content displayed on console is not impacted by this project, just what it looks like (better). 4.7. Admin/Config Impact: 4.8. HA Impact: none 4.9. I18N/L10N Impact: none 4.10. Packaging & Delivery: no new packages 4.11. Security Impact: none 4.12. Dependencies: EFI support depends on the linear frame buffer support delivered by this project. 5. Reference Documents: 6. Resources and Schedule: 6.1. Projected Availability: Q4 CY 09 6.2. Cost of Effort: 2 engineers / 9 months. 6.3. Cost of Capital Resources: Minor, mostly existing x86 systems, some graphics cards. 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: OSNet 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: Solaris.next Q4 CY 09 6.4.8. Target Code Design Review Date: 6.4.9. Update approval addition: 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open 6.6.1. Rationale: 7. Prototype Availability: 7.1. Prototype Availability: mid to end 08/09 7.2. Prototype Cost: 2 engineers 6 months