Update copyright date on LICENSE.

Update README to note that multi-id firmware needs to be used for NPIV.

Add a FIRMWARE readme that was supposed to go in back last June.

M    qla_isp/LICENSE
M    qla_isp/README.scst
A    qla_isp/FIRMWARE.readme

git-svn-id: https://scst.svn.sourceforge.net/svnroot/scst/trunk@1062 d57e44dd-8a1f-0410-8b47-8ef2f437770f

diff --git a/qla_isp/FIRMWARE.readme b/qla_isp/FIRMWARE.readme
new file mode 100644 (file)
index 0000000..af799f8
--- /dev/null
+++ b/qla_isp/FIRMWARE.readme
@@ -0,0 +1,26 @@
+Sat Aug 22 21:06:07 PDT 2009
+
+Firmware binary modules provided by QLogic may be loaded with the standard
+linux firmware blob mechanism, and in fact this is the default.
+
+It should be noted that pulling random firmware blobs will get random
+results. For example, 4.4.5 seems to crash and burn with target mode
+here on 24XX cards. Normally this would be a cause for panic, yet the
+more recent 4.6.0 version works fine. The trouble is that this firmware
+may not be available in binary from the QLogic ftp site.
+
+You can either hack on Makefile definies and compile in the QLogic firmware
+sets included herein, or use the fwbin tool in the firmware directory to
+make your own binary modules.
+
+If you want multi-id firmware support enabled for the binaries built
+with the fwbin module, change the in fwbin from
+
+dowr '#define ISP_2400 1'
+dowr '#define ISP_2500 1'
+
+to
+
+dowr '#define ISP_2400_MULTI 1'
+dowr '#define ISP_2500_MULTI 1'
+

diff --git a/qla_isp/LICENSE b/qla_isp/LICENSE
index c6aca8d..5a91588 100644 (file)
--- a/qla_isp/LICENSE
+++ b/qla_isp/LICENSE
@@ -1,4 +1,4 @@
-Copyright (c) 1997-2008 by Matthew Jacob
+Copyright (c) 1997-2009 by Matthew Jacob
 All rights reserved.
 
 Redistribution and use in source and binary forms, with or without

diff --git a/qla_isp/README.scst b/qla_isp/README.scst
index 462acc7..6212b71 100644 (file)
--- a/qla_isp/README.scst
+++ b/qla_isp/README.scst
@@ -132,6 +132,8 @@ ports(channels) and cannot be greater than 127. Each vport has its own WWN.
 From the driver point of view each vport is a separate channel. You can define
 separate role for each of the channels.
 
+Note that firmware that supports multiple ids must be used.
+
 PROCFS INTERFACE
 
 Target configuration interface is located in the following file: