linux-kernel - Question about HighPoint RocketRAID 642L SCSI driver conflict with Linux AHCI driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <002a01d09e84$22be8f90$683baeb0$@highpoint-tech.com>
Date:	Thu, 4 Jun 2015 13:05:49 +0800
From:	"linux" <linux@...hpoint-tech.com>
To:	<tj@...nel.org>
Cc:	<linux-ide@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Question about HighPoint RocketRAID 642L SCSI driver conflict with Linux AHCI driver

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?

Best Regards,
HighPoint Linux Team

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