From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Alexander Holler <holler@ahsoftware.de>
Cc: Nicolas Pitre <nico@fluxnic.net>,
Dave Martin <dave.martin@linaro.org>,
Rabin Vincent <rabin@rab.in>,
linux-kernel@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: ARM: relocation out of range (when loading a module)
Date: Thu, 13 Jan 2011 10:04:07 +0000 [thread overview]
Message-ID: <20110113100407.GB24149@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4D2E928D.9030208@ahsoftware.de>
On Thu, Jan 13, 2011 at 06:50:05AM +0100, Alexander Holler wrote:
> Hello,
>
> Am 12.01.2011 19:42, schrieb Russell King - ARM Linux:
>
>> As the overall feeling at the time was "don't use large initrds" it's
>> something I've never really cared about - and I'm still of the opinion
>> that 16MB of compressed initrd/initramfs is rather silly.
>
> Hmm, sorry, I have to disagree. ;)
> E.g. 12MB out of the 16MB in the initramfs I've used are modules.
> I've also created some larger initramfs wich included X11 and such, and
> I find it very convenient to use the initramfs to include a rootfs in
> the the kernel and so only have to handle one file for all. E.g. just
> load the kernel with the included rootfs via tftp and you are done.
Oddly, that's why I wrote the bootp wrapper, which predates the
currently broken initrd-in-kernel idea.
> Sure this can all be done using an external initrd, but that is much
> less comfortable to use.
>
> At least I like that feature since it is available and won't miss it now. ;)
The feature isn't available if it doesn't work. It's not going to get
fixed for 2.6.38 - it'll be 2.6.39 due to the timing and complexity of
the problem.
next prev parent reply other threads:[~2011-01-13 10:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 18:16 Alexander Holler
2011-01-10 22:26 ` Nicolas Pitre
2011-01-11 6:34 ` Alexander Holler
2011-01-11 15:17 ` Alexander Holler
2011-01-11 15:57 ` Russell King - ARM Linux
2011-01-11 16:02 ` Nicolas Pitre
2011-01-11 15:46 ` Rabin Vincent
2011-01-11 15:59 ` Russell King - ARM Linux
2011-01-12 3:00 ` Alexander Holler
2011-01-12 16:05 ` Dave Martin
2011-01-12 16:23 ` Russell King - ARM Linux
2011-01-12 18:28 ` Nicolas Pitre
2011-01-12 18:42 ` Russell King - ARM Linux
2011-01-12 18:55 ` Nicolas Pitre
2011-01-25 8:44 ` Sachin Verma
2011-01-25 13:23 ` Catalin Marinas
2011-01-27 5:43 ` Nicolas Pitre
2011-02-10 15:43 ` Russell King - ARM Linux
2011-02-10 19:41 ` Nicolas Pitre
2011-02-11 9:31 ` Dave Martin
2011-02-11 9:38 ` Russell King - ARM Linux
2011-02-11 9:45 ` Dave Martin
2011-02-11 13:55 ` Nicolas Pitre
2011-02-11 13:51 ` Nicolas Pitre
2011-02-11 14:25 ` Dave Martin
2011-02-11 14:42 ` Russell King - ARM Linux
2011-02-12 19:52 ` Nicolas Pitre
2011-01-13 5:50 ` Alexander Holler
2011-01-13 10:04 ` Russell King - ARM Linux [this message]
2011-01-13 14:36 ` Alexander Holler
2011-01-12 16:25 ` Matthieu CASTET
2011-01-12 16:38 ` Russell King - ARM Linux
2011-01-11 16:01 ` Nicolas Pitre
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=20110113100407.GB24149@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=dave.martin@linaro.org \
--cc=holler@ahsoftware.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=rabin@rab.in \
/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®