Re: Where is CONFIG_BOOT_LOAD ?
On Tuesday 12 April 2011 19:03:09 Joachim Förster wrote: Note that the default 0x400... is the link address of the zImage wrapper rather than the one of THE kernel. Yes, and I need more space for the uncompression to take place when using a ramdisk. Currently the link address seems to be hard-coded into arch/powerpc/boot/wrapper (a shell script). Since long ago I'm wondering why the maintainers did that. But I guess there is a reason, because it wasn't that way in the old arch/ppc days ;-) ... Thanks for that. I'd been using objcopy --change-addresses to relocate the elf file with success. Is configuring the zImage-piggy-back-loader through menuconfig co evil? That seems like a good idea. Maybe add some way to figure out if the uncompressed kernel overlaps the zImage wrapper ? -- Guillaume Dargaud http://www.gdargaud.net/Antarctica/ ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Where is CONFIG_BOOT_LOAD ?
On Tue, 2011-04-12 at 19:03 +0200, Joachim Förster wrote: Note that the default 0x400... is the link address of the zImage wrapper rather than the one of THE kernel. Currently the link address seems to be hard-coded into arch/powerpc/boot/wrapper (a shell script). Since long ago I'm wondering why the maintainers did that. But I guess there is a reason, because it wasn't that way in the old arch/ppc days ;-) ... Is configuring the zImage-piggy-back-loader through menuconfig co evil? Well, not really evil but if you need a special setting for your board, you add a case for that board in the wrapper script. The idea is that the boot wrapper can be build outside of the kernel build tree itself. IE. A distro could (and sometimes do) ship with the standalone boot directory, possibly the .o's already built, and will wrap the zImage at install time. Cheers, Ben. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Where is CONFIG_BOOT_LOAD ?
On 04/08/2011 02:58 PM, Guillaume Dargaud wrote: Isn't that blackfin specific? So how do you change the loading address of the PowerPC kernel from its default 0x40 address ? Note that the default 0x400... is the link address of the zImage wrapper rather than the one of THE kernel. Currently the link address seems to be hard-coded into arch/powerpc/boot/wrapper (a shell script). Since long ago I'm wondering why the maintainers did that. But I guess there is a reason, because it wasn't that way in the old arch/ppc days ;-) ... Is configuring the zImage-piggy-back-loader through menuconfig co evil? Joachim ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Where is CONFIG_BOOT_LOAD ?
Hello all, I don't see this option in the .config and in the menuconfig / Advanced Setup I don't see a [Set the boot link/load address]: [*] Prompt for advanced kernel configuration options [ ] Set maximum low memory [ ] Set custom page offset address [ ] Set custom kernel base address [ ] Set custom user task size [ ] Set custom consistent memory pool size -- Guillaume Dargaud http://www.gdargaud.net/Antarctica/ ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Where is CONFIG_BOOT_LOAD ?
On Fri, 2011-04-08 at 11:28 +0200, Guillaume Dargaud wrote:
Hello all,
I don't see this option in the .config and in the menuconfig / Advanced Setup
I don't see a [Set the boot link/load
address]:
[*] Prompt for advanced kernel configuration options
[ ] Set maximum low memory
[ ] Set custom page offset address
[ ] Set custom kernel base address
[ ] Set custom user task size
[ ] Set custom consistent memory pool size
Isn't that blackfin specific?
linux-next # find -name Kconfig -exec grep -H BOOT_LOAD \{\} \;
./arch/blackfin/Kconfig:config BOOT_LOAD
linux-next # find -exec grep -H CONFIG_BOOT_LOAD \{\} \;
./arch/blackfin/boot/Makefile:UIMAGE_OPTS-$(CONFIG_RAMKERNEL) += -a
$(CONFIG_BOOT_LOAD)
./arch/blackfin/kernel/vmlinux.lds.S: . = CONFIG_BOOT_LOAD;
./arch/blackfin/kernel/vmlinux.lds.S: . = CONFIG_BOOT_LOAD;
./arch/blackfin/kernel/trace.c: } else if (address CONFIG_BOOT_LOAD) {
./arch/blackfin/kernel/setup.c: _rambase = CONFIG_BOOT_LOAD;
./arch/blackfin/configs/SRV1_defconfig:CONFIG_BOOT_LOAD=0x40
./arch/blackfin/configs/BF527-TLL6527M_defconfig:CONFIG_BOOT_LOAD=0x40
./arch/blackfin/mach-common/arch_checks.c:#if CONFIG_BOOT_LOAD
FIXED_CODE_END
./arch/blackfin/mach-common/arch_checks.c:#if (CONFIG_BOOT_LOAD 0x3)
./arch/blackfin/mach-common/arch_checks.c:#if ((0x -
L1_CODE_START + 1) + CONFIG_BOOT_LOAD) 0x100
-Florian
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Where is CONFIG_BOOT_LOAD ?
Isn't that blackfin specific? So how do you change the loading address of the PowerPC kernel from its default 0x40 address ? -- Guillaume Dargaud http://www.gdargaud.net/ ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
