From: Pintu Agarwal <pintu.ping@gmail.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: devel@edk2.groups.io, mcb30@ipxe.org, afish@apple.com,
edk2-devel <edk2-devel@lists.01.org>
Subject: Re: [edk2-devel] [EDK2 / UEFI]: Support for flashing ubi-volume using fastboot
Date: Thu, 15 Apr 2021 23:17:52 +0530 [thread overview]
Message-ID: <CAOuPNLhR=JujAROgh8nH=+YaLJQfeAXFdEdYjVU-gZ5vN6kqkQ@mail.gmail.com> (raw)
In-Reply-To: <59e74e6a-16f5-3603-72b3-de7abe69664e@redhat.com>
On Thu, 15 Apr 2021 at 16:30, Laszlo Ersek <lersek@redhat.com> wrote:
>
> On 04/14/21 21:41, Michael Brown wrote:
> > On 14/04/2021 20:34, Andrew Fish via groups.io wrote:
> >> EFI does not have a concept of Volume names, EFI has a concept of
> >> EFI_HANDLEs that contain device paths that indentify the volume.
> >>
> >> The UEFI Shell has volume names, but that is a construct produced by
> >> the UEFI Shell.
> >
> > The filesystem label (if any) also gets exposed via EFI_FILE_SYSTEM_INFO
> > in the VolumeLabel field, independently of the UEFI shell.
>
> Also in "EFI_FILE_SYSTEM_VOLUME_LABEL.VolumeLabel".
>
> (This is just a side comment, because I believe Pintu may not need
> filesystem-level access (as in, SimpleFs).)
>
Hi All,
Thank you so much for your reply so far.
Sorry, I am new to UEFI so I think I couldn't quite understand it clearly.
Is it possible to explain with an example about how to implement
volume concept in UEFI using the EDK2 application?
If there are some references available then it will be good to follow.
Thanks,
Pintu
next prev parent reply other threads:[~2021-04-15 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 18:12 [EDK2 / UEFI]: Support for flashing ubi-volume using fastboot Pintu Agarwal
2021-04-14 19:34 ` [edk2-devel] " Andrew Fish
2021-04-14 19:41 ` Michael Brown
2021-04-15 11:00 ` Laszlo Ersek
2021-04-15 17:47 ` Pintu Agarwal [this message]
2021-04-15 17:56 ` Andrew Fish
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-list 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='CAOuPNLhR=JujAROgh8nH=+YaLJQfeAXFdEdYjVU-gZ5vN6kqkQ@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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