From: "Randy.Dunlap" <rddunlap@osdl.org>
To: adaplas <adaplas@pol.net>, akpm <akpm@osdl.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: [PATCH 11/11] tdfxfb: eliminate bad section references
Date: Wed, 9 Mar 2005 10:27:41 -0800 [thread overview]
Message-ID: <20050309102741.72bae5f6.rddunlap@osdl.org> (raw)
In-Reply-To: <20050309100825.0d77ded8.rddunlap@osdl.org>
Fix tdfxfb section references:
convert __initdata to __devinitdata.
Error: ./drivers/video/tdfxfb.o .text refers to 0000000000000e6f R_X86_64_PC32 .init.data+0xfffffffffffffffc
Error: ./drivers/video/tdfxfb.o .text refers to 0000000000000fea R_X86_64_32S .init.data+0x00000000000000c0
Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001006 R_X86_64_32S .init.data+0x00000000000000c0
Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001022 R_X86_64_32S .init.data+0x00000000000000c0
Error: ./drivers/video/tdfxfb.o .text refers to 000000000000103c R_X86_64_PC32 .init.data+0x00000000000000f4
Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001067 R_X86_64_PC32 .init.data+0x00000000000000f4
Error: ./drivers/video/tdfxfb.o .text refers to 000000000000106f R_X86_64_PC32 .init.data+0x00000000000000fc
Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001084 R_X86_64_32S .init.data+0x00000000000000c0
Error: ./drivers/video/tdfxfb.o .text refers to 00000000000010f1 R_X86_64_PC32 .init.data+0x00000000000000cc
Error: ./drivers/video/tdfxfb.o .text refers to 00000000000011b8 R_X86_64_PC32 .init.data+0x00000000000000d4
Error: ./drivers/video/tdfxfb.o .text refers to 00000000000011c1 R_X86_64_32S .init.data+0x00000000000000c0
Error: ./drivers/video/tdfxfb.o .text refers to 000000000000122b R_X86_64_PC32 .init.data+0x00000000000000d4
Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001232 R_X86_64_PC32 .init.data+0x00000000000000cc
Error: ./drivers/video/tdfxfb.o .text refers to 000000000000124a R_X86_64_32S .init.data+0x00000000000000c0
Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001320 R_X86_64_PC32 .init.data+0x00000000000000d4
Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001327 R_X86_64_32S .init.data+0x00000000000000c0
Error: ./drivers/video/tdfxfb.o .text refers to 000000000000134c R_X86_64_32S .init.data+0x00000000000000c0
Error: ./drivers/video/tdfxfb.o .text refers to 000000000000136a R_X86_64_PC32 .init.data+0x00000000000000e6
Error: ./drivers/video/tdfxfb.o .text refers to 000000000000137d R_X86_64_PC32 .init.data+0x00000000000000e8
Error: ./drivers/video/tdfxfb.o .text refers to 00000000000013b1 R_X86_64_PC32 .init.data+0xfffffffffffffffc
Error: ./drivers/video/tdfxfb.o .text refers to 00000000000013c5 R_X86_64_PC32 .init.data+0xfffffffffffffffc
Error: ./drivers/video/tdfxfb.o .text refers to 00000000000013e4 R_X86_64_32S .init.data+0x0000000000000020
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
diffstat:=
drivers/video/tdfxfb.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff -Naurp ./drivers/video/tdfxfb.c~video_tdfxfb_sections ./drivers/video/tdfxfb.c
--- ./drivers/video/tdfxfb.c~video_tdfxfb_sections 2005-03-01 23:37:51.000000000 -0800
+++ ./drivers/video/tdfxfb.c 2005-03-08 13:37:00.000000000 -0800
@@ -89,7 +89,7 @@
#define VOODOO3_MAX_PIXCLOCK 300000
#define VOODOO5_MAX_PIXCLOCK 350000
-static struct fb_fix_screeninfo tdfx_fix __initdata = {
+static struct fb_fix_screeninfo tdfx_fix __devinitdata = {
.id = "3Dfx",
.type = FB_TYPE_PACKED_PIXELS,
.visual = FB_VISUAL_PSEUDOCOLOR,
@@ -98,7 +98,7 @@ static struct fb_fix_screeninfo tdfx_fix
.accel = FB_ACCEL_3DFX_BANSHEE
};
-static struct fb_var_screeninfo tdfx_var __initdata = {
+static struct fb_var_screeninfo tdfx_var __devinitdata = {
/* "640x480, 8 bpp @ 60 Hz */
.xres = 640,
.yres = 480,
@@ -202,7 +202,7 @@ static unsigned long do_lfb_size(struct
*/
static int nopan = 0;
static int nowrap = 1; // not implemented (yet)
-static char *mode_option __initdata = NULL;
+static char *mode_option __devinitdata = NULL;
/* -------------------------------------------------------------------------
* Hardware-specific funcions
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-03-09 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 18:08 [PATCH 0/11] framebuffer: eliminate bad section references Randy.Dunlap
2005-03-09 18:10 ` [PATCH 1/11] asiliantfb: " Randy.Dunlap
2005-03-09 18:11 ` [PATCH 2/11] atyfb: " Randy.Dunlap
2005-03-09 18:15 ` [PATCH 3/11] imsttfb: " Randy.Dunlap
2005-03-09 18:17 ` [PATCH 4/11] kyro: " Randy.Dunlap
2005-03-09 18:18 ` [PATCH 5/11] neofb: " Randy.Dunlap
2005-03-09 18:19 ` [PATCH 6/11] pm2fb: " Randy.Dunlap
2005-03-09 18:23 ` [PATCH 7/11] radeonfb: " Randy.Dunlap
2005-03-09 18:35 ` Torgeir Veimo
2005-03-09 18:59 ` Randy.Dunlap
2005-03-09 18:24 ` [PATCH 8/11] riva: " Randy.Dunlap
2005-03-09 18:25 ` [PATCH 9/11] savagefb: " Randy.Dunlap
2005-03-09 18:26 ` [PATCH 10/11] sis: " Randy.Dunlap
2005-03-09 18:27 ` Randy.Dunlap [this message]
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=20050309102741.72bae5f6.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).