From: Tejun Heo <tj@kernel.org>
To: linux <linux@highpoint-tech.com>
Cc: 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: Thu, 4 Jun 2015 14:16:56 +0900 [thread overview]
Message-ID: <20150604051656.GO20091@mtj.duckdns.org> (raw)
In-Reply-To: <002a01d09e84$22be8f90$683baeb0$@highpoint-tech.com>
Hello,
On Thu, Jun 04, 2015 at 01:05:49PM +0800, linux 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.
>
> 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? Is there
> any way to prevent this in the future?
Hmmm... so, you're trying to load a proprietary driver but you're
having problem because in-kernel ahci attaches to the driver?
* If the driver is built-in, putting the proprietary driver before
ahci in Makefile will make that driver probe before ahci.
* If module, ahci can be unbound by echoing the PCI bus ID to
/sys/bus/pci/drivers/ahci/unbind and then bind that to the
proprietary driver.
* Or you can tell pci-stub driver do grab the PCI ID so that ahci
doesn't probe it at all. Once the proprietary driver becomes
available, the device can be rebound to the driver.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-06-04 5:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 5:05 Question about HighPoint RocketRAID 642L SCSI driver conflict with Linux AHCI driver linux
2015-06-04 5:16 ` Tejun Heo [this message]
2015-06-10 22:47 ` One Thousand Gnomes
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=20150604051656.GO20091@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@highpoint-tech.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