On Thursday, April 28, 2005 3:43 PM, Andrew Morton wrote: > "Moore, Eric Dean" <Eric.Moore@xxxxxxxx> wrote: > > > > Ok - The problem is the module_init entry point for > > mptbase.ko is not being called when the driver is statically > > compiled into the kernel. > > That doesn't sound right. The kernel will call that > module_init() function > for statically linked things. > > This came out: > > "Fusion MPT SPI Host driver 3.03.00" > > So fusion_init() is being called. Maybe the problem is that > fusion_init() > is being called at the wrong time. Look at the dsc02504.jpg you sent earlier today. Only mptspi_init was called. Not fusion_init. When fusion_init() called, it would display "Fusion MPT base driver 3.03.00". The message "Fusion MPT SPI Host driver 3.03.00" came from mptspi_init. Anyways, I have it solved. A patch soon follows. Eric Moore - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
