From: "Bret Barkelew" <bret.barkelew@microsoft.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"jbrasen@nvidia.com" <jbrasen@nvidia.com>
Cc: "jian.j.wang@intel.com" <jian.j.wang@intel.com>,
"ao.a.wu@intel.com" <ao.a.wu@intel.com>,
Jeff Brasen <jbrasen@nvidia.com>
Subject: Re: [EXTERNAL] [edk2-devel] [PATCH 1/1] MdeModulePkg/BmpSupportLib: Allow BMP with extra data
Date: Tue, 23 Mar 2021 17:41:28 +0000 [thread overview]
Message-ID: <MW4PR21MB1907D81FE3C97F62AD10C4DBEF649@MW4PR21MB1907.namprd21.prod.outlook.com> (raw)
In-Reply-To: <70c26f78d461d1b8021462d3c3fe6eb717b19193.1616520420.git.jbrasen@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]
Is this a *good* idea?
What is considered valid extra data? If it’s immaterial to the FW displaying the image, our policy has been to strip it off BEFORE adding it to the FW image.
- Bret
From: Jeff Brasen via groups.io<mailto:jbrasen=nvidia.com@groups.io>
Sent: Tuesday, March 23, 2021 10:29 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Cc: jian.j.wang@intel.com<mailto:jian.j.wang@intel.com>; ao.a.wu@intel.com<mailto:ao.a.wu@intel.com>; Jeff Brasen<mailto:jbrasen@nvidia.com>
Subject: [EXTERNAL] [edk2-devel] [PATCH 1/1] MdeModulePkg/BmpSupportLib: Allow BMP with extra data
Add support for processing BMP data that contains extra data after the
image array, this data will not be parsed in anyway in the library but
images that contain this will not be rejected from processing.
---
MdeModulePkg/Library/BaseBmpSupportLib/BmpSupportLib.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MdeModulePkg/Library/BaseBmpSupportLib/BmpSupportLib.c b/MdeModulePkg/Library/BaseBmpSupportLib/BmpSupportLib.c
index 3ac31f6723d0..944d01fe7cdf 100644
--- a/MdeModulePkg/Library/BaseBmpSupportLib/BmpSupportLib.c
+++ b/MdeModulePkg/Library/BaseBmpSupportLib/BmpSupportLib.c
@@ -213,7 +213,7 @@ TranslateBmpToGopBlt (
if ((BmpHeader->Size != BmpImageSize) ||
(BmpHeader->Size < BmpHeader->ImageOffset) ||
- (BmpHeader->Size - BmpHeader->ImageOffset != DataSize)) {
+ (BmpHeader->Size - BmpHeader->ImageOffset < DataSize)) {
DEBUG ((DEBUG_ERROR, "TranslateBmpToGopBlt: invalid BmpImage... \n"));
DEBUG ((DEBUG_ERROR, " BmpHeader->Size: 0x%x\n", BmpHeader->Size));
--
2.25.1
[-- Attachment #2: Type: text/html, Size: 3918 bytes --]
next prev parent reply other threads:[~2021-03-23 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 17:29 [PATCH 1/1] MdeModulePkg/BmpSupportLib: Allow BMP with extra data Jeff Brasen
2021-03-23 17:41 ` Bret Barkelew [this message]
2021-03-24 11:31 ` [EXTERNAL] [edk2-devel] " Laszlo Ersek
2021-03-24 15:25 ` Jeff Brasen
2021-03-24 18:26 ` Laszlo Ersek
2021-03-25 3:00 ` Andrew Fish
2021-03-30 1:35 ` Gao, Zhichao
2021-04-01 17:37 ` Bret Barkelew
2021-04-16 17:12 ` Jeff Brasen
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=MW4PR21MB1907D81FE3C97F62AD10C4DBEF649@MW4PR21MB1907.namprd21.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