public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Andrew Fish" <afish@apple.com>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
	edk2-devel-groups-io <devel@edk2.groups.io>,
	Michael Brown <mcb30@ipxe.org>,
	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 10:56:06 -0700	[thread overview]
Message-ID: <B6025E65-29CF-4D56-859D-E75F80BD3B7E@apple.com> (raw)
In-Reply-To: <CAOuPNLhR=JujAROgh8nH=+YaLJQfeAXFdEdYjVU-gZ5vN6kqkQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]



> On Apr 15, 2021, at 10:47 AM, Pintu Agarwal <pintu.ping@gmail.com> wrote:
> 
> On Thu, 15 Apr 2021 at 16:30, Laszlo Ersek <lersek@redhat.com <mailto: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?
> 

Pintu,

Are you writing an UEFI Shell application or an EFI Application? The UEFI Shell produces extra APIs that abstracts the concept of volume names with a “DOS like” syntax <volumeName:>FilePath. 

In EFI there is no unified system file system API. Each mounted volume produces the same file system API and the root directory is the root of that volume. So the 1st thing you have to do is find the correct file system protocol (API) that matches your volume. As others have mentioned you can query that file system protocol (API) for the volume name, but non of the file system APIs take that volume name as input. That was the point I was trying to make, but sorry I did not give enough detail. 

Thanks,

Andrew Fish

> If there are some references available then it will be good to follow.
> 
> Thanks,
> Pintu


[-- Attachment #2: Type: text/html, Size: 11821 bytes --]

      reply	other threads:[~2021-04-15 17:56 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
2021-04-15 17:56         ` Andrew Fish [this message]

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=B6025E65-29CF-4D56-859D-E75F80BD3B7E@apple.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