From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) by mx.groups.io with SMTP id smtpd.web11.44082.1617550398631576751 for ; Sun, 04 Apr 2021 08:33:18 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@apple.com header.s=20180706 header.b=fHrphGi7; spf=pass (domain: apple.com, ip: 17.171.2.68, mailfrom: afish@apple.com) Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.42/8.16.0.42) with SMTP id 134FWeQD011577; Sun, 4 Apr 2021 08:33:17 -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=wEwpe2PGEoYni4r09uOni0fpZ5DUmv0EMJzOJkK/7x8=; b=fHrphGi7gUmLpEP2/lJzEZ3BVM+qDF4HpcYZVVtBoIQnWYA5h5hf6sBDkfNrHVbC2g+5 FFV0wWvnXOv15UT0oCtlhhYF0jpXCpoHgYQgWIsXBybbe9yM8ntnTQ5S4o9jL4xp5IhB l9aN+H90cn9OJM9HTZTomuB3UecWtoPUyrayKsQBtV5xfC9YU5zqjOhCuMzHdHU4TKlZ vWFDFSAv54stCJDitbDeq6Qk82gxSGT4lBtbF0yegMrtEIOEQDV1nxJFAlB7/L1wktDZ A8QA8RH7XCa4aRu62CEdMdK8cx4TXeKrkcsrKsaCvREcDA/4jVOoMH2+y9CtA4LOmSHc Lw== Received: from rn-mailsvcp-mta-lapp01.rno.apple.com (rn-mailsvcp-mta-lapp01.rno.apple.com [10.225.203.149]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 37q2qqxpbc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 04 Apr 2021 08:33:17 -0700 Received: from rn-mailsvcp-mmp-lapp04.rno.apple.com (rn-mailsvcp-mmp-lapp04.rno.apple.com [17.179.253.17]) 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 <0QR100T2TPVHB120@rn-mailsvcp-mta-lapp01.rno.apple.com>; Sun, 04 Apr 2021 08:33:17 -0700 (PDT) Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp04.rno.apple.com by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) id <0QR100200PEEML00@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Sun, 04 Apr 2021 08:33:17 -0700 (PDT) X-Va-A: X-Va-T-CD: 677289d23efd9e3153717a2cf58a2ef1 X-Va-E-CD: 73eb0a56594c48916ccd3c81ccd136f6 X-Va-R-CD: 678afdf0c7c9b62d74f4d4c649ecdaf0 X-Va-CD: 0 X-Va-ID: e68e3ad7-9cee-4976-886a-4c37aaf914aa X-V-A: X-V-T-CD: 677289d23efd9e3153717a2cf58a2ef1 X-V-E-CD: 73eb0a56594c48916ccd3c81ccd136f6 X-V-R-CD: 678afdf0c7c9b62d74f4d4c649ecdaf0 X-V-CD: 0 X-V-ID: b5cd062a-4d4c-4805-aaad-b6f17c177802 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369,18.0.761 definitions=2021-04-04_05:2021-04-01,2021-04-04 signatures=0 Received: from [17.235.19.121] (unknown [17.235.19.121]) by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPSA id <0QR100967PVFTY00@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Sun, 04 Apr 2021 08:33:16 -0700 (PDT) From: "Andrew Fish" Message-id: <08EE6FDA-81FB-4825-8E92-2C3304335917@apple.com> MIME-version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.1\)) Subject: Re: [edk2-devel] GSoC 2021 (MinPlatform, Ext2, ACPICA, etc) Date: Sun, 04 Apr 2021 08:33:15 -0700 In-reply-to: <19876.1617533421134769104@groups.io> Cc: Nate DeSimone To: edk2-devel-groups-io , pedro.falcato@gmail.com References: <19876.1617533421134769104@groups.io> X-Mailer: Apple Mail (2.3654.20.0.2.1) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369,18.0.761 definitions=2021-04-04_05:2021-04-01,2021-04-04 signatures=0 Content-type: multipart/alternative; boundary="Apple-Mail=_D59A28F2-CD5D-46C7-BEF1-3AA3B1417078" --Apple-Mail=_D59A28F2-CD5D-46C7-BEF1-3AA3B1417078 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Apr 4, 2021, at 3:50 AM, Pedro Falcato wrot= e: >=20 > Hi, >=20 > Sounds great! You may be right about that, although I believe I read som= ewhere that you need to set a milestone for each evaluation? If so, I'm out= of ideas as to what can be tangible enough to be a milestone; if not, spec= ifying a read-only driver as project's objective and having write support a= s a stretch goal is certainly the way to go. >=20 Pedro, Just an idea but but you could have a milestone to feature complete of th= e driver, and have a milestone to develop a test strategy, and test suite t= o validate the driver. Documentation could also be a milestone. For example= I=E2=80=99ve worked on some proprietary EFI File System drivers (HFS+, apf= s) and we chose not to implement certain features like compressed files. So= you would want to have good documentation about that and tests to make sur= e the driver gracefully fails in these cases. The test cases don=E2=80=99t = only need to be tests as you could create a file system disk image that you= could mount in OVMF that contains a lot of file system end case constructs= (max size file, links, etc.) to make testing easier. It is not just about = leaving a driver behind, but a driver that is easy to maintain and modify o= ver the years. For bonus points that would probably look good on your CV.= =20 Historical note: EFI did not start with the FAT32 file system as it requir= ed a license. EFI started with a made-up file system. The Microsoft file sy= stem team rejected this as it turns out testing file systems for all the po= ssible end cases, across the range of produces and consumers is very very c= omplicated. Microsoft ended up contributing FAT32 to EFI so that another ne= w file system would not end up in the world that needed to be validated. So= that is probably a good argument to invest in testing this new driver.=20 Thanks, Andrew Fish > Thanks, > Pedro >=20 --Apple-Mail=_D59A28F2-CD5D-46C7-BEF1-3AA3B1417078 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On Apr 4, 20= 21, at 3:50 AM, Pedro Falcato <pedro.falcato@gmail.com> wrote:

Hi,

Soun= ds great! You may be right about that, although I believe I read somewhere = that you need to set a milestone for each evaluation? If so, I'm out of ide= as as to what can be tangible enough to be a milestone; if not, specifying = a read-only driver as project's objective and having write support as a str= etch goal is certainly the way to go.


Pedro,

<= /div>
Just an idea but but you could have a milestone to feature comple= te  of the driver, and have a milestone to develop a test strategy, an= d test suite to validate the driver. Documentation could also be a mileston= e. For example I=E2=80=99ve worked on some proprietary EFI File System driv= ers (HFS+, apfs) and we chose not to implement certain features like compre= ssed files. So you would want to have good documentation about that and tes= ts to make sure the driver gracefully fails in these cases. The test cases = don=E2=80=99t only need to be tests as you could create a file system disk = image that you could mount in OVMF that contains a lot of file system end c= ase constructs (max size file, links, etc.) to make testing easier. It is n= ot just about leaving a driver behind, but a driver that is easy to maintai= n and modify over the years. For bonus points that would probably look good= on your CV. 

Historical note: EFI= did not start with the FAT32 file system as it required a license. EFI sta= rted with a made-up file system. The Microsoft file system team rejected th= is as it turns out testing file systems for all the possible end cases, acr= oss the range of produces and consumers is very very complicated. Microsoft= ended up contributing FAT32 to EFI so that another new file system would n= ot end up in the world that needed to be validated. So that is probably a g= ood argument to invest in testing this new driver. 

Thanks,

Andrew Fish
Tha= nks,
Pedro

--Apple-Mail=_D59A28F2-CD5D-46C7-BEF1-3AA3B1417078--