public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ayush Singh" <ayushdevel1325@gmail.com>
To: "Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
	"Bret Barkelew" <Bret.Barkelew@microsoft.com>,
	"Marvin Häuser" <mhaeuser@posteo.de>,
	"Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] Applying for GSoC 2022: Add Rust Support to EDK II
Date: Fri, 8 Apr 2022 18:11:10 +0530	[thread overview]
Message-ID: <CA+Yfj7uX92HJrFouf0O4Sk=8J4C-yPoSY=OPAhoA+cnBL9qD1g@mail.gmail.com> (raw)
In-Reply-To: <MW4PR11MB5821EC8ECB0B5E4E2A5A1822CDE69@MW4PR11MB5821.namprd11.prod.outlook.com>

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

Hi Nate

Thanks for the response.

For the std implementation, I do have some idea how to go about
implementing it now. The most important thing I realized is that most of
the std isn't actually std. For example, std::collection, Vector, Box, Rc,
etc are all actually part of alloc and not std. The things that really are
part of std include threads, i/o, etc.

I have taken a look at some other people's projects who have tried
implementing libstd for other targets and it seems it is possible to write
an implementation without libc. It's just very difficult since in most OS
besides Linux, the syscall ABI is not stable enough and using libc is just
easier and recommended.

As for my earlier patches, Jiewen told me that edkii-rust branch is no
longer maintained and that they are now using a different uefi rust
implementation for their work.

I did also find that it will be possible to make the std with stable Rust
even though if internals use nightly, so that's cool. Some useful projects
about writing libstd for new platform that I found are below:
- https://github.com/betrusted-io/rust/tree/1.54.0.5
- https://github.com/japaric/steed

Ayush Singh

On Fri, 8 Apr, 2022, 2:33 am Desimone, Nathaniel L, <
nathaniel.l.desimone@intel.com> wrote:

> Hi Ayush,
>
> Great to meet you and welcome to the TianoCore project! Great to hear you
> are interested! Apologize for the tardiness in my response. Implementing
> Rust support sounds like a wonderful project and one that would really help
> advance the state of the art for UEFI firmware development! I am looking
> for someone with Rust experience that can help mentor this project. My
> usage of Rust at time of writing has not advanced very far beyond "Hello
> World." While I can give a great deal of knowledge and background on UEFI
> and EDK II, my ability to recommend how that be applied to a Rust binding
> is limited. However, I do know enough to suspect the vast majority of the
> work will be figuring out how to integrate the vast array of libraries that
> EDK II provides into a coherent and clean Rust binding. The one aspect of
> this project that I think will be interesting is figuring out is what to do
> about std:: in Rust. From what I have seen of the functionality there more
> or less assumes the existence of a libc implementation for the platform,
> which is not necessarily true for DXE and is absolutely not true for PEI. I
> would be interested in hearing your thought on how to handle that elegantly.
>
> I'm sorry that your patches haven't gotten much attention thus far. Once I
> find mentor(s) for the Rust project I'll make sure they pick those up and
> take a look at the work you have done thus far.
>
> Hope this helps and welcome to the project!
>
> With Best Regards,
> Nate
>
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Ayush Singh
> Sent: Monday, April 4, 2022 10:18 AM
> To: devel@edk2.groups.io
> Cc: Bret.Barkelew@microsoft.com; Desimone, Nathaniel L <
> nathaniel.l.desimone@intel.com>; mhaeuser@posteo.de
> Subject: [edk2-devel] Applying for GSoC 2022: Add Rust Support to EDK II
>
> 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
>
>
> 
>
>
>

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

  reply	other threads:[~2022-04-08 12:41 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 ` [edk2-devel] " Pedro Falcato
2022-04-07 12:01   ` Ayush Singh
2022-04-07 21:03 ` Nate DeSimone
2022-04-08 12:41   ` Ayush Singh [this message]
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='CA+Yfj7uX92HJrFouf0O4Sk=8J4C-yPoSY=OPAhoA+cnBL9qD1g@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