public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Andrew Fish" <afish@apple.com>
To: devel@edk2.groups.io, tim.lewis@insyde.com
Subject: Re: [edk2-devel] Mappings and StdLib
Date: Wed, 04 Sep 2019 17:35:16 -0700	[thread overview]
Message-ID: <EEE09658-B8AC-44F5-BFC2-594937872E28@apple.com> (raw)
In-Reply-To: <01d101d5637e$e80098c0$b801ca40$@insyde.com>

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

Tim,

I don't know about the plans with the StdLib, but I do remember a long time ago with the old shell there was a protocol that let you translate volume names (mappings) into handles and device paths. 

So you could write a simple library that has 2 styles of APIs:
1) Handle + FilePath in Shell mapping with Volume Name out
2) Shell file path with mapping Volume names in and Simple File System handle Out with the file path
	a) A device path out version of this is also useful

You can make the lib just error return if the Shell protocol does not exist so you don't make it a requirement. The caller handles that failure as the current working volume/directory case. 

Thanks,

Andrew Fish

> On Sep 4, 2019, at 5:14 PM, Tim Lewis <tim.lewis@insyde.com> wrote:
> 
> Following up on my last e-mail, I guess I had the wrong assumption: there doesn’t appear to be a way to resolve mappings within StdLib.
>
> Are there any plans here?
>
> Thanks,
>
> Tim
> 


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

  reply	other threads:[~2019-09-05  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05  0:14 Mappings and StdLib Tim Lewis
2019-09-05  0:35 ` Andrew Fish [this message]
2019-09-05 17:25   ` [edk2-devel] " Tim Lewis
     [not found] <15C19AC418D00FDA.11246@groups.io>
2019-09-05 20:06 ` Tim Lewis

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=EEE09658-B8AC-44F5-BFC2-594937872E28@apple.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