Skip to content

EFI Shell Interface: CurDir Functions #1740

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

RenTrieu
Copy link
Contributor

This PR implements the wrappers for the GetCurDir and SetCurDir EFI Shell Protocol functions as part of the effort to address #448 .

Checklist

  • GetCurDir
  • SetCurDir

@RenTrieu RenTrieu mentioned this pull request Aug 11, 2025
45 tasks
@@ -2,12 +2,141 @@

//! EFI Shell Protocol v2.2

use crate::proto::unsafe_protocol;
#![cfg(feature = "alloc")]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For module-wide restrictions, we prefer:

#[cfg(feature = "alloc")]
mod shell;

on the upper level instead.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also it doesn't look to me that set_dir and get_dir need alloc at all

/// * `Some(Vec<env_names>)` - Vector of environment variable names
/// * `None` - Environment variable doesn't exist
#[must_use]
pub fn get_env<'a>(&'a self, name: Option<&CStr16>) -> Option<Vec<&'a CStr16>> {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think this accidentally hit the PR.? should be part of #1679 ?

This commit implements wrappers for the following EFI Shell Protocol
functions: set_cur_dir() and get_cur_dir().
This commit includes tests for the following EFI Shell Protocol functions:
get_cur_dir() and set_cur_dir().
@RenTrieu RenTrieu force-pushed the enhancement/efi_shell_interface_cur_dir branch from 4bef474 to 873e382 Compare August 12, 2025 15:29
@RenTrieu
Copy link
Contributor Author

Hi Philipp. Thanks for catching these! It looks like when rebasing the commits, although I removed references to the other PR from the commit messages I neglected to do so from the code in all but the most recent commit. I've addressed it now and will also do so shortly for #1679.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants