From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=192.55.52.88; helo=mga01.intel.com; envelope-from=brian.richardson@intel.com; receiver=edk2-devel@lists.01.org Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) (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 8BEC2207E36D6 for ; Thu, 10 May 2018 14:54:39 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 May 2018 14:54:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,386,1520924400"; d="scan'208";a="57635196" Received: from orsmsx107.amr.corp.intel.com ([10.22.240.5]) by orsmga002.jf.intel.com with ESMTP; 10 May 2018 14:54:38 -0700 Received: from orsmsx163.amr.corp.intel.com (10.22.240.88) by ORSMSX107.amr.corp.intel.com (10.22.240.5) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 10 May 2018 14:54:38 -0700 Received: from orsmsx114.amr.corp.intel.com ([169.254.8.4]) by ORSMSX163.amr.corp.intel.com ([169.254.9.19]) with mapi id 14.03.0319.002; Thu, 10 May 2018 14:54:38 -0700 From: "Richardson, Brian" To: Blibbet , "edk2-devel@lists.01.org" Thread-Topic: [edk2] OVMF Logo Thread-Index: AQHT5i5wfva6KsvgJ0+mdYxNloAZe6QmGZiA//+7ohCAAr1FgIAA8/OA Date: Thu, 10 May 2018 21:54:37 +0000 Message-ID: <80AC2BAA3152784F98F581129E5CF5AFAF1ECDE6@ORSMSX114.amr.corp.intel.com> References: <80AC2BAA3152784F98F581129E5CF5AFAF1E9570@ORSMSX114.amr.corp.intel.com> <21ad5942-48f0-47c7-996a-34f783323c0f@gmail.com> In-Reply-To: <21ad5942-48f0-47c7-996a-34f783323c0f@gmail.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNzhjYmQ1MzAtNGMzYy00MjQ1LWI4MzUtMzhhN2JjOTk3YWYwIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IkVXcmpwMUE0WStoRTVPb3dUVXNqS3d4WGNxRzVGK0JDSjladEJOcDFaZ009In0= dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [10.22.254.139] MIME-Version: 1.0 Subject: Re: OVMF Logo X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2018 21:54:39 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable You shouldn't have to hack BGRT in OVMF since you change the logo in the ED= K II source. Can you provide a screenshot to show what the logo corruption looks like? Thanks ... br --- Brian Richardson, Senior Technical Marketing Engineer, Intel Software brian.richardson@intel.com -- @intel_brian (Twitter & WeChat) https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian= -richardson=20 -----Original Message----- From: edk2-devel On Behalf Of Blibbet Sent: Wednesday, May 9, 2018 8:21 PM To: edk2-devel@lists.01.org Subject: Re: [edk2] OVMF Logo | [...] Is it possible to tune Logo's behavior in OVMF? [...] FYI, the HackBGRT tool exists, and may be helpful [on some bare-metal syste= ms, unclear about OVMF-based usefulness]. I've never used it. https://github.com/Metabolix/HackBGRT https://firmwaresecurity.com/2018/03/22/hackbgrt-how-to-change-windows-boot= -logo-using-hackbgrt/ HTH, Lee Fisher _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel