[nvmewin] Amy way to avoid loading inbox NVMe driver in WINPE

[Abhijit Khande]

Hi Ray,

Yes its correct, but Microsoft (MS) NVMe driver is part of WinPE image
(Inbox Driver) and it gets loaded automatically (class/sub class matches
with MS NVMe inf).
When we reach to driver load screen NVMe stack will be build up, as MS NVMe
driver is already loaded.

After this we can load our driver, but I want to check can we avoid the
loading of the MS driver in first place?

Thanks,
Abhijit.


On Tue, Aug 4, 2015 at 1:40 AM, Robles, Raymond C <
raymond.c.robles at intel.com> wrote:

> Hi Abhijit,
>
>
>
> Understood. And the process I outline below is exactly for that. To load a
> third party driver during the OS install (via the “Load Drivers” option).
> If you do not select this option during the OS install, the MS inbox driver
> will claim the NVMe device. But if you load a driver during the OS install,
> for example our OFA driver, then the OFA driver will claim the NVMe device.
>
>
>
> Thanks,
>
> Ray
>
>
>
> *From:* Abhijit Khande [mailto:abhijit.khande at gmail.com]
> *Sent:* Monday, August 03, 2015 11:03 AM
> *To:* Robles, Raymond C
> *Cc:* nvmewin
> *Subject:* Re: [nvmewin] Amy way to avoid loading inbox NVMe driver in
> WINPE
>
>
>
> Hi Ray,
>
>
>
> Thanks for this data. But I want to avoid loading inbox NVMe driver
> (StorNvme.sys) while OS installation in WINPE.
>
> Currently if we boot in WINPE during OS installation inbox NVMe gets
> loaded and claim NVMe drives. This I want to avoid.
>
>
>
> I want to avoid loading inbox NVMe and load our open-source driver and
> claim the NVMe devices
>
>
>
> Thanks,
>
> Abhijit
>
>
>
>
>
>
>
> On Mon, Aug 3, 2015 at 2:12 AM, Robles, Raymond C <
> raymond.c.robles at intel.com> wrote:
>
> Hi Abhijit,
>
>
>
> Normally, when installing a Windows OS, there is an option to “load a
> driver” just before kicking off the install (on the same page as the disk
> partition layout). It is here that you could specify your desired driver,
> vs. the MS inbox driver, to load and run during an install. This was often
> referred to as the “F6 Install”.
>
>
>
> However, I’ve never tried this with WinPE. It may be worth investigating.
>
>
>
> Anyone else tried an “F6 Install” on WinPE?
>
>
>
> Thanks,
>
> Ray Robles
>
>
>
> *From:* nvmewin-bounces at lists.openfabrics.org [mailto:
> nvmewin-bounces at lists.openfabrics.org] *On Behalf Of *Abhijit Khande
> *Sent:* Thursday, July 30, 2015 6:57 PM
> *To:* nvmewin
> *Subject:* [nvmewin] Amy way to avoid loading inbox NVMe driver in WINPE
>
>
>
> Hi All,
>
>
>
> Is there any way to avoid loading inbox NVMe driver in WINPE during OS
> installation?
>
> Currently after booting in WINPE the class/sub-class code matched and
> inbox NVMme claims the device and PDOs gets exposesed  to class driver.
>
>
>
> Any way to avoid this stack getting buildup using by inbox driver and load
> our driver.
>
>
>
> Thanks,
>
> AK
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150804/c4556364/attachment.html>