Re: preferred solution for building kernel.deb and defining Entry point address
Am 12.07.2011 01:43, schrieb Ben Hutchings:
Please explain exactly how you are building the kernel with a
different entry point (config changes and commands).
Hi Ben, many thanks for the answer.
I'm working with the debian sources on patchlevel 31 as base and applied
the mikep5 patch [1]. I also tried to use the default powerpc-config (I
grepped it from a powerpc-kernel-deb).
The commands on a recent amd64 Squeeze were:
linux-src#>sudo make-kpkg --initrd --cross-compile powerpc-linux-gnu-
--arch powerpc --append-to-version +mikep5 kernel_image
linux-src#>sudo make KDEB_PKGVERSION=upstreamdebpkgcreatorNOINITRD.1.0
ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- deb-pkg
linux-src#>sudo make ARCH=powerpc CROSS32_COMPILE=powerpc-linux-gnu-
CROSS_COMPILE=powerpc-linux-gnu- zImage
All commands were launched within the same linux-src-tree.
readelf -h <image out of deb generated by make-kpkg> --> 0xc0000000
readelf -h <image out of deb generated by make deb-pkg> --> 0xc0000000
readelf -h arch/powerpc/boot/zImage --> desired 0x600000
I know, that 0x600000 works for my Wii. And I know, that the powerpc
images of the official packages have an Entry point address of 0xc0000000.
Nevertheless, I don't understand, why make-kpkg/make deb-pkg are
producing an image with a different address than using plain make commands.
Regards,
Marcus
[1]
http://www.gc-linux.org/wiki/Building_a_GameCube_Linux_Kernel_%28ARCH%3Dpowerpc%29
Reply to: