Messages in this thread | | | Date | Tue, 25 Jun 2002 20:47:47 -0700 | From | jw schultz <> | Subject | Re: Urgent, Please respond - Re: max_scsi_luns and 2.4.19-pre10. |
| |
On Tue, Jun 25, 2002 at 10:05:39PM -0500, Austin Gonyou wrote: > On Tue, 2002-06-25 at 21:48, jw schultz wrote: > > I'm no expert on this bit but look in > > drivers/scsi/scsi_scan.c for CONFIG_SCSI_MULTI_LUN > > > > #ifdef CONFIG_SCSI_MULTI_LUN > > static int max_scsi_luns = 8; > > #else > > static int max_scsi_luns = 1; > > #endif > > This is, but there seems to be something more fundamental here. I'm > using the -aa patches, and the static int max_scsi_luns = 8; is actually > static int max_scsi_luns = MAX_SCSI_LUNS; > > where above is: #define MAX_SCSI_LUNS 0xFFFFFFFF; > but I'm not sure if this syntax is 0xFFFFFFFF == 8 or 2^n. > > To me, it seems like 8. I'm using pre10-aa2, I'm going to try pre10-aa4 > as well, but if I must I'm going to hard-code the kernel bits I need I > supposed to make static int max_scsi_luns = MAX_SCSI_LUNS; into static > int max_scsi_luns = 16; to ensure it works at the level I need. >
I don't have -aa but that is -1. I would suggest a bit of greping.
I seriously doubt changing it to 16 would cause data corruption. It will either work or not. If it doesn't you will crash on boot/init.
-- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws
Remember Cernan and Schmitt - 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/
| |