content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: iswraid calling modprobe when scsi statically compiled?
Date: Thu, 15 Jan 2004 12:05:50 -0700
Message-ID: <933D2981B35C9B4B8793B56C4AE9E16B593A8F@azsmsx405.ch.intel.com>
Thread-Topic: iswraid calling modprobe when scsi statically compiled?
Thread-Index: AcPbk2D8qMGzkQQyQWewdYIgYF96IwABjX+Q
From: "Kannanthanam, Boji T" <boji.t.kannanthanam@intel.com>
To: "Sergey Vlasov" <vsu@altlinux.ru>, <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1056
Lines: 26

> 
> The problem is in the initialization ordering. iswraid must initialize
> after SCSI, but it is located in the IDE drivers directory, and
> therefore is initialized before SCSI. So it won't work when built into
> the kernel.
> 
> If you build iswraid as module and load it from initrd (after the SCSI
> subsystem is initialized and raw drives are detected), it should work.
> 

As pointed this in an unfortunate side effect of the nature of driver
dependency: iswraid (in ataraid/IDE subsystem) depending on ata_piix (in
SCSI). The above solution will solve the issue. 

But can anyone shed some light on resolving this issue other than
compiling the driver as kernel module ?
i.e is there a way I can change the order of driver initialization in
the kernel ? Load SCSI subsystem before IDE ? 

Thanks,
boji
-
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/