From: "Wu, Hao A" <hao.a.wu@intel.com>
To: david moheban <moheban79@gmail.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Non-EDK Dependent NVME driver possible?
Date: Fri, 9 Mar 2018 07:57:10 +0000 [thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A0931D6531B@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CADxnD1zoPSZJyHrR=o9ezMZU34pmiTgsG4AioRcJ+w2ssKupuw@mail.gmail.com>
Hello,
Not sure about your actual using scenario.
But just taking the fact that the NvmeDxe driver depends on the existence
of PciIoProtocol, I think merely recompiling the driver will not work in
other platforms.
Best Regards,
Hao Wu
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of david
> moheban
> Sent: Sunday, March 04, 2018 4:16 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] Non-EDK Dependent NVME driver possible?
>
> Hi,
>
> Was wondering if that Nvmedxe driver could be recompiled with out the Edk2
> dependencies such that one could port it to another non-uefi platform?
>
> Thank you.
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2018-03-09 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 20:16 Non-EDK Dependent NVME driver possible? david moheban
2018-03-09 7:57 ` Wu, Hao A [this message]
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=B80AF82E9BFB8E4FBD8C89DA810C6A0931D6531B@SHSMSX104.ccr.corp.intel.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