linux-kernel - Re: [RFC,PATCH] scripts/package: add powerpc images to tarball

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fa686aa40807252155l4f785920qdb14d117067b30f4@mail.gmail.com>
Date:	Sat, 26 Jul 2008 00:55:31 -0400
From:	"Grant Likely" <grant.likely@...retlab.ca>
To:	"Milton Miller" <miltonm@....com>
Cc:	"Jeremy Kerr" <jk@...abs.org>, linuxppc-dev@...abs.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC,PATCH] scripts/package: add powerpc images to tarball

On Thu, Jul 24, 2008 at 9:08 PM, Milton Miller <miltonm@....com> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/