public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>, ayushdevel1325@gmail.com
Cc: "Bret Barkelew" <Bret.Barkelew@microsoft.com>,
	"Nate DeSimone" <nathaniel.l.desimone@intel.com>,
	"Marvin Häuser" <mhaeuser@posteo.de>
Subject: Re: [edk2-devel] Applying for GSoC 2022: Add Rust Support to EDK II
Date: Wed, 6 Apr 2022 21:15:28 +0100	[thread overview]
Message-ID: <CAKbZUD0z81tcM7bpEqnvZNjzR=PNX8kOVqJ8-+D7=Ks7E12DfA@mail.gmail.com> (raw)
In-Reply-To: <CA+Yfj7s7cMbDDz0CMEb8hr4e5RFWw-RTVgcXqZrah=v3xQjKEg@mail.gmail.com>

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

Hi Ayush!

I had a decent look at your proposal, and I have some questions (note that
you can always re-submit proposals until April 19th):

1) How are you planning to reconcile the cargo build system with EDK2's
build system?

2) If you go ahead with cargo, will the new Rust code require a lot of tiny
crates? I'm personally not very enthusiastic about having lots of
dependencies all over the place,
especially somewhere Tianocore doesn't control. I've seen Rust crates that
were integrated into an operating system (
https://fuchsia.googlesource.com/fuchsia/+/refs/heads/main/third_party/rust_crates/
),
where they essentially maintain their own versions of the crate, with the
"proper" build system that the project uses.

3) How much of std are you going to implement? Note that traditionally,
EDK2, like a lot of this firmware/kernel/bootloader code, doesn't actually
implement much of the standard library (and that's the reasoning behind
edk2-libc).

4) Do you have any idea of what DXE driver you're going to implement? Do
you have any experience writing drivers?

5) Any plans for generation of C <-> Rust bindings? Does
https://github.com/rust-lang/rust-bindgen work out of the box?

Best regards,
Pedro

On Mon, Apr 4, 2022 at 6:18 PM Ayush Singh <ayushdevel1325@gmail.com> wrote:

> Hello everyone, I am a 2nd-year University Student from India. I am
> interested in applying for adding Rust support to EDK2. I have already
> introduced myself to the mailing list earlier
> (https://edk2.groups.io/g/devel/message/87637) and have even submitted
> some patches for the edkii-rust branch in edk2-staging (which were not
> merged since that branch seems to be abandoned now).
> - https://edk2.groups.io/g/devel/message/87753
> - https://edk2.groups.io/g/devel/message/87754
> - https://edk2.groups.io/g/devel/message/87755
> - https://edk2.groups.io/g/devel/message/87756
>
> Anyway, since no mentor has been listed for this project, I was
> wondering who should I discuss the proposal with? Normally, I think
> one is supposed to discuss the proposal details with a mentor in form
> of a google doc or something before submitting an application. So
> should I directly start by submitting a proposal through the GSoC
> application portal? Or is there someone I should contact first?
>
> Ayush Singh
>
>
> 
>
>
>

-- 
Pedro Falcato

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

  reply	other threads:[~2022-04-06 20:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 17:18 Applying for GSoC 2022: Add Rust Support to EDK II Ayush Singh
2022-04-06 20:15 ` Pedro Falcato [this message]
2022-04-07 12:01   ` [edk2-devel] " Ayush Singh
2022-04-07 21:03 ` Nate DeSimone
2022-04-08 12:41   ` Ayush Singh
2022-04-14  1:00     ` Nate DeSimone
2022-04-16 18:10       ` Ayush Singh

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='CAKbZUD0z81tcM7bpEqnvZNjzR=PNX8kOVqJ8-+D7=Ks7E12DfA@mail.gmail.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