From: Ralf Baechle <ralf@linux-mips.org>
To: Madhavi <madhavis@sasken.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Relocation overflow problem with MIPS
Date: Thu, 3 Apr 2003 23:04:51 +0200 [thread overview]
Message-ID: <20030403230451.A6583@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0304031124100.24014-100000@pcz-madhavis.sasken.com>; from madhavis@sasken.com on Thu, Apr 03, 2003 at 11:25:28AM +0530
On Thu, Apr 03, 2003 at 11:25:28AM +0530, Madhavi wrote:
> I am working on a device driver software for linux kernel version 2.4.19.
> My driver is a loadable module and the size of the module executable is
> approximately 1.4MB.
>
> When I tried to load this module on x86, I didn't have any problems while
> installing it. On MIPS (R5432) CPU, this is giving the following problems:
>
> edge_mod.o: Relocation overflow of type 4 for printk
[...]
You must use the same flag to compile modules as the kernel's Makefile.
In particular you were missing -mlong-calls.
> Could anyone tell me what this problem could be? What is relocation
> overflow of type 4? Where can I find the list of all the possible
> relocation overflow types and their descriptions?
Read the source ...
> My module is not compiled using the options -fPIC. Would it make any
> difference if I enable this option?
>
> I have seen this following comment in modutils-2.4.12/obj/obj_mips.c
>
> /* _gp_disp is a magic symbol for PIC which is not supported for
> the kernel and loadable modules. */
>
> So, I was thinking that -fPIC wouldn't help much. Am I right?
-fPIC is the compiler default.
> Sasken Business Disclaimer
[legal bullshit disclaimer burried in /dev/zero]
Ralf
next prev parent reply other threads:[~2003-04-03 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 5:55 Relocation overflow problem with MIPS Madhavi
2003-04-03 5:55 ` Madhavi
2003-04-03 21:04 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-03 4:40 Madhavi
2003-04-03 5:21 ` Jun Sun
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=20030403230451.A6583@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=madhavis@sasken.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.