From: vlad@emcraft.com (Vladimir K)
To: linux-arm-kernel@lists.infradead.org
Subject: insmod problem on ARM with more than 16MB of RAM?
Date: Fri, 03 Feb 2012 19:12:04 +0300 [thread overview]
Message-ID: <4F2C0754.4070504@emcraft.com> (raw)
In-Reply-To: <20111222204515.GQ2577@n2100.arm.linux.org.uk>
> So for MMU platforms, we just ensure that modules are always placed
> within reach of the kernel text. For nommu platforms, modules are
> a bitch - and TBH given the virtually non-existent activity/interest
> from the nommu sector, it's something I'm willing to spend the grand
> total of zero time to solve this _really_ _hard_ problem.
Wouldn't just adding a -mlong-calls to CFLAGS_MODULE
resolve the problem?
Something along the lines of:
ifeq ($(CONFIG_MODULES),y)
CFLAGS_MODULE += -mlong-calls
endif
in arch/arm/Makefile.
This this change, modules work fine for me on a 32MBytes RAM
Cortex-M3 configuration.
Regards,
Vladimir Khusainov
prev parent reply other threads:[~2012-02-03 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 16:35 insmod problem on ARM with more than 16MB of RAM? Sergei Poselenov
2011-12-22 16:49 ` Catalin Marinas
2011-12-22 20:45 ` Russell King - ARM Linux
2012-02-03 16:12 ` Vladimir K [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=4F2C0754.4070504@emcraft.com \
--to=vlad@emcraft.com \
--cc=linux-arm-kernel@lists.infradead.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.