On Mon, Oct 15, 2007 at 08:18:24PM +0200, Boaz Harrosh wrote: > This is all new territory for me. But CONFIG_SCSI_PLUTO is dependent on > SCSI and fc.c is not the real driver just the needed bits from the sparc > side. So the code mess calls for a Kconfig mess, I guess.
I've spent a lot of time looking at pluto/fc4 recently. And I'm very much still in a 'wtf' mode. Pluto creates a new scsi *host* for every Sun Storage Array proessor *device* on the SCSI bus. I have no clue why it does this. I'm sure there's a sane sensible driver or three trying to get out from inside the pluto/soc/socal/fc4 maze, but I'm not quite sure what form it should take. Dave, can you explain what's going on? I really want to help this driver fit the current scsi model better, but I don't understand what it's trying to do. -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
