From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 2/7] cmd: efidebug: add devices command
Date: Wed, 23 Jan 2019 13:56:18 +0900 [thread overview]
Message-ID: <20190123045617.GG20286@linaro.org> (raw)
In-Reply-To: <aee7b3bf-d0a2-afe6-1fe7-8e97a9e96530@suse.de>
On Tue, Jan 22, 2019 at 10:19:35AM +0100, Alexander Graf wrote:
>
>
> On 22.01.19 02:38, AKASHI Takahiro wrote:
> > Alex,
> >
> > On Mon, Jan 21, 2019 at 02:34:43PM +0100, Alexander Graf wrote:
> >> On 01/21/2019 08:49 AM, AKASHI Takahiro wrote:
> >>> "devices" command prints all the uefi variables on the system.
> >>>
> >>> => efi devices
> >>> Scanning disk ahci_scsi.id0lun0...
> >>> Scanning disk ahci_scsi.id1lun0...
> >>> Found 4 disks
> >>> D
> >>> e
> >>> v Device Path
> >>
> >> Why the weird formatting of "Dev"?
> >
> > Good question :)
> > The format mimics a EDK2's shell.
> > The purpose is that we will be able to add some *narrow* data fields
> > later without spilling out a line length.
> >
> > But I admit that we don't have to do so because we have an enough width,
> > 16 digits, for ID (or address of efi object in this case).
> >
> > === From EDK2 UEFI Shell output ===
> > Shell> drivers
> > T D
> > D Y C I
> > e P F A
> > V VERSION E G G #D #C DRIVER NAME IMAGE NAME
> > == ======== = = = == == =================================== ==========
> > 6E 0000000A D - - 1 - Platform Console Management Driver ConPlatformDxe
>
> Ah, yes, in this output it makes sense. We don't have the table header
> size problem though, so let's please not pull that ugly header in :).
Okay.
I will also modify the code so that this field (address of efi_handle_t)
can be 32-bit or 64-bit wide.
-Takahiro Akashi
>
> Alex
next prev parent reply other threads:[~2019-01-23 4:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 7:49 [U-Boot] [PATCH v5 0/7] cmd: add efidebug for efi environment AKASHI Takahiro
2019-01-21 7:49 ` [U-Boot] [PATCH v5 1/7] cmd: add efidebug command AKASHI Takahiro
2019-01-21 13:07 ` Alexander Graf
2019-01-22 1:02 ` AKASHI Takahiro
2019-01-22 9:18 ` Alexander Graf
2019-01-23 4:47 ` AKASHI Takahiro
2019-01-23 9:52 ` Alexander Graf
2019-01-24 1:02 ` AKASHI Takahiro
2019-01-21 7:49 ` [U-Boot] [PATCH v5 2/7] cmd: efidebug: add devices command AKASHI Takahiro
2019-01-21 13:34 ` Alexander Graf
2019-01-22 1:38 ` AKASHI Takahiro
2019-01-22 9:19 ` Alexander Graf
2019-01-23 4:56 ` AKASHI Takahiro [this message]
2019-01-21 7:49 ` [U-Boot] [PATCH v5 3/7] cmd: efidebug: add drivers command AKASHI Takahiro
2019-01-21 7:49 ` [U-Boot] [PATCH v5 4/7] cmd: efidebug: add dh command AKASHI Takahiro
2019-01-21 7:49 ` [U-Boot] [PATCH v5 5/7] cmd: efidebug: add images command AKASHI Takahiro
2019-01-21 7:49 ` [U-Boot] [PATCH v5 6/7] cmd: efidebug: add memmap command AKASHI Takahiro
2019-01-21 13:39 ` Alexander Graf
2019-01-22 1:42 ` AKASHI Takahiro
2019-01-21 7:49 ` [U-Boot] [PATCH v5 7/7] cmd: env: add "-e" option for handling UEFI variables AKASHI Takahiro
2019-01-21 13:41 ` Alexander Graf
2019-01-22 3:06 ` AKASHI Takahiro
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=20190123045617.GG20286@linaro.org \
--to=takahiro.akashi@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox