On Thu, Jul 24, 2008 at 9:08 PM, Milton Miller <[EMAIL PROTECTED]> wrote: > >> Currently, tarball builds for powerpc kernels don't have any boot >> images (other than vmlinux) present. >> >> Add support for powerpc builds in the buildtar script, to include >> a few default images. >> >> Signed-off-by: Jeremy Kerr <jk at ozlabs.org> >> >> --- >> RFC: any requests for more/less boot images? >> > .. >> + for img in zImage zImage.pseries zImage.iseries \ >> + dtbImage dtbImage.ps3 > > Yes. How about all dtbImage, zImage, cuboot, treeboot, etc > that are newer than vmlinux?
dtbImage is not a buildable image. Neither is cuImage, treeImage or simpleImage. All of those targets embed a device tree which is specified by adding the .dts filename to the target name. so, for example, 'make cuImage' fails. Instead you do 'make cuImage.lite5200b' which pulls in dts/lite5200b.dts. Also, zImage is a 'meta' target that builds all the default image targets (the $image-y list). The zImage is actually just a symlink to the first file in the list of default images. So zImage can actually point to any kind of kernel image depending on how the kernel is configured. I wonder if we should just remove the zImage file entirely, or at least make it always linked to one particular image type. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
