mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Date: Wed, 10 Jun 2015 23:47:14 +0100	[thread overview]
Message-ID: <20150610234714.76db2719@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <002a01d09e84$22be8f90$683baeb0$@highpoint-tech.com>

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

      parent reply	other threads:[~2015-06-10 22:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04  5:05 linux
2015-06-04  5:16 ` Tejun Heo
2015-06-10 22:47 ` One Thousand Gnomes [this message]

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=20150610234714.76db2719@lxorguk.ukuu.org.uk \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@highpoint-tech.com \
    --cc=tj@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

all inboxes | Powered by JetHome®