From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=2607:f8b0:4864:20::62f; helo=mail-pl1-x62f.google.com; envelope-from=prabinca4u@gmail.com; receiver=edk2-devel@lists.01.org Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 3E8AC21194D32 for ; Fri, 23 Nov 2018 22:10:04 -0800 (PST) Received: by mail-pl1-x62f.google.com with SMTP id y6-v6so11469925plt.3 for ; Fri, 23 Nov 2018 22:10:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7F9tMD7fkS3Htjm/jGmEngT+UagtuGRBzdutRDbg9L0=; b=Fi19K1YXPFGpdJpd4VLr7ajk91Gf3eEYKe++0wT3PnlGTSy21iKi8ueWEd9xYNDqfP JOz9J0Mt7UKmoSuq9G6YZdhhD812C71ZWSkhvKF+VuvRw9T0YV/ivwIqM3rs/HvO5C4p 4cJI/bpurTEw32GqpfJY1fMr5Cx3R337aGEfCCBaasQQf75dO/QxTF/2e9EpQeOHEZ/W R2gnq3X1SELeIXsELreiArqSK2HT8Iv3hszCS/6eleTLTFjKLAbP+8XVhb9BLMLU70bV hp0ffqg0o4/0BwhedOJIh59DD5SA5AL2nbEDhXHJYaD1YEGPkKOb35fVd0ykKFakr93/ 06Mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7F9tMD7fkS3Htjm/jGmEngT+UagtuGRBzdutRDbg9L0=; b=cq0MsJhWxOgnTh9IbhLXdf9EQkE6uemnVUaMSpE7CaY6jGQeCvD8ZDnWJMuNXqDjwF HFpg7ISTCWen/Az+5rHottnFkB0iLNPZnWYLZbdIqr05JRkFTeGUKI+z6Moe0xOnH+OR 9zwIfJNQGYSGFcPwUmh9B51kaJ725Pjz1R436Z90aAgbVsFNt3HkcnQ06ivAKMWBQgQl Ay9GCJSgFvmJ28Vgi92t74Hn2VgChMDzGx1cKtmMuO2F4MENNcdHLKhOLwF/nfaPsBi6 CGHWGXLgsioqSaMCZzhtIjP48bZvQm6yljyeKAT+ARDo1CeYZBM27ey7G5GpraHUMmL5 U9kg== X-Gm-Message-State: AA+aEWZgudtRorEqt3JGT4qW83T0dB/jIqgMMIyCVbeJDlxnivHQN5Hs R6w48DfH5GFzZnjqCVimYZA= X-Google-Smtp-Source: AFSGD/VfwarBkaNCYeq0O2idtDLSFxpOKMxcgQpOHJZEb6ZMyGbgDDurvc8i6x9eGmcW/rBw2jOLKg== X-Received: by 2002:a17:902:2c03:: with SMTP id m3mr18010343plb.6.1543039803634; Fri, 23 Nov 2018 22:10:03 -0800 (PST) Received: from [192.168.1.3] ([103.199.161.86]) by smtp.gmail.com with ESMTPSA id p9-v6sm62929381pfa.22.2018.11.23.22.10.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Nov 2018 22:10:03 -0800 (PST) Mime-Version: 1.0 (1.0) From: prabin ca X-Mailer: iPhone Mail (16B92) In-Reply-To: <163aeada-5a63-9a69-e220-1bb2a175644c@redhat.com> Date: Sat, 24 Nov 2018 11:39:57 +0530 Cc: edk2-devel@lists.01.org, dandan.bi@intel.com, afish@apple.com Message-Id: References: <28112B7C-8710-4394-9990-B69C5FDD15E5@gmail.com> <163aeada-5a63-9a69-e220-1bb2a175644c@redhat.com> To: Laszlo Ersek 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: Sat, 24 Nov 2018 06:10:04 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Laszlo, Thanks for your support, let me look on this=20 > On 23-Nov-2018, at 2:49 PM, Laszlo Ersek wrote: >=20 >> On 11/23/18 07:27, prabin ca wrote: >> Hi Team, >>=20 >> I=E2=80=99m new to UEFI and display interface in UEFI. I would like to ha= ve deep dive into how display is working in UEFI (display architecture) and h= ow display is have been bring up (porting of display panel in a any platform= in general ). >>=20 >> Please help me with sample codes and necessary documents. I would like to= get knowledge about display bring up and display architecture in UEFI >=20 > 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. >=20 > https://github.com/tianocore/tianocore.github.io/wiki/UEFI-Driver-Writer%2= 7s-Guide >=20 >=20 > 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= . >=20 >=20 > In addition, you might want to look into the generic >=20 > MdeModulePkg/Universal/Console/GraphicsOutputDxe >=20 > 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: >=20 > MdePkg/Include/Guid/GraphicsInfoHob.h >=20 > (... 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. =46rom the following two commit messages: >=20 > - 697c6cf32693 ("MdePkg: Add PI 1.4 Graphics HOB and PPI header files", > 2015-04-28) >=20 > - 2af538fbf667 ("MdeModulePkg: Add GraphicsOutputDxe driver.", 2016-10-12)= >=20 > 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.) >=20 > Thanks > Laszlo