From: Kai Holthaus <kmh@sonic.net>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Module Relocation Problem
Date: Mon, 5 Jun 2006 19:38:19 -0700 [thread overview]
Message-ID: <200606051938.20617.kmh@sonic.net> (raw)
In-Reply-To: <200606060220.k562KRc2009433@hiauly1.hia.nrc.ca>
[-- Attachment #1.1: Type: text/plain, Size: 1157 bytes --]
> You might explore ways to reduce the modules's (e.g., limit inlining).
> You might also try compiling with the -mlong-calls options. This forces
> GCC to use the "bve" instruction for calls in PA 2.0 compilations. The
> call setup using bve is slightly longer but there are no distance
> limitations. There's also a PA 1.x variant using "ble". What's unclear
> to me is whether the kernel loader has support for the relocations used
> in these sequences.
I think I'm clearly out of my league here, since I honestly don't understand
bve vs ble... :(
Anyway - I tried compiling the module with the "-mlong-calls" option - now I
get a different error message upon trying to insert the module into the
kernel:
module quickcam: Unknown relocation: 10
Does that tell you anything? Because I have no clue...
Thanks so much for your help!
Kai
--
Hofstadter's Law:
"It always takes longer than you expect,
even when you take into account Hofstadter's Law."
-- Douglas R. Hofstadter
kmh.AT.sonic.net
Check out Mission Octagon - a new, exciting novel!
http://www.missionoctagon.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 169 bytes --]
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2006-06-06 2:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 1:45 [parisc-linux] Module Relocation Problem Kai Holthaus
2006-06-06 2:20 ` John David Anglin
2006-06-06 2:26 ` John David Anglin
2006-06-06 2:38 ` Kai Holthaus [this message]
2006-06-06 3:07 ` John David Anglin
2006-06-06 3:20 ` Kai Holthaus
2006-06-06 3:49 ` John David Anglin
2006-06-06 12:51 ` Thibaut VARENE
2006-06-14 8:02 ` Randolph Chung
2006-06-14 16:47 ` James Bottomley
[not found] <J0FGHF$3C34E7AFFFACE857F314B50EFB7BB29D@scarlet.be>
[not found] ` <200606101105.38472.kmh@sonic.net>
[not found] ` <448B184F.7020309@tiscali.be>
2006-06-26 2:02 ` Kai Holthaus
2006-06-26 2:10 ` Kyle McMartin
[not found] ` <200606252124.58264.kmh@sonic.net>
2006-06-26 12:10 ` Kyle McMartin
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=200606051938.20617.kmh@sonic.net \
--to=kmh@sonic.net \
--cc=parisc-linux@lists.parisc-linux.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 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.