Hi Pedro, These ideas have been discussed. These are all valuable and would be required to use Rust in PEI, DXE, and SMM environments as part of system firmware images. However, there is

Hi Ayush, Since this is a fork of the rust project, I would recommend following the branch naming convention used by other PRs in the rust project. Thanks, Mike

Right. I had no idea that you were going to go for std support in your project. This makes me like your project much less. I thought you were going to go the way of linux, where they do not use std

Hi Mike. What should be the naming scheme of the branch/s? I think you already had some in mind to handle the development workflow. Ayush Singh

Hi Yao Jiewen. The currently implemented portions in the `std::sys` module would have to be the following: - [x] alloc - [x] GlobalAlloc: Currently uses hardcoded

Hi Ayush, I have created a fork in tianocore https://github.com/tianocore/rust I have added you and the EDK II Maintainers as collaborators on this repo. Please let me know if any permission

Hi Ayush Thanks for the great work. Would you please help me understand that how far we are between current [1] and final upstream to Rust? Is upstreaming a goal of GSoC project? Thank

Hi Pedro. To clarify the original email. The proposal is not to create a new repository to start Rust std work. Rather, it is to move all the per-existing work that I have done for

Hi Pedro. Bare Rust already works in UEFI. In fact, UEFI support for no_std Rust has been present upstream for a few years. However, as you might be able to guess, bare Rust without any

Hi, May I suggest you just port the bare rust language (no crates, no std) to EDK2? It seems far more plausible to expect people to use a cut down version with some bindings to the rest of the project

Hello everyone. In the previous email thread [1], I discussed the proposal to move Rust std work to edk2-staging and mentioned its potential problems. After some discussion with mentors, we arrived at

Hello, 1. I checked that and you are right. It will invoke callback functions when PPIs are already installed. I removed unnecessary function calls in v3 patch. 2. Moved in v3. 3. Corrected in v3. 4.

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3907 This change modifies AhciPei library to allow usage both EDKII_PCI_DEVICE_PPI and EDKII_PEI_ATA_AHCI_HOST_CONTROLLER_PPI to manage ATA HDD

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3907 This commit introduces EDKII_PCI_DEVICE_PPI. The purpose of this PPI is to provide a way of accessing PCI devices to drvice drivers such

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3907 The purpose of those changes is to introduce the way to enumerate and assign resources in PEI for the systems with more than one PCI root.

TianoCore Community Meeting - APAC/NAMO When: Thursday, August 18, 2022 7:30pm to 8:30pm (UTC-07:00) America/Los

TianoCore Community Meeting - EMEA / NAMO When: Thursday, August 18, 2022 9:00am to 10:00am (UTC-07:00) America/Los

Hi, The patch owner Pranav Madhu send two same patches in different branch. Does someone can help to fix it? Best Regards, Yanbo Huang

OK! Thanks a lot, It's great to receive your reply! So it's just a small but serious problem😂 Sorry to bother you! Thanks again!!! S, Ashraf Ali <ashraf.ali.s@...> 于2022年7月31日周日