From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 205889] New: CONFIG_PPC_85xx with CONFIG_CORENET_GENERIC outputs uImage instead of zImage
Date: Tue, 17 Dec 2019 15:37:36 +0000 [thread overview]
Message-ID: <bug-205889-206035@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=205889
Bug ID: 205889
Summary: CONFIG_PPC_85xx with CONFIG_CORENET_GENERIC outputs
uImage instead of zImage
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 5.5
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PPC-32
Assignee: platform_ppc-32@kernel-bugs.osdl.org
Reporter: bradley.gamble@ncipher.com
Regression: No
Attempting a PowerPC Linux kernel build with the config options
"CONFIG_PPC_85xx=y" and "CONFIG_CORENET_GENERIC=y" will output a file named
"zImage", however this file is actually a "uImage" formatted file.
This can be replicated with this minimal defconfig:
CONFIG_PPC_85xx=y
CONFIG_CORENET_GENERIC=y
If I perform a build with one of these options I am given a valid zImage file:
$ file arch/powerpc/boot/zImage
arch/powerpc/boot/zImage: ELF 32-bit MSB executable, PowerPC or cisco 4500,
version 1 (SYSV), statically linked, not stripped
However performing the same build with both config options enabled gives an
incorrectly formatted image:
$ file arch/powerpc/boot/zImage
arch/powerpc/boot/zImage: u-boot legacy uImage, Linux-5.5.0-rc2-gea200dec5,
Linux/PowerPC, OS Kernel Image (gzip), 1366142 bytes, Tue Dec 17 15:30:22 2019,
Load Address: 0x00000000, Entry Point: 0x00000000, Header CRC: 0x99D350A0, Data
CRC: 0xC9090D33
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2019-12-17 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 15:37 bugzilla-daemon [this message]
2019-12-18 11:37 ` [Bug 205889] CONFIG_PPC_85xx with CONFIG_CORENET_GENERIC outputs uImage instead of zImage bugzilla-daemon
2019-12-20 11:55 ` bugzilla-daemon
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=bug-205889-206035@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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.