Date: Wed, 10 Jun 2015 23:47:14 +0100
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: "linux" <linux@highpoint-tech.com>
Cc: <tj@kernel.org>, <linux-ide@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>
Subject: Re: Question about HighPoint RocketRAID 642L SCSI driver conflict
 with Linux AHCI driver
Message-ID: <20150610234714.76db2719@lxorguk.ukuu.org.uk>
In-Reply-To: <002a01d09e84$22be8f90$683baeb0$@highpoint-tech.com>
References: <002a01d09e84$22be8f90$683baeb0$@highpoint-tech.com>
Organization: Intel Corporation
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1312
Lines: 32

On Thu, 4 Jun 2015 13:05:49 +0800
"linux" <linux@highpoint-tech.com> wrote:

> Dear Tejun Heo,
> 
>   This is HighPoint Linux Team. We found Linux AHCI driver since kernel 3.16
> has added ID (0x06421103) to support RocketRAID 642L which is not what we
> expected. If we want to load HighPoint RR642L RAID version Linux SCSI
> driver, it becomes conflict each other. This affects our customers who need
> to use our RAID version driver stack.

If your stack existed in full open source form upstream we might be able
to add it the supported raid formats, which would make life even easier
for your customers.

>   Hence,  this is to ask Linux how to solve this conflict with AHCI driver?
> and why Linux wants to add RR642L ID (0x06421103) into AHCI driver? 

So that users can use the hardware with the standard kernel AHCI drivers
because they are best freely available and integrated driver available.

> Is there > any way to prevent this in the future?

Apart from having your customers reconfigure their kernel or carefully
set stuff up at boot time, no.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/