From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from rn-mailsvcp-ppex-lapp24.apple.com (rn-mailsvcp-ppex-lapp24.apple.com [17.179.253.38]) by mx.groups.io with SMTP id smtpd.web09.18810.1618428865123485321 for ; Wed, 14 Apr 2021 12:34:25 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@apple.com header.s=20180706 header.b=lLOB5VkC; spf=pass (domain: apple.com, ip: 17.179.253.38, mailfrom: afish@apple.com) Received: from pps.filterd (rn-mailsvcp-ppex-lapp24.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp24.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 13EJX9sn025392; Wed, 14 Apr 2021 12:34:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=20180706; bh=agk7gfFKP0gup2vAFrGb+D4zLZ4siw0CuPiD2dTsrn8=; b=lLOB5VkCXT6LO4xil/eyg/P7pLku+t7F/nypz4pxM4PTIhQvoI4tv1F7RfLXjlqw4nuP RCIDNCokb7aL9ID92HD/jpFTDniuYcuARVvZARHorUjTv8gbJop53cIet6l//956rYu7 cidQICpFIT7nQ6Voxnq9iWVaE5ZLALccF8ZMMcCqz/vVhY3i7zMJ3nsqynP9IJWGujCv E3/k83ILCMw9MCLLOg+HcrHsK+Xbe8E800b4MfMpHvImt/6AcLPwYLsBB0IcjhW9B2G4 cF2EY/6+tqOCNAZUV1hpukfhX1BiszRvrh0PDoe+tPau+p7jONQLL1xGg7GaOELihabz /w== Received: from rn-mailsvcp-mta-lapp03.rno.apple.com (rn-mailsvcp-mta-lapp03.rno.apple.com [10.225.203.151]) by rn-mailsvcp-ppex-lapp24.rno.apple.com with ESMTP id 37u9ma3rd4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 14 Apr 2021 12:34:24 -0700 Received: from rn-mailsvcp-mmp-lapp02.rno.apple.com (rn-mailsvcp-mmp-lapp02.rno.apple.com [17.179.253.15]) by rn-mailsvcp-mta-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPS id <0QRK00SQZJPC0XG0@rn-mailsvcp-mta-lapp03.rno.apple.com>; Wed, 14 Apr 2021 12:34:24 -0700 (PDT) Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp02.rno.apple.com by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) id <0QRK00200JORMO00@rn-mailsvcp-mmp-lapp02.rno.apple.com>; Wed, 14 Apr 2021 12:34:24 -0700 (PDT) X-Va-A: X-Va-T-CD: 2b624d38da897828d5044ea8e4d1f57b X-Va-E-CD: 159fb9faa11ba7bb0780bb63bcc1cd33 X-Va-R-CD: 59aa2b777059a2aba31e914a9901c5bd X-Va-CD: 0 X-Va-ID: 7f384005-6fab-42b4-bcf9-f4297a26f033 X-V-A: X-V-T-CD: 2b624d38da897828d5044ea8e4d1f57b X-V-E-CD: 159fb9faa11ba7bb0780bb63bcc1cd33 X-V-R-CD: 59aa2b777059a2aba31e914a9901c5bd X-V-CD: 0 X-V-ID: 308bba91-b65a-4f86-ad7b-c732cc00981b X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391,18.0.761 definitions=2021-04-14_10:2021-04-14,2021-04-14 signatures=0 Received: from [17.235.1.165] (unknown [17.235.1.165]) by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPSA id <0QRK00IGWJP7F900@rn-mailsvcp-mmp-lapp02.rno.apple.com>; Wed, 14 Apr 2021 12:34:23 -0700 (PDT) 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 From: "Andrew Fish" In-reply-to: Date: Wed, 14 Apr 2021 12:34:19 -0700 Cc: edk2-devel Message-id: References: To: devel@edk2.groups.io, pintu.ping@gmail.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-14_10:2021-04-14,2021-04-14 signatures=0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable > On Apr 14, 2021, at 11:12 AM, Pintu Agarwal wrote= : >=20 > Hi, >=20 > I am new to EDK2 and UEFI. > I am working on an ARM32 embedded Linux board that supports NAND and UBI= images. > I have several partitions in my system images, and some partitions > have sub-volumes. > I am looking for help on how to support flashing ubi-volumes directly > using the fastboot flash method. >=20 > I see that our EDK2 does not have a mechanism to flash ubi-volumes. > But the underlying UEFI code, have support for ubi-volume. > {{{ > UEFI Code flow: > ubi_flasher_write(...) > { > [...] > if (hdl->is_it_volume) { > result =3D ubi_flasher_vol_write(hdl); > if (result !=3D 0) > goto End; > } else { > result =3D ubi_flasher_ubi_write(hdl); > if (result !=3D 0) > goto End; > } > [...] > } > }}} >=20 > When I tried to invoke ubi_flasher_write from EDK2, by passing the > ubifs volume name, instead of PartitionName, it does not work (crash). >=20 EFI does not have a concept of Volume names, EFI has a concept of EFI_HAND= LEs that contain device paths that indentify the volume.=20 The UEFI Shell has volume names, but that is a construct produced by the U= EFI Shell.=20 Thanks, Andrew Fish > Thus I am wondering, what needs to done at EDK2 (and how) to invoke > this ubi volume write at uefi. > Or, is there some functionality missing at the UEFI layer itself ? >=20 > Please provide some suggestions on this. >=20 > Thanks, > Pintu >=20 >=20 >=20 >=20 >=20