From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: Nate DeSimone <nathaniel.l.desimone@intel.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] GSoC 2021 (MinPlatform, Ext2, ACPICA, etc)
Date: Tue, 23 Mar 2021 07:16:50 -0700 [thread overview]
Message-ID: <15506.1616509010029055239@groups.io> (raw)
In-Reply-To: <MWHPR1101MB21600AE5EA3C75B0851A4B6DCD6B9@MWHPR1101MB2160.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
Hi Nate!
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 :)
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.
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: https://github.com/heatd/edk2-ext. 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.
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:
* 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.
* Is the read-only behaviour still the target?
Thanks,
Pedro Falcato
[-- Attachment #2: Type: text/html, Size: 1623 bytes --]
next prev parent reply other threads:[~2021-03-23 14:16 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 [this message]
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
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=15506.1616509010029055239@groups.io \
--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