From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by mx.groups.io with SMTP id smtpd.web12.969.1588117111941621766 for ; Tue, 28 Apr 2020 16:38:32 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@preossec.com header.s=mesmtp header.b=cNVPRZyn; spf=pass (domain: preossec.com, ip: 64.147.123.25, mailfrom: lee@preossec.com) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 3391B802; Tue, 28 Apr 2020 19:38:31 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 28 Apr 2020 19:38:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=preossec.com; h= subject:to:references:cc:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=7kAhDvnIxvU+lr/N5M4U3pJJ1PP28RRKHghr3S3Dg7c=; b=cNVPRZynTcIl 4eMlX6BTypfCFk8l+3rGjai092mFinKsEP1jSbSsjPW7LhCfxddGzpEtFwKJs8TP I0rPuAS/esLseXD4JPaZON01q5KhORUSGI0ClSv5bbaEsK+vj6McEVYaiMTsLfH+ RA3UmmN8+WpNu4D/RZKYGpgPcyV7dQ8= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=7kAhDvnIxvU+lr/N5M4U3pJJ1PP28RRKHghr3S3Dg 7c=; b=Xjk6P5/fus395L269niEzdLB3wKtcI6gxuibj+3JVn7qrjo0k0orTYyHD 0HXp/O8iyPD2lilEeAhR5dKxmT3f6MAW4ofD5IITmM0g5tLy4Wl0osujsyLifyKM Qv9upJY8gT+xWPgNrq1V2LEceNUW8BmHShdiHmxljOqKhh+9GPn7tCcT0rFIYcql 7EKNxk/3AtFs1/DoS5nTD8Iv66gip5AJnK08yPtN3aKTjkkF6MzFXgMOo7OJt3Dc HeZZlCoOPhghv1yS/+FXHHrNoukTMJtNhMDrAKpfUGVs6Kl9bLiKSA6P0UFukP0L W8eU9eZGMpNlAg1bXG6R7ej6iPdzQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedriedvgddvfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepnfgvvgcuhfhishhhvghruceolhgvvgesphhrvghoshhsvggt rdgtohhmqeenucffohhmrghinhepfhhirhhmfigrrhgvshgvtghurhhithihrdgtohhmpd hfphhmuhhrphhhhidrtghomhdpmhhitghrohhsohhfthdrtghomhenucfkphephedtrdef hedrkedrkedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homheplhgvvgesphhrvghoshhsvggtrdgtohhm X-ME-Proxy: Received: from [192.168.1.100] (unknown [50.35.8.81]) by mail.messagingengine.com (Postfix) with ESMTPA id 48B8C3280065; Tue, 28 Apr 2020 19:38:30 -0400 (EDT) Subject: Re: [edk2-devel] EDK2 Logo Support To: jim.slaughter@sage-micro.com References: Cc: devel@edk2.groups.io From: lee@preossec.com Message-ID: <6a09fcfe-dfec-090d-21d3-45a237148e23@preossec.com> Date: Tue, 28 Apr 2020 16:38:26 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US Perhaps search for "BGRT"-related components. There are tools to modify the logo in binaries at run-time. Eg: https://firmwaresecurity.com/2020/02/10/bgrtinjector-customize-boot-logo-without-modifying-uefi/ https://firmwaresecurity.com/2016/05/21/hackbgrt-changes-windows-boot-logo-on-uefi-systems/ https://blog.fpmurphy.com/2015/07/access-bsrt-information-and-boot-logo-from-uefi-shell.html But I don't know how to change the logo in sources at design-time. I'm not aware of any Tianocore docs on the subject, the only OEM-focused info on topic I know of is Windows-centric: https://docs.microsoft.com/en-us/windows-hardware/drivers/bringup/boot-screen-components HTH, Lee PS: FWIW, one of my blog's most commonly-accessed articles are the above ones, end-users wanting to customize their logo. Maybe this is a sign that end-users want to customize their HW/FW/OS boot logos: perhaps OEMs/IHVs might want to add a feature to their product to let end-users easily change this, eg, from a BIOS Menu. On 4/28/20 4:05 PM, 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.