From: David Miller <davem@davemloft.net>
To: kyle@mcmartin.ca
Cc: vst@vlnb.net, sparclinux@vger.kernel.org, simone.ricci@gmail.com,
scst-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Nick.Couchman@seakr.com
Subject: Re: Error "Unknown relocation: 36" on module load on Sparc
Date: Wed, 16 Jun 2010 13:38:54 -0700 (PDT) [thread overview]
Message-ID: <20100616.133854.183053376.davem@davemloft.net> (raw)
In-Reply-To: <20100616192257.GW20317@bombadil.infradead.org>
From: Kyle McMartin <kyle@mcmartin.ca>
Date: Wed, 16 Jun 2010 15:22:57 -0400
> arch/sparc/kernel/module.c needs to be patched to support the new
> relocation type... Based on binutils/gas/config/tc-sparc.c and gold's
> sparc config this looks to be the same as the hi22 reloc...
>
> Can you test the following patch?
This change is incorrect.
LM22 relocations do not get emitted for the "medlow" code model, which
is what is explicitly specified on the kernel compiler command line
for sparc64 via "-mcmodel=medlow".
Someone this person is using incorrect CFLAGS when building their
module, and that's why they have this problem, because the compiler's
default code model on sparc64 can generate those relocations.
next prev parent reply other threads:[~2010-06-16 20:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimuv7nOlcGFxqPZlwcAjLmFMiLAvbA5O7F32Wbg@mail.gmail.com>
2010-06-16 19:05 ` Vladislav Bolkhovitin
2010-06-16 19:22 ` Kyle McMartin
2010-06-16 20:38 ` David Miller [this message]
2010-06-16 20:40 ` Kyle McMartin
2010-06-16 20:35 ` David Miller
2010-06-22 19:07 ` Vladislav Bolkhovitin
2010-06-22 19:35 ` Sam Ravnborg
2010-06-22 21:17 ` David Miller
2010-06-22 21:16 ` David Miller
2010-06-16 19:08 ` How to printk/sprintf uint64_t on Sparc without format and argument types mismatch Vladislav Bolkhovitin
2010-06-16 19:29 ` Kyle McMartin
2010-06-16 20:36 ` David Miller
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=20100616.133854.183053376.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Nick.Couchman@seakr.com \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=scst-devel@lists.sourceforge.net \
--cc=simone.ricci@gmail.com \
--cc=sparclinux@vger.kernel.org \
--cc=vst@vlnb.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
all inboxes | Powered by JetHome®