public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Andrew Fish" <afish@apple.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>, pedro.falcato@gmail.com
Subject: Re: [edk2-devel] GSoC 2021 (MinPlatform, Ext2, ACPICA, etc)
Date: Fri, 12 Mar 2021 16:51:20 -0800	[thread overview]
Message-ID: <49D6FCF5-295B-4228-A625-257A3F25EE57@apple.com> (raw)
In-Reply-To: <CAKbZUD2G2XqJzZgHdY2oyYP_sJ8Sxj=jiSTosTvaNL96=WyY2w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]



> On Mar 12, 2021, at 5:07 AM, Pedro Falcato <pedro.falcato@gmail.com> wrote:
> 
> Hi everyone!
> 
> I'm Pedro Falcato, a student from FCT Nova in Lisbon, Portugal. I've gotten a bunch of experience over the years with C/C++, x86 in general and UEFI/ACPI with my hobby OS/kernel development, and I've got to say, I'm quite interested in some of the projects you've got here.
> 
> So, a few questions:
> 
> 1) What entails building a MinPlatform board port for any board whatsoever? I've seen Kaaira wants to do the Qemu port, I would love to do something like that but for the RPi or some real motherboard, but I fear it might be too difficult?
> 
> 2) How much knowledge of EFI firmware internals do you need? With my EFI bootloader development over the years I already have a firm hand on how the external-facing API looks like, but I have to say I haven't really read the parts of the spec that describe the driver and internal APIs, so to speak.
> 

Pedro,

Knowing UEFI is a really good baseline. Tianocore is UEFI + edk2 Build System + UEFI Platform initialization Specification [1],

There is some training here: [2]

Some of us also sit on the spec committees so you can usually get good quality answers to questions on the mailing list. 

[1] https://uefi.org/specifications

[2] https://github.com/tianocore/tianocore.github.io/wiki/UEFI-EDKII-Learning-Dev

Thanks,

Andrew Fish

> 3) Isn't there already an ACPICA port for UEFI environments? What stops us from going one step further and also build the rest of the "user-space" utilities?
> 
> 4) How's the status of the ext2 driver? How different do Tianocore filesystem implementations look from the standard-ish kernel interfaces you can see in Linux, *BSD, etc? I'm also quite interested in this one because I've written a read/write ext2 driver before, so the concepts are kind-of fresh in my head.
> 
> I hope you folks can answer my questions so I can figure out what project I want to work on! :)
> 
> Looking forward to working in Tianocore!
> 
> Thanks,
> Pedro Falcato
> 


[-- Attachment #2: Type: text/html, Size: 3599 bytes --]

  reply	other threads:[~2021-03-13  0:51 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 [this message]
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
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=49D6FCF5-295B-4228-A625-257A3F25EE57@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