From: Laszlo Ersek <lersek@redhat.com>
To: prabin ca <prabinca4u@gmail.com>,
edk2-devel@lists.01.org, dandan.bi@intel.com, afish@apple.com
Subject: Re: Display Architecture and Bring Up in UEFI
Date: Fri, 23 Nov 2018 10:19:30 +0100 [thread overview]
Message-ID: <163aeada-5a63-9a69-e220-1bb2a175644c@redhat.com> (raw)
In-Reply-To: <28112B7C-8710-4394-9990-B69C5FDD15E5@gmail.com>
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.)
Thanks
Laszlo
next prev parent reply other threads:[~2018-11-23 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 6:27 Display Architecture and Bring Up in UEFI prabin ca
2018-11-23 9:19 ` Laszlo Ersek [this message]
2018-11-24 6:09 ` prabin ca
2018-11-27 1:45 ` Ni, Ruiyu
2018-11-27 15:13 ` prabin ca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=163aeada-5a63-9a69-e220-1bb2a175644c@redhat.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox