From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.24; helo=mga09.intel.com; envelope-from=ruiyu.ni@intel.com; receiver=edk2-devel@lists.01.org Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id EA59A21195BD0 for ; Mon, 26 Nov 2018 17:43:43 -0800 (PST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Nov 2018 17:43:43 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,284,1539673200"; d="scan'208";a="110917569" Received: from ray-dev.ccr.corp.intel.com (HELO [10.239.9.22]) ([10.239.9.22]) by fmsmga004.fm.intel.com with ESMTP; 26 Nov 2018 17:43:41 -0800 To: Laszlo Ersek , prabin ca , edk2-devel@lists.01.org, dandan.bi@intel.com, afish@apple.com References: <28112B7C-8710-4394-9990-B69C5FDD15E5@gmail.com> <163aeada-5a63-9a69-e220-1bb2a175644c@redhat.com> From: "Ni, Ruiyu" Message-ID: <5b413938-384d-cb1c-da7a-cdaba2b3b84e@Intel.com> Date: Tue, 27 Nov 2018 09:45:14 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <163aeada-5a63-9a69-e220-1bb2a175644c@redhat.com> Subject: Re: Display Architecture and Bring Up in UEFI X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2018 01:43:44 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit On 11/23/2018 5:19 PM, Laszlo Ersek wrote: > On 11/23/18 07:27, prabin ca wrote: >> Hi Team, >> >> I’m new to UEFI and display interface in UEFI. I would like to have deep dive into how display is working in UEFI (display architecture) and how display is have been bring up (porting of display panel in a any platform in general ). >> >> Please help me with sample codes and necessary documents. I would like to get knowledge about display bring up and display architecture in UEFI > > The driver writers' guide and the UEFI spec have relevant chapters on > this. I think it's best to start reading the former, at "23 Graphics > Driver Design Guidelines"; that part will give you the pointers to the > rest as well. > > https://github.com/tianocore/tianocore.github.io/wiki/UEFI-Driver-Writer%27s-Guide > > > For a (hopefully educational) example, I refer you to > OvmfPkg/VirtioGpuDxe. In the series that first added this driver to > edk2, I managed to construct the driver in stages such that each stage > would build and even function, at the level expected from that stage. In > particular, commit a2a4fa66701d ("OvmfPkg/VirtioGpuDxe: introduce with > Component Name 2 and Driver Binding", 2016-09-01) could prove helpful, > as it adds the skeleton of the driver, mostly without VirtIo GPU specifics. > > > In addition, you might want to look into the generic > > MdeModulePkg/Universal/Console/GraphicsOutputDxe > > driver. A platform may be able to incorporate that driver without any > changes, and control it by first producing the two HOBs in the PEI phase > that the driver consumes: > > MdePkg/Include/Guid/GraphicsInfoHob.h > > (... Interestingly, due to the fact that this header file is under > MdePkg and not MdeModulePkg, I've just learned, from the related commit > messages, that the PEI phase has standardized graphics support, > described in the PI spec. From the following two commit messages: > > - 697c6cf32693 ("MdePkg: Add PI 1.4 Graphics HOB and PPI header files", > 2015-04-28) > > - 2af538fbf667 ("MdeModulePkg: Add GraphicsOutputDxe driver.", 2016-10-12) > > it appears that enabling graphics support in the PEI phase could be a > *requirement* for using GraphicsOutputDxe in the DXE phase. That might > or might not match your use case, so perhaps it will prevent you from > using GraphicsOutputDxe. I'm not sure.) Yes. GraphicsOutputDxe layers on the HOB produced in PEI phase to provide GOP protocol. > > Thanks > Laszlo > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel > -- Thanks, Ray