From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.120])
 by mx.groups.io with SMTP id smtpd.web11.1221.1588190139141241510
 for <devel@edk2.groups.io>;
 Wed, 29 Apr 2020 12:55:40 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=gDeoKGgV;
 spf=pass (domain: redhat.com, ip: 205.139.110.120, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1588190138;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=BZsPpTvw84RJtqhjv6a3BZFLK8m7FnBrJHpw+jwhPOM=;
	b=gDeoKGgVTjayQNLhCOvHYIzgZhdFKhosyGi51G6pkWFZCRsCmeGtgk/RRRoiQ2oxrCcKzG
	bj5r9OAa8fND2qrEuMINQjUveyPyjUfhbOHYDCDZQCGihqONDIL0DDQE9JF/nieDjPEB0A
	AuoYHmlxNvYSTeN14t6+EmjllQAsP6Y=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-358-6FW5TLNAN36Vh0JzvVrR-A-1; Wed, 29 Apr 2020 15:55:36 -0400
X-MC-Unique: 6FW5TLNAN36Vh0JzvVrR-A-1
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1D0F0835B40;
	Wed, 29 Apr 2020 19:55:35 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-114-1.ams2.redhat.com [10.36.114.1])
	by smtp.corp.redhat.com (Postfix) with ESMTP id 3B71C50F57;
	Wed, 29 Apr 2020 19:55:34 +0000 (UTC)
Subject: Re: [edk2-devel] EDK2 Logo Support
To: devel@edk2.groups.io, jim.slaughter@sage-micro.com
References: <CAP1zt84eWjdqTZq+22gKsJ-tocKqJMPngTFDs0=o81UmMmduwQ@mail.gmail.com>
Cc: Ray Ni <ray.ni@intel.com>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <d85f0106-9621-7f08-0db6-9f28c561a0f5@redhat.com>
Date: Wed, 29 Apr 2020 21:55:33 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAP1zt84eWjdqTZq+22gKsJ-tocKqJMPngTFDs0=o81UmMmduwQ@mail.gmail.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Language: en-US
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

+Ray

On 04/29/20 01:05, jim slaughter wrote:
> Hello,
> 
> I build and am running edk2-202002 (x86). Build done under WSL with Ubuntu
> 16.04.
> I found the Logo code and I need to replace the logo?
> The logo supplied with EDK2  is a .bmp file and is a tianocore logo.
> When I boot I never see the logo during the boot process? Is the logo used?
> I am not sure where the logo function is called during the boot process?
> Are there any documents on the logo? Where can I get information?
> Any help would be appreciated.
> Thanks.
> 

Please look at

MdeModulePkg/Include/Library/BootLogoLib.h
MdeModulePkg/Library/BootLogoLib/*
MdeModulePkg/Logo/LogoDxe.inf

and follow wherever those lead.

LogoDxe contains the image and exposes the custom protocol.

BootLogoLib lets your PlatformBootManagerLib instance consume (display)
the image via the protocol. You need to call the BootLogoLib functions
in your platform BDS code so the logo be displayed.

(Sorry, got no time to investigate / elaborate more in depth.)

hth
Laszlo