All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12411] New: Kernel zImage is actually a uImage
Date: Mon, 16 Dec 2019 14:53:01 +0000	[thread overview]
Message-ID: <bug-12411-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=12411

            Bug ID: 12411
           Summary: Kernel zImage is actually a uImage
           Product: buildroot
           Version: 2019.08.2
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: bradley.gamble at ncipher.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

I am currently building the Linux kernel with Buildroot and have been
outputting a working, bootable uImage file without issue.
A snippet of my config file:

    BR2_LINUX_KERNEL=y
    BR2_LINUX_KERNEL_CUSTOM_VERSION=y
    BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.1.9"
    BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
   
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="$(BR2_EXTERNAL)/board/linux-config/platform_defconfig"
    BR2_LINUX_KERNEL_DTS_SUPPORT=y
   
BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="$(BR2_EXTERNAL)/board/device-tree/platform.dts"

I wanted to instead output a zImage file. I added the following line to the
config:
    BR2_LINUX_KERNEL_ZIMAGE=y

After a full rebuild (for snity) a zImage file is output to the
"./output/images/" directory, however the file is not actually a zImage:
    $ file zImage 
    zImage: u-boot legacy uImage, Linux-5.1.9, Linux/PowerPC, OS Kernel Image
(gzip), 4304978 bytes, Mon Dec 16 14:39:07 2019, Load Address: 0x00000000,
Entry Point: 0x00000000, Header CRC: 0x43D672C7, Data CRC: 0x4FF108C3

I am able to manually truncate the first 64 bytes which will give me a working
zImage file, however I expected Buildroot to give me an actual zImage file, not
requiring any manual modification.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2019-12-16 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16 14:53 bugzilla at busybox.net [this message]
2019-12-16 15:28 ` [Buildroot] [Bug 12411] Kernel zImage is actually a uImage bugzilla at busybox.net
2019-12-17 15:38 ` bugzilla at busybox.net

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-12411-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.