Hi Nate!<br /><br />Sorry for taking so long to get back to you, I've been a bit busy and I'm not too used to so many emails in my inbox :)<br /><br />So, if I'm getting this right, essentially what is proposed in the MinPlatform board ports is to refactor the existing board code into an OpenBoardPkg that uses MinPlatform to reuse more generic code? I was thinking about getting a Raspberry Pi and doing the MinPlatform port for that, although honestly I'm not too inclined for that option anymore.<br /><br />Honestly, I'm looking more towards the ext2/4 drivers now. I've been poking a little at the build system and how the driver model is supposed to work and I think I more or less got the idea. Here's the link to my ext2 test repo, if you're curious: <a href="https://github.com/heatd/edk2-ext" target="_blank" rel="noopener">https://github.com/heatd/edk2-ext</a>. Note that it doesn't quite do anything right now, it's missing all sorts of features and testing and what's there is mostly driver model and build system boilerplate that was pieced together by looking at the UEFI spec and the FatPkg code, plus some of my own ext2 headers.<br /><br />With regards to ext4, yes, it sounds like the better option at the moment, although I'm not terribly familiar with it. I do have some questions though:<br /><br />
<ol>
<li>What are the standards for filesystem driver performance? Is a page/disk cache a necessity for the driver? I would assume the FS driver has some substancial footprint in the overall boot time.</li>
<li>Is the read-only behaviour still the target?</li>
</ol>
Thanks,<br />Pedro Falcato