From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from rn-mailsvcp-ppex-lapp15.apple.com (rn-mailsvcp-ppex-lapp15.apple.com [17.179.253.34]) by mx.groups.io with SMTP id smtpd.web09.1020.1618509368736393008 for ; Thu, 15 Apr 2021 10:56:08 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@apple.com header.s=20180706 header.b=mj3fpvV1; spf=pass (domain: apple.com, ip: 17.179.253.34, mailfrom: afish@apple.com) Received: from pps.filterd (rn-mailsvcp-ppex-lapp15.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp15.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 13FHn05g029924; Thu, 15 Apr 2021 10:56:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=3ZzcgNkKuHqVIrOVAPpKtOuV1ZwzuPN82pprl4EWAaY=; b=mj3fpvV1MFjbj/+nH3AxqU/ZqzcZ/ldkmejcFVoyop8Ay4yu0l/7Qil/gSjSe0BZOStK QXPkwE3oUnrCKxL0cvBhG3+8SwKclpNZVHd3dNEMVR8YNfFPOZWPn6QktJcGt/O9waDs 7OsYqhezclZ+TUy/VD2CgxvoGOGd/kESY72txHShJ0Qb4hJzSZo3OFdJ9/oaJr6F2kb4 p0ET2HaciwJO0o35bR7LXvFDOyQgytxJHqVd0qJ/qVvPkZX5HBEPx8QjNu2IU03IgPzJ vEIMIn3GpKy7LalFB+nYj5iD/B+mTZMoGbGiTR6aDMaiRGEATlPIdztMCMSVSG6cD5L+ vw== Received: from rn-mailsvcp-mta-lapp01.rno.apple.com (rn-mailsvcp-mta-lapp01.rno.apple.com [10.225.203.149]) by rn-mailsvcp-ppex-lapp15.rno.apple.com with ESMTP id 37u9kda1ds-4 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 15 Apr 2021 10:56:08 -0700 Received: from rn-mailsvcp-mmp-lapp03.rno.apple.com (rn-mailsvcp-mmp-lapp03.rno.apple.com [17.179.253.16]) by rn-mailsvcp-mta-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPS id <0QRM00K489TJ5M60@rn-mailsvcp-mta-lapp01.rno.apple.com>; Thu, 15 Apr 2021 10:56:07 -0700 (PDT) Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp03.rno.apple.com by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) id <0QRM007009OBGL00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Thu, 15 Apr 2021 10:56:07 -0700 (PDT) X-Va-A: X-Va-T-CD: b382b2f65421aaf8aca7767de12e8967 X-Va-E-CD: 159fb9faa11ba7bb0780bb63bcc1cd33 X-Va-R-CD: 59aa2b777059a2aba31e914a9901c5bd X-Va-CD: 0 X-Va-ID: ec41e6cb-2296-4243-a0fc-4ef5df71bc2a X-V-A: X-V-T-CD: b382b2f65421aaf8aca7767de12e8967 X-V-E-CD: 159fb9faa11ba7bb0780bb63bcc1cd33 X-V-R-CD: 59aa2b777059a2aba31e914a9901c5bd X-V-CD: 0 X-V-ID: 4a1c2bb5-7d61-4117-a949-7da7e2631599 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391,18.0.761 definitions=2021-04-15_09:2021-04-15,2021-04-15 signatures=0 Received: from [17.235.1.165] (unknown [17.235.1.165]) by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPSA id <0QRM00DTD9TIF500@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Thu, 15 Apr 2021 10:56:07 -0700 (PDT) From: "Andrew Fish" Message-id: MIME-version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.1\)) Subject: Re: [edk2-devel] [EDK2 / UEFI]: Support for flashing ubi-volume using fastboot Date: Thu, 15 Apr 2021 10:56:06 -0700 In-reply-to: Cc: Laszlo Ersek , edk2-devel-groups-io , Michael Brown , edk2-devel To: Pintu Agarwal References: <2ac07694-85ff-d6f2-6d02-cc33914d4df5@ipxe.org> <59e74e6a-16f5-3603-72b3-de7abe69664e@redhat.com> X-Mailer: Apple Mail (2.3654.20.0.2.1) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391,18.0.761 definitions=2021-04-15_09:2021-04-15,2021-04-15 signatures=0 Content-type: multipart/alternative; boundary="Apple-Mail=_38940C38-9833-416C-B70C-0221116E496D" --Apple-Mail=_38940C38-9833-416C-B70C-0221116E496D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Apr 15, 2021, at 10:47 AM, Pintu Agarwal = wrote: >=20 > On Thu, 15 Apr 2021 at 16:30, Laszlo Ersek > wrote: >>=20 >> 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. >>>>=20 >>>> The UEFI Shell has volume names, but that is a construct produced = by >>>> the UEFI Shell. >>>=20 >>> The filesystem label (if any) also gets exposed via = EFI_FILE_SYSTEM_INFO >>> in the VolumeLabel field, independently of the UEFI shell. >>=20 >> Also in "EFI_FILE_SYSTEM_VOLUME_LABEL.VolumeLabel". >>=20 >> (This is just a side comment, because I believe Pintu may not need >> filesystem-level access (as in, SimpleFs).) >>=20 >=20 > Hi All, >=20 > Thank you so much for your reply so far. >=20 > 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? >=20 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 =E2=80=9CDOS like=E2=80=9D syntax FilePath.=20 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.=20 Thanks, Andrew Fish > If there are some references available then it will be good to follow. >=20 > Thanks, > Pintu --Apple-Mail=_38940C38-9833-416C-B70C-0221116E496D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

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> 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 = =E2=80=9CDOS like=E2=80=9D 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

= --Apple-Mail=_38940C38-9833-416C-B70C-0221116E496D--