linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Jens Axboe <axboe@kernel.dk>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] ahci: Add Intel Emmitsburg PCH RAID PCI IDs
Date: Mon, 23 Nov 2020 12:51:14 +0000	[thread overview]
Message-ID: <20201123125114.GA4264@infradead.org> (raw)
In-Reply-To: <20201123122820.GD2495@lahna.fi.intel.com>

On Mon, Nov 23, 2020 at 02:28:20PM +0200, Mika Westerberg wrote:
> On Mon, Nov 23, 2020 at 11:38:01AM +0000, Christoph Hellwig wrote:
> > The point is: these AHCI controllers do not support RAID in form
> > despite the confusing naming.
> 
> Are you sure?
> 
> I looked at the Emmitsburg data sheet and it actually seems to support
> some sort of RAID but it requires some special Rapid Storage Technology
> [1] drivers from Intel. Probably the idea is that when in "RAID mode"
> the thing, as AHCI spec says, does not announce itself to be AHCI
> compliant which makes Windows inbox AHCI driver to not to load, and this
> allows the Intel propriatery driver to load that then takes advantage of
> this somehow.

Yes, and that is purely (badly implemented) software RAID.

  reply	other threads:[~2020-11-23 13:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 10:43 [PATCH] ahci: Add Intel Emmitsburg PCH RAID PCI IDs Mika Westerberg
2020-11-19 16:50 ` Christoph Hellwig
2020-11-20 10:53   ` Mika Westerberg
2020-11-23 10:09     ` Christoph Hellwig
2020-11-23 11:26       ` Mika Westerberg
2020-11-23 11:38         ` Christoph Hellwig
2020-11-23 12:28           ` Mika Westerberg
2020-11-23 12:51             ` Christoph Hellwig [this message]
2020-11-25 14:44               ` Mika Westerberg
2022-04-02  0:43           ` Williams, Dan J
2020-12-16 12:34 ` Mika Westerberg

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=20201123125114.GA4264@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=linux-ide@vger.kernel.org \
    --cc=mika.westerberg@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;
as well as URLs for NNTP newsgroup(s).