From: James Bottomley <James.Bottomley@xxxxxxxxxxxx> Date: Sat, 09 Sep 2006 11:04:15 -0500 > On Sat, 2006-09-09 at 08:36 -0700, Andrew Morton wrote: > > Does anyone else us the fcal driver? > > > > I'd suggest the next step would be to run a kernel profile, or just sysrq-P > > to find out where the CPU is stuck. Could a sparc person please talk the > > reporter through that process? > > I'm not sure this is really worth it. Apart from trying to keep it > compiling, fcal has had no maintainer since the 2.2 kernel days. Since > no-one has the hardware or the inclination, it's not plugged into the > SCSI FC infrastructure and thus it's bitrotting. I think it's not feasible nor worth plugging the fcal driver into the SCSI FC infrastructure right now simply because these drivers need a full software FC stack, and the SCSI FC stuff just provides very high level interfaces to all of this an expects on-board firmware to do all the protocol packet building and other FC stuff just like the Qlogic-FC and other cards do. So it's not just a matter of "porting fcal to SCSI FC", someone would need to implement the full FC software stack. - To unsubscribe from this list: 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
