From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: devel@edk2.groups.io, leif@nuviainc.com, michael.d.kinney@intel.com
Cc: "pedro.falcato@gmail.com" <pedro.falcato@gmail.com>
Subject: Re: [edk2-devel] GSOC 2021 EXT4 driver Project
Date: Fri, 11 Jun 2021 14:23:07 -0400 [thread overview]
Message-ID: <a55e0ef8-6d19-3f6a-9d63-680cdae07ef3@linux.microsoft.com> (raw)
In-Reply-To: <20210610175411.jqbn6s5yv7eukeqv@leviathan>
I had done some of the early work in moving content to
edk2-platforms/Features. Just wanted to add my support for maintaining
this as a vendor neutral feature there.
#4 in the options list is not really what AdvancedFeaturePkg intended
for, there's more details here -
https://github.com/tianocore/edk2-platforms/tree/master/Features/Intel#AdvancedFeaturePkg.
- Michael
On 6/10/2021 1:54 PM, Leif Lindholm wrote:
> edk2-platforms/Features/Ext4Pkg sounds good to me too.
>
> /
> Leif
>
> On Thu, Jun 10, 2021 at 17:38:17 +0000, Michael D Kinney wrote:
>> Hi Pedro,
>>
>> After thinking about this, I think I would prefer Option (4).
>>
>> The proposed landing zone would be a new Ext4Pkg in the edk2-platforms repository in the Features directory.
>>
>> edk2-platforms/Features/Intel/Ext4Pkg
>>
>> All the features in that directory and not specific to Intel. There are other email discussions about moving some of that content up a level, so an alternative path would be:
>>
>> edk2-platforms/Features/Ext4Pkg
>>
>> Best regards,
>>
>> Mike
>>
>>
>> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Pedro Falcato
>> Sent: Monday, May 24, 2021 12:27 PM
>> To: devel@edk2.groups.io
>> Subject: [edk2-devel] GSOC 2021 EXT4 driver Project
>>
>> Hi everyone,
>>
>> Me and my project have been selected for GSoC this year, under Michael Kinney and bret. Thank you for the opportunity to collaborate with you and improve Tianocore!
>> If anyone has any questions, please fire away :)
>> How do I get started? I'd like to find some easier tasks as to start trying out patch submission and generally programming in a firmware environment.
>> Also, I've been talking with my mentors and a relevant question to ask the mailing list is: Where should we put the EXT4 driver?
>> Michael said there are other filesystems in MdeModulePkg, but it might be getting too big and proposed the following options:
>>
>> 1) EXT4 in new package in edk2 repo as a peer to FatPkg.
>> 2) EXT4 in edk2 repo in MdeModulePkg
>> 3) EXT4 in edk2-platforms advanced feature package.
>> 4) EXT4 in edk2 advanced feature package
>>
>> As someone that's still learning how to navigate the project's tree(s), this is a bit over my head and so I'd like your opinion on the matter.
>> Also, I would love if someone could point me to some good reading material and/or examples of the package/build system, as I couldn't find documentation on those
>> and my previous experiment with Tianocore involved looking at FatPkg and mindlessly copying what it was doing.
>>
>> Thanks,
>>
>> Pedro
>>
>>
>>
>>
>>
>>
>
>
>
>
next prev parent reply other threads:[~2021-06-11 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 19:26 GSOC 2021 EXT4 driver Project Pedro Falcato
2021-05-24 20:26 ` [edk2-devel] " Michael D Kinney
2021-05-24 23:15 ` Michael Brown
2021-05-28 17:16 ` Pedro Falcato
2021-06-01 11:56 ` Michael Brown
2021-06-10 17:38 ` Michael D Kinney
2021-06-10 17:54 ` Leif Lindholm
2021-06-11 18:23 ` Michael Kubacki [this message]
2021-06-11 21:27 ` Michael D Kinney
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=a55e0ef8-6d19-3f6a-9d63-680cdae07ef3@linux.microsoft.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