 Messages in this thread SubjectRe: ARM: relocation out of range
(when loading a module) On Tue, Jan 11, 2011 at 04:17:24PM
+0100, Alexander Holler wrote: > Thinking a bit more about that
(for me unexcpected) "relocation out of > range" error when
loading a module, I'm curious if there could be other >
conditions which would lead to that error. Especially conditions
which > could be generated by the userspace or remote from some
network.  It's purely about the relative position of the kernel
text to the module text. Nothing outside of the compilation of
the kernel will affect it.  It's all to do with the branch
instructions in modules having a limited  We generally place the
kernel such that it starts 32K into the kernel's system RAM
mapping. We place modules immediately below this mapping. The
initramfs image sits in the kernel body in the startup data,
which sits between the startup text at the beginning of the
kernel, and the main kernel text which follows.  We _could_
rearrange the placement of these sect