From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: NVMe Generic Devices Linux x Windows
Date: Wed, 23 Dec 2015 15:26:21 -0800 [thread overview]
Message-ID: <1450913181.6363.38.camel@linux.intel.com> (raw)
In-Reply-To: <CAMjVwgTj6FJQD=y-JqDr_CO6OByGe540xxLiATm1oqWhJ5sBkQ@mail.gmail.com>
On Sun, 2015-12-20@16:02 -0300, Angelo Brito wrote:
> Thanks Ian.
> It is really a windows problem. The native driver version is too old.
There is an actively maintained open-source NVMe Windows driver you can
try and see if that works:
https://www.openfabrics.org/index.php/windows-nvm-express/nvm-express-s
ubversion-repos.html
>
>
> Regards,
> Angelo Silva Brito.
> B.S. in Computer Engineering - UFPE Brazil
> http://about.me/angelobrito
> _________________________________________________
>
>
> 2015-12-20 5:28 GMT-03:00 Ian Bakshan <ianb at mellanox.com>:
> > Hello Angelo,
> >
> > I recommend to open a support ticket to the Windows driver
> > provider.
> > In case this is a Windows built-in driver you need to open the
> > support
> > ticket at Microsoft Support Center.
> >
> > BR,
> > Ian
> >
> >
> > On 18/12/2015 21:17, Angelo Brito wrote:
> > >
> > > Hello All,
> > >
> > > I have a generic NVMe device that works perfectly on Linux but
> > > does
> > > not work on Windows. The device is recognized as a Default NVMe
> > > Controller with Microsoft as vendor but issue an error code 10:
> > > This
> > > device cannot start. I am aware that this is a generic error code
> > > and
> > > could mean any thing.
> > >
> > > I have started to debug from the device perspective and the Host
> > > CPU
> > > just writes the MSI configuration registers during startup. I use
> > > Altera?s PCIe Hard IP to implement the PCIe and my controller is
> > > hosted on FPGA. The NVMe controller was never started. Is it an
> > > expected behavior to work on Linux but not on windows?
> > > Someone can share any more leads to debug? Why windows doesn?t
> > > start my
> > > device?
> > >
> > >
> > > Regards,
> > > Angelo Silva Brito.
> > > B.S. in Computer Engineering - UFPE Brazil
> > > http://about.me/angelobrito
> > > _________________________________________________
> > >
> > > _______________________________________________
> > > Linux-nvme mailing list
> > > Linux-nvme at lists.infradead.org
> > > http://lists.infradead.org/mailman/listinfo/linux-nvme
> >
> >
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2015-12-23 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 19:17 NVMe Generic Devices Linux x Windows Angelo Brito
2015-12-20 8:28 ` Ian Bakshan
2015-12-20 19:02 ` Angelo Brito
2015-12-23 23:26 ` J Freyensee [this message]
2015-12-24 2:49 ` Angelo Brito
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-all 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=1450913181.6363.38.camel@linux.intel.com \
--to=james_p_freyensee@linux.intel.com \
/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