From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc3-mm3: `risc_code_addr01' multiple definition
Date: Thu, 07 Oct 2004 10:29:05 -0700 [thread overview]
Message-ID: <1097170149.12535.27.camel@praka> (raw)
In-Reply-To: <20041007165849.GA4493@stusta.de>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
On Thu, 2004-10-07 at 18:58 +0200, Adrian Bunk wrote:
> On Thu, Oct 07, 2004 at 01:51:39AM -0700, Andrew Morton wrote:
> >...
> > Changes since 2.6.9-rc3-mm2:
> >...
> > bk-scsi.patch
> >...
>
> This causes the following compile error:
>
>
> <-- snip -->
>
> ...
> LD drivers/scsi/built-in.o
> drivers/scsi/qla1280.o(.data+0xe65c): multiple definition of `risc_code_addr01'
> drivers/scsi/qlogicfc.o(.data+0x0): first defined here
> make[2]: *** [drivers/scsi/built-in.o] Error 1
>
Hmm, seems the additional 1040 support in qla1280.c is causing name
clashes with the firmware image in qlogicfc_asm.c. Try out the attached
patch (not tested) which provides the 1040 firmware image unique
variable names.
Looks like there would be some name clashes in qlogicfc and qlogicisp.
--
av
> <-- snip -->
>
>
> cu
> Adrian
>
[-- Attachment #2: fixup_fw_variables.diff --]
[-- Type: text/plain, Size: 1849 bytes --]
--- linux-2.6.9-rc3-mm3/drivers/scsi/ql1040_fw.h~ 2004-10-07 10:15:19.275258120 -0700
+++ linux-2.6.9-rc3-mm3/drivers/scsi/ql1040_fw.h 2004-10-07 10:17:51.292148040 -0700
@@ -28,15 +28,15 @@
* Firmware Version 7.65.00 (14:17 Jul 20, 1999)
*/
-unsigned short risc_code_version = 7*1024+65;
+unsigned short fw1040_version = 7*1024+65;
-unsigned char firmware_version[] = {7,65,0};
+unsigned char fw1040_version_str[] = {7,65,0};
#define FW_VERSION_STRING "7.65.0"
-unsigned short risc_code_addr01 = 0x1000 ;
+unsigned short fw1040_addr01 = 0x1000 ;
-unsigned short risc_code01[] = {
+unsigned short fw1040_code01[] = {
0x0078, 0x103a, 0x0000, 0x4057, 0x0000, 0x2043, 0x4f50, 0x5952,
0x4947, 0x4854, 0x2031, 0x3939, 0x3520, 0x514c, 0x4f47, 0x4943,
0x2043, 0x4f52, 0x504f, 0x5241, 0x5449, 0x4f4e, 0x2049, 0x5350,
@@ -2097,5 +2097,5 @@ unsigned short risc_code01[] = {
0x0014, 0x878e, 0x0016, 0xa21c, 0x1035, 0xa8af, 0xa210, 0x3807,
0x300c, 0x817e, 0x872b, 0x8772, 0xa8a8, 0x0000, 0xdf21
};
-unsigned short risc_code_length01 = 0x4057;
+unsigned short fw1040_length01 = 0x4057;
--- linux-2.6.9-rc3-mm3/drivers/scsi/qla1280.c~ 2004-10-07 10:21:47.552231048 -0700
+++ linux-2.6.9-rc3-mm3/drivers/scsi/qla1280.c 2004-10-07 10:22:56.828699424 -0700
@@ -659,8 +659,8 @@ static struct qla_boards ql1280_board_tb
/* Name , Number of ports, FW details */
{"QLA12160", 2, &fw12160i_code01[0], &fw12160i_length01,
&fw12160i_addr01, &fw12160i_version_str[0]},
- {"QLA1040", 1, &risc_code01[0], &risc_code_length01,
- &risc_code_addr01, &firmware_version[0]},
+ {"QLA1040", 1, &fw1040_code01[0], &fw1040_length01,
+ &fw1040_addr01, &fw1040_version_str[0]},
{"QLA1080", 1, &fw1280ei_code01[0], &fw1280ei_length01,
&fw1280ei_addr01, &fw1280ei_version_str[0]},
{"QLA1240", 2, &fw1280ei_code01[0], &fw1280ei_length01,
next prev parent reply other threads:[~2004-10-07 17:46 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 8:51 2.6.9-rc3-mm3 Andrew Morton
2004-10-07 9:30 ` 2.6.9-rc3-mm3 Martin Zwickel
2004-10-07 9:41 ` 2.6.9-rc3-mm3 Nick Sanders
2004-10-07 9:50 ` 2.6.9-rc3-mm3 Andrew Morton
2004-10-07 10:10 ` 2.6.9-rc3-mm3 Martin Zwickel
2004-10-07 10:44 ` 2.6.9-rc3-mm3 Hanno Meyer-Thurow
[not found] ` <20041007125610.0019eb3d@mango.fruits.de>
2004-10-07 10:58 ` 2.6.9-rc3-mm3 Hanno Meyer-Thurow
2004-10-07 10:16 ` 2.6.9-rc3-mm3 Nick Sanders
2004-10-07 11:40 ` 2.6.9-rc3-mm3 William Lee Irwin III
2004-10-07 21:25 ` 2.6.9-rc3-mm3 J.A. Magallon
2004-10-07 21:46 ` 2.6.9-rc3-mm3 J.A. Magallon
2004-10-07 22:07 ` 2.6.9-rc3-mm3 Andrew Morton
2004-10-07 22:41 ` 2.6.9-rc3-mm3 J.A. Magallon
2004-10-07 22:54 ` 2.6.9-rc3-mm3 Andrew Morton
2004-10-07 23:06 ` 2.6.9-rc3-mm3 J.A. Magallon
2004-10-07 23:40 ` 2.6.9-rc3-mm3 Greg KH
2004-10-08 1:05 ` 2.6.9-rc3-mm3 Paul Fulghum
2004-10-08 11:23 ` 2.6.9-rc3-mm3 William Lee Irwin III
2004-10-08 11:34 ` 2.6.9-rc3-mm3 Ryan Cumming
2004-10-08 7:00 ` 2.6.9-rc3-mm3 Ingo Molnar
2004-10-07 22:03 ` 2.6.9-rc3-mm3 William Lee Irwin III
2004-10-07 9:59 ` 2.6.9-rc3-mm3 Martin Zwickel
2004-10-07 10:04 ` 2.6.9-rc3-mm3 Jesper Juhl
2004-10-07 10:15 ` 2.6.9-rc3-mm3 Russell King
2004-10-07 16:58 ` 2.6.9-rc3-mm3: `risc_code_addr01' multiple definition Adrian Bunk
2004-10-07 17:29 ` Andrew Vasquez [this message]
2004-10-07 17:50 ` James Bottomley
2004-10-07 18:13 ` Andrew Vasquez
2004-10-07 18:15 ` Andrew Vasquez
2004-10-07 18:30 ` Andrew Vasquez
2004-10-21 13:02 ` Jes Sorensen
2004-10-07 17:08 ` 2.6.9-rc3-mm3 (compile stats) John Cherry
2004-10-07 20:56 ` 2.6.9-rc3-mm3 Joel Schopp
2004-10-07 21:33 ` 2.6.9-rc3-mm3 Andrew Morton
2004-10-07 21:01 ` 2.6.9-rc3-mm3: build problem on dual-Opteron w/ NUMA Rafael J. Wysocki
2004-10-07 21:40 ` Andrew Morton
2004-10-07 21:46 ` Andi Kleen
2004-10-08 10:33 ` 2.6.9-rc3-mm3: vm-thrashing-control-tuning Hideo AOKI
2004-10-08 20:49 ` Andrew Morton
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=1097170149.12535.27.camel@praka \
--to=andrew.vasquez@qlogic.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).