From: Christoph Hellwig <hch@infradead.org>
To: "David F." <df7729@gmail.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
linux-ide@vger.kernel.org, linux-nvme@lists.infradead.org,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: When will Linux support new RAID controllers
Date: Fri, 10 Nov 2017 05:19:37 -0800 [thread overview]
Message-ID: <20171110131937.GA26181@infradead.org> (raw)
In-Reply-To: <CAGRSmLs-Hr+FFfa4_29kidEeL2d7b+cEP6u1OkOUoYW6Cm15BA@mail.gmail.com>
On Thu, Nov 09, 2017 at 10:24:54AM -0800, David F. wrote:
> It seems that Linux will not see any HD on Intel's 100 Series or newer
> chipsets (Z170, etc.) when in RAID mode. (typically these systems
> have M2 NVMe devices ). This is problematic when wanting to use Linux
> on the system without having to disable RAID and when on their with
> Windows. Maybe not a linux-raid issue, but is Linux RAID issue
> within the kernel device support.
Dan (on Cc) posted some patches to support the awkwared so called
"RAID" mode (it really should be Intel landgrab mode) in the client
chipsets more than a year ago.
It needed a bit of a rework to be present as a fake PCIe root port
instead of the platform driver magic, so I wonder what happened to
it - Dan any chance to get back to it?
next parent reply other threads:[~2017-11-10 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGRSmLs-Hr+FFfa4_29kidEeL2d7b+cEP6u1OkOUoYW6Cm15BA@mail.gmail.com>
2017-11-10 13:19 ` Christoph Hellwig [this message]
2017-11-10 13:31 ` When will Linux support new RAID controllers Dennis Mungai
2017-11-10 19:06 ` David F.
2017-12-05 2:01 ` David F.
2017-12-07 0:00 ` Christoph Hellwig
2017-12-07 14:16 ` Alan Cox
2017-12-07 14:18 ` Dennis Mungai
2017-12-13 20:20 ` David F.
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=20171110131937.GA26181@infradead.org \
--to=hch@infradead.org \
--cc=dan.j.williams@intel.com \
--cc=df7729@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-raid@vger.kernel.org \
/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