From: Sascha Hauer <s.hauer@pengutronix.de>
To: David Dgien <dgienda125@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC PATCH 8/8] arm: module: Allow modules outside of bl range
Date: Wed, 17 Jun 2020 15:52:22 +0200 [thread overview]
Message-ID: <20200617135222.GD11869@pengutronix.de> (raw)
In-Reply-To: <20200617034404.5904-9-dgienda125@gmail.com>
On Tue, Jun 16, 2020 at 11:44:04PM -0400, David Dgien wrote:
> Unlike the Linux kernel, barebox does not have a dedicated heap for
> storing modules. Therefore, if the system memory configuration places
> the general heap further away than can be reached by a 'bl' instruction
> (24 bits of address, or 16 MiB), then the module relocations will fail
> due to being out of range.
At least the tlsf malloc implementation allows for multiple heaps. It
might be easier to just add another heap just below the barebox image.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-06-17 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 3:43 [RFC PATCH 0/8] Module and ARM Module updates and fixes David Dgien
2020-06-17 3:43 ` [RFC PATCH 1/8] Makefile: Initialize and export KBUILD variables David Dgien
2020-06-17 3:43 ` [RFC PATCH 2/8] module: Add init macros to module.h David Dgien
2020-06-17 3:43 ` [RFC PATCH 3/8] module: Fix adding module to list after layout David Dgien
2020-06-17 3:44 ` [RFC PATCH 4/8] module: Fix module command registration David Dgien
2020-06-17 3:44 ` [RFC PATCH 5/8] module: Implement HAVE_MOD_ARCH_SPECIFIC David Dgien
2020-06-17 3:44 ` [RFC PATCH 6/8] arm: makefile: Fix compiler flag variable David Dgien
2020-06-17 3:44 ` [RFC PATCH 7/8] arm: elf: Add THM relocation types David Dgien
2020-06-17 3:44 ` [RFC PATCH 8/8] arm: module: Allow modules outside of bl range David Dgien
2020-06-17 13:52 ` Sascha Hauer [this message]
2020-06-17 13:45 ` [RFC PATCH 0/8] Module and ARM Module updates and fixes Sascha Hauer
2020-06-18 1:54 ` David Dgien
2020-06-18 13:10 ` Sascha Hauer
2020-06-22 17:52 ` Masahiro Yamada
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=20200617135222.GD11869@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=dgienda125@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox