From: Evan Lloyd <Evan.Lloyd@arm.com>
To: "ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
Leif Lindholm <leif.lindholm@linaro.org>
Cc: Girish Pathak <Girish.Pathak@arm.com>,
edk2-devel <edk2-devel@lists.01.org>,
"ryan.harkin@linaro.org" <ryan.harkin@linaro.org>,
Sami Mujawar <Sami.Mujawar@arm.com>,
Alexei Fedorov <Alexei.Fedorov@arm.com>
Subject: Re: ArmPlatformPkg: LcdGraphicsOutputDxe, PL111, and HdLcd rejig
Date: Thu, 4 May 2017 14:49:42 +0000 [thread overview]
Message-ID: <AM4PR0801MB14449986C7CF4395BBCE75868BEA0@AM4PR0801MB1444.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <5D22060A-68B9-4632-A884-07220A737BA9@linaro.org>
> -----Original Message-----
> From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
...
> >
> > The real improvement is the reduction in code duplication.
> >
>
> Perhaps we shoukd move to the UEFI driver model at the same time?
>
[[Evan Lloyd]] That would certainly be the "proper" way to do it.
The reasons not to are:
1. So that early output can be seen on the display.
(I confess that argument would be stronger were ConSplitterDxe not itself UEFI driver model) :-{
2. The theoretical case of a boot logo, which, I think, should flash up as early as possible.
However, we don't feel strongly about either.
...
Regards,
Evan
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
prev parent reply other threads:[~2017-05-04 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 16:58 ArmPlatformPkg: LcdGraphicsOutputDxe, PL111, and HdLcd rejig Girish Pathak
2017-05-04 11:14 ` Leif Lindholm
2017-05-04 13:34 ` Ard Biesheuvel
2017-05-04 14:49 ` Evan Lloyd [this message]
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=AM4PR0801MB14449986C7CF4395BBCE75868BEA0@AM4PR0801MB1444.eurprd08.prod.outlook.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