On 12/06/2013 02:04 PM, Tom Rini wrote: ...
There's two problems here. The first problem is that we have between 256MiB and 1GiB of DDR on the platform, but we could just design for the smallest case. The second problem is, what's big enough? You've got 32MiB (tegra30) which I would hope is enough (and I suggested as much in Dennis' thread) for kernel + BSS, but how big is a multi platform kernel with a few big features going to get? Or do we say that's an unreasonable out of box use case?
Is there any limit on .data/.bss size like there is .text (due to the limited range of relative jump encoding), or would data accesses just fall back to a relative load of the absolute address, and hence be unbounded.
FWIW, I see the following sizes currently:
tegra_defconfig
.text 005862c4 .data 0005eb68 .bss 00055bf0
multi_v7_defconfig
.text 004a5560 .data 00092600 .bss 00046014
(I think multi_v7_defconfig doesn't yet have that many drivers enabled, and when it does presumably they'd be modules)
... so BSS isn't terribly large at the moment.