Nicholas Bishop

Here's how you can do this with the existing API: ```rust use uefi::proto::console::gop::{GraphicsOutput, PixelFormat}; use uefi::table::boot::{BootServices, OpenProtocolAttributes, OpenProtocolParams, SearchType}; use uefi::{Handle, Identify, Result}; pub fn gop_test(image: Handle, bt: &BootServices) ->...

Thanks for looking into this. First question I have is: how common is firmware that is still on EFI

Some followup thoughts and questions: Taking another look at `EFI_BOOT_SERVICES.UninstallProtocolInterface` in the spec, I noticed this piece: > The caller is responsible for ensuring that there are no references to...

I think we can call this one done now. We've made some good improvements in the protocol interface that should help keep things sound, although to a certain extent we'll...

Lgtm! See https://github.com/rust-osdev/uefi-rs/issues/494 for the CI issue, once that's resolved we can re-run the CI on this and merge.

I'm not seeing quite the same thing as you with the builtin x86_64-unknown-uefi target. I do get what seems to be a valid pdb file generated under the `deps` directory....

This crate seems like a similar idea: https://docs.rs/fake-enum/latest/fake_enum/

I just did my first release, wrote up some notes on the process here: https://github.com/rust-osdev/uefi-rs/issues/340#issuecomment-1013563793

I can see some pros and cons of both options, but I'm leaning towards the main repo because it's easier to keep stuff in sync -- e.g. if an API...

Closing since there haven't been any updates in a while. If you are still running into the issue please feel free to reopen.