On 2005-12-16 04:32 -0500, Jeff Garzik wrote: > Andre Majorel wrote: > > >I have a motherboard with two SATA chips (Nvidia nForce 4 and > >Silicon Image SiI 3114) running Linux 2.6.14.3. The drivers are > >SCSI_SATA_NV and SCSI_SATA_SIL, both compiled-in. > > > >Ports on the SiI 3114 controller are assigned scsi0 through > >scsi3 and ports on the nForce4 chip are assigned scsi4 through > >scsi7. Is there any way to control the order so that SCSI_SATA_NV > >gets scsi0-scsi3 and SCSI_SATA_SIL gets scsi4-scsi7 instead ? > > Use modules, But then wouldn't I have to use initrd if / is on a raid device ? > otherwise its defined by link order... OK. This did the trick : diff -ur --exclude '*.o' linux-2.6.14.3/drivers/scsi/Makefile linux-2.6.14.3-nf4-first/drivers/scsi/Makefile --- linux-2.6.14.3/drivers/scsi/Makefile 2005-11-24 23:10:21.000000000 +0100 +++ linux-2.6.14.3-nf4-first/drivers/scsi/Makefile 2005-12-16 20:52:14.000000000 +0100 @@ -124,6 +124,7 @@ obj-$(CONFIG_SCSI_NSP32) += nsp32.o obj-$(CONFIG_SCSI_IPR) += ipr.o obj-$(CONFIG_SCSI_IBMVSCSI) += ibmvscsi/ +obj-$(CONFIG_SCSI_SATA_NV) += libata.o sata_nv.o obj-$(CONFIG_SCSI_SATA_AHCI) += libata.o ahci.o obj-$(CONFIG_SCSI_SATA_SVW) += libata.o sata_svw.o obj-$(CONFIG_SCSI_ATA_PIIX) += libata.o ata_piix.o @@ -134,7 +135,6 @@ obj-$(CONFIG_SCSI_SATA_VITESSE) += libata.o sata_vsc.o obj-$(CONFIG_SCSI_SATA_SIS) += libata.o sata_sis.o obj-$(CONFIG_SCSI_SATA_SX4) += libata.o sata_sx4.o -obj-$(CONFIG_SCSI_SATA_NV) += libata.o sata_nv.o obj-$(CONFIG_SCSI_SATA_ULI) += libata.o sata_uli.o obj-$(CONFIG_SCSI_SATA_MV) += libata.o sata_mv.o # dmesg | grep 'scsi. :' scsi0 : sata_nv scsi1 : sata_nv scsi2 : sata_nv scsi3 : sata_nv scsi4 : sata_sil scsi5 : sata_sil scsi6 : sata_sil scsi7 : sata_sil Thanks ! -- André Majorel <URL:http://www.teaser.fr/~amajorel/> Do not use this account for regular correspondence. See the URL above for contact information. - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
