From: ianb@mellanox.com (Ian Bakshan)
Subject: NVMe Generic Devices Linux x Windows
Date: Sun, 20 Dec 2015 10:28:39 +0200 [thread overview]
Message-ID: <567666B7.10902@mellanox.com> (raw)
In-Reply-To: <CAMjVwgQ+WicdTLjXb5Xa70XC+BnQdvyob+iGhjBt_t3Z9bw=dA@mail.gmail.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
next prev parent reply other threads:[~2015-12-20 8:28 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 [this message]
2015-12-20 19:02 ` Angelo Brito
2015-12-23 23:26 ` J Freyensee
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=567666B7.10902@mellanox.com \
--to=ianb@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.