From: <sezeroz@ttnet.net.tr>
To: <linux-kernel@vger.kernel.org>
Cc: <marcelo.tosatti@cyclades.com>
Subject: 2.4.28-rc1, more lost patches [4/10]
Date: Wed, 27 Oct 2004 12:35:29 +0300 [thread overview]
Message-ID: <20041027093529.JYPX6935.fep01.ttnet.net.tr@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 47 bytes --]
[4/10] DAC960, firmware/alpha patch. in 2.6.
[-- Attachment #2: DAC960-firmware.patch --]
[-- Type: application/octet-stream, Size: 1675 bytes --]
from -ac / redhat
Already in 2.6
diff -urN linux-2.4.27-pre2/drivers/block/DAC960.c linux-2.4.27-pre2-pac1/drivers/block/DAC960.c
--- linux-2.4.27-pre2/drivers/block/DAC960.c 2002-11-28 23:53:12.000000000 +0000
+++ linux-2.4.27-pre2-pac1/drivers/block/DAC960.c 2004-05-05 15:48:42.000000000 +0000
@@ -1133,6 +1133,26 @@
DAC960PU/PD/PL 3.51 and above
DAC960PU/PD/PL/P 2.73 and above
*/
+#if defined(__alpha__)
+ /*
+ DEC Alpha machines were often equipped with DAC960 cards that were
+ OEMed from Mylex, and had their own custom firmware. Version 2.70,
+ the last custom FW revision to be released by DEC for these older
+ controllers, appears to work quite well with this driver.
+
+ Cards tested successfully were several versions each of the PD and
+ PU, called by DEC the KZPSC and KZPAC, respectively, and having
+ the Manufacturer Numbers (from Mylex), usually on a sticker on the
+ back of the board, of:
+
+ KZPSC D040347 (1ch) or D040348 (2ch) or D040349 (3ch)
+ KZPAC D040395 (1ch) or D040396 (2ch) or D040397 (3ch)
+ */
+# define FIRMWARE_27x "2.70"
+#else
+# define FIRMWARE_27x "2.73"
+#endif
+
if (Enquiry2.FirmwareID.MajorVersion == 0)
{
Enquiry2.FirmwareID.MajorVersion =
@@ -1152,7 +1172,7 @@
(Controller->FirmwareVersion[0] == '3' &&
strcmp(Controller->FirmwareVersion, "3.51") >= 0) ||
(Controller->FirmwareVersion[0] == '2' &&
- strcmp(Controller->FirmwareVersion, "2.73") >= 0)))
+ strcmp(Controller->FirmwareVersion, FIRMWARE_27x) >= 0)))
{
DAC960_Failure(Controller, "FIRMWARE VERSION VERIFICATION");
DAC960_Error("Firmware Version = '%s'\n", Controller,
reply other threads:[~2004-10-27 9:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041027093529.JYPX6935.fep01.ttnet.net.tr@localhost \
--to=sezeroz@ttnet.net.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox