From: Tom Rini <trini@ti.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH 4/4] ti33x, ti43x, omap-a15: switch KERNEL_IMAGETYPE to zImage by default
Date: Tue, 24 Sep 2013 09:00:48 -0400 [thread overview]
Message-ID: <52418D00.8060904@ti.com> (raw)
In-Reply-To: <20130924043924.GJ4390@edge>
On 09/24/2013 12:39 AM, Denys Dmytriyenko wrote:
> On Tue, Sep 24, 2013 at 03:36:47AM +0000, Cooper Jr., Franklin wrote:
>> What is the benefit of this switch?
>>
>> Although outdated a lot of posts talking about uImage vs zImage seems to
>> favor uImage due to additional functionality that it provides.
>
> I guess this is a more generic question addressed to Tom...
There are two sides to it. On the zImage side, it's what the kernel
produces normally, without needing other tools, so it's vastly preferred
by the majority of kernel developers. On the production side, uImages
provide useful things like a checksums and the ability to detect
overlaps. If we enabled FIT images, we could go so far as to allow for
cryptographically signed images and configurations (what FIT calls a
kernel+fdt(+optional ramdisk)).
For community oriented things like this, zImage is best and for
production, it's up to the designer on what's important and what's not.
--
Tom
next prev parent reply other threads:[~2013-09-24 13:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 2:27 [PATCH 1/4] linux*: don't force KERNEL_IMAGETYPE from recipes, let machine config set it Denys Dmytriyenko
2013-09-24 2:27 ` [PATCH 2/4] u-boot-ti-staging: update to the latest 2013.10-rc2 and make it the default Denys Dmytriyenko
2013-09-24 12:48 ` Cooper Jr., Franklin
2013-09-24 13:52 ` Maupin, Chase
2013-09-24 2:27 ` [PATCH 3/4] linux-ti-staging: make 3.12-rc the default for supported platforms, drop omap5-sevm.dtb Denys Dmytriyenko
2013-09-24 3:26 ` Denys Dmytriyenko
2013-09-24 12:51 ` Cooper Jr., Franklin
2013-09-24 13:52 ` Maupin, Chase
2013-09-24 2:27 ` [PATCH 4/4] ti33x, ti43x, omap-a15: switch KERNEL_IMAGETYPE to zImage by default Denys Dmytriyenko
2013-09-24 3:36 ` Cooper Jr., Franklin
2013-09-24 4:39 ` Denys Dmytriyenko
2013-09-24 13:00 ` Tom Rini [this message]
2013-09-24 13:49 ` Maupin, Chase
2013-09-24 14:03 ` Tom Rini
2013-09-24 13:53 ` Maupin, Chase
2013-09-24 12:46 ` [PATCH 1/4] linux*: don't force KERNEL_IMAGETYPE from recipes, let machine config set it Cooper Jr., Franklin
2013-09-24 12:53 ` Dmytriyenko, Denys
2013-09-24 13:02 ` Cooper Jr., Franklin
2013-09-24 13:16 ` Dmytriyenko, Denys
2013-09-24 13:33 ` Cooper Jr., Franklin
2013-09-24 13:51 ` Maupin, Chase
2013-09-24 14:00 ` Cooper Jr., Franklin
2013-09-24 13:51 ` Maupin, Chase
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52418D00.8060904@ti.com \
--to=trini@ti.com \
--cc=denys@ti.com \
--cc=meta-ti@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.