I thought I'd look into this, since it seems to be relatively simple: you get the parameters from the device config page0 and set them via device config page1 as I read the driver. However, this appears to be where my fusion card runs into difficulty. Debugging the header setup I get this: mptbase: ioc1: Headers: 0: version 0 length 0 mptbase: ioc1: Headers: 1: version 3 length 4 The driver seems to think this is valid, but if it occurs, there's no way to get the parameters or run domain validation. Is this correct? There are classes of fusion card for which we simply cannot obtain transport data? Or is there a work around that's not coded into the driver? James - : 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
