From: Alexander Graf <agraf@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 5/6] efi_loader: new functions to print loaded image information
Date: Wed, 4 Apr 2018 11:38:29 +0200 [thread overview]
Message-ID: <4161780b-6a54-2ca7-7699-bae09f1a4573@suse.de> (raw)
In-Reply-To: <20180403202935.1466-6-xypron.glpk@gmx.de>
On 03.04.18 22:29, Heinrich Schuchardt wrote:
> Introduce functions to print information about loaded images.
>
> If we want to analyze an exception in an EFI image we need the offset
> between the PC and the start of the loaded image.
>
> With efi_print_image_info() we can print the necessary information for a
> single image, e.g.
>
> UEFI image
> start 0x7fdb4000, size 0xa7b60
> pc offset 0x72ca
> /\snp.efi
>
> efi_print_image_infos() provides output for all loaded images.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Sorry, I didn't see the new version earlier. The same comment applies
though. Please condense the output down to a single line.
Alex
next prev parent reply other threads:[~2018-04-04 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 20:29 [U-Boot] [PATCH v2 0/6] efi_loader: fixes for loaded image protocol Heinrich Schuchardt
2018-04-03 20:29 ` [U-Boot] [PATCH v2 1/6] efi_loader: use efi_uintn_t for LoadImage Heinrich Schuchardt
2018-04-03 20:29 ` [U-Boot] [PATCH v2 2/6] efi_loader: save image relocation address and size Heinrich Schuchardt
2018-04-03 20:29 ` [U-Boot] [PATCH v2 3/6] efi_loader: ImageSize must be multiple of SectionAlignment Heinrich Schuchardt
2018-04-03 20:29 ` [U-Boot] [PATCH v2 4/6] efi_loader: correct types for EFI_LOADED_IMAGE_PROTOCOL Heinrich Schuchardt
2018-04-03 20:29 ` [U-Boot] [PATCH v2 5/6] efi_loader: new functions to print loaded image information Heinrich Schuchardt
2018-04-04 9:38 ` Alexander Graf [this message]
2018-04-03 20:29 ` [U-Boot] [PATCH v2 6/6] arm: print information about loaded UEFI images Heinrich Schuchardt
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-all 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=4161780b-6a54-2ca7-7699-bae09f1a4573@suse.de \
--to=agraf@suse.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.