From: "Andrew Fish" <afish@apple.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>, pedro.falcato@gmail.com
Cc: Nate DeSimone <nathaniel.l.desimone@intel.com>
Subject: Re: [edk2-devel] GSoC 2021 (MinPlatform, Ext2, ACPICA, etc)
Date: Sun, 04 Apr 2021 08:33:15 -0700 [thread overview]
Message-ID: <08EE6FDA-81FB-4825-8E92-2C3304335917@apple.com> (raw)
In-Reply-To: <19876.1617533421134769104@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1925 bytes --]
> On Apr 4, 2021, at 3:50 AM, Pedro Falcato <pedro.falcato@gmail.com> wrote:
>
> Hi,
>
> Sounds 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 ideas 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 stretch goal is certainly the way to go.
>
Pedro,
Just an idea but but you could have a milestone to feature complete of the driver, and have a milestone to develop a test strategy, and test suite to validate the driver. Documentation could also be a milestone. For example I’ve worked on some proprietary EFI File System drivers (HFS+, apfs) 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 sure the driver gracefully fails in these cases. The test cases don’t 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 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 started with a made-up file system. The Microsoft file system team rejected this as it turns out testing file systems for all the possible end cases, across the range of produces and consumers is very very complicated. Microsoft ended up contributing FAT32 to EFI so that another new 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.
Thanks,
Andrew Fish
> Thanks,
> Pedro
>
[-- Attachment #2: Type: text/html, Size: 2644 bytes --]
next prev parent reply other threads:[~2021-04-04 15:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 13:07 [edk2-devel] GSoC 2021 (MinPlatform, Ext2, ACPICA, etc) pedro.falcato
2021-03-13 0:51 ` Andrew Fish
2021-03-13 17:01 ` Pedro Falcato
2021-03-16 0:25 ` Nate DeSimone
2021-03-23 14:16 ` Pedro Falcato
2021-03-28 22:31 ` Nate DeSimone
2021-03-28 22:42 ` Bret Barkelew
2021-03-31 20:45 ` Pedro Falcato
2021-03-31 20:43 ` Pedro Falcato
2021-03-31 23:13 ` Nate DeSimone
2021-04-04 10:50 ` Pedro Falcato
2021-04-04 15:33 ` Andrew Fish [this message]
2021-04-06 7:24 ` Nate DeSimone
2021-04-06 18:51 ` Pedro Falcato
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=08EE6FDA-81FB-4825-8E92-2C3304335917@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