From: Palmer Dabbelt <palmer@sifive.com>
To: mail@aurabindo.in
Cc: Troy Benjegerdes <troy.benjegerdes@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [RFC] buildtar: add case for riscv architecture
Date: Sat, 14 Sep 2019 05:59:55 -0700 (PDT) [thread overview]
Message-ID: <mhng-ed262582-dc00-41fe-9be5-2487297f2432@palmer-si-x1e> (raw)
In-Reply-To: <X9f9LozkDQUeBwasTsPlPseP6ZT5yJHNY2GcIgoAgNQJPuFAyYimnDXTJUqxfrZ64GOIl5-uPh07NZnD1pi4uWhCpZvbu9khOW6rEq5P4jU=@aurabindo.in>
On Wed, 11 Sep 2019 05:54:07 PDT (-0700), mail@aurabindo.in wrote:
>
>
>> None of the available RiscV platforms that I’m aware of use compressed images, unless there are some new bootloaders I haven’t seen yet.
>>
>
> I noticed that default build image is Image.gz, which is why I thought its a good idea to copy it into the tarball. Does such a copy not make sense at this point ?
Image.gz can't be booted directly: it's just Image that's been compressed with
the standard gzip command. A bootloader would have to decompress that image
before loading it into memory, which requires extra bootloader support.
Contrast that with the zImage style images (which are vmlinuz on x86), which
are self-extracting and therefor require no bootloader support. The examples
for u-boot all use the "booti" command, which expects uncompressed images.
Poking around I couldn't figure out a way to have u-boot decompress the images,
but that applies to arm64 as well so I'm not sure if I'm missing something.
If I was doing this, I'd copy over arch/riscv/boot/Image and call it
"/boot/image-${KERNELRELEASE}", as calling it vmlinuz is a bit confusing to me
because I'd expect vmlinuz to be a self-extracting compressed executable and
not a raw gzip file.
next prev parent reply other threads:[~2019-09-14 12:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 7:07 [RFC] buildtar: add case for riscv architecture Aurabindo Jayamohanan
2019-09-11 9:05 ` Troy Benjegerdes
2019-09-11 12:54 ` Aurabindo Jayamohanan
2019-09-14 12:59 ` Palmer Dabbelt [this message]
2019-09-14 13:05 ` Anup Patel
2019-09-14 19:27 ` Palmer Dabbelt
2019-09-17 9:35 ` Aurabindo Jayamohanan
2019-09-20 22:40 ` Palmer Dabbelt
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=mhng-ed262582-dc00-41fe-9be5-2487297f2432@palmer-si-x1e \
--to=palmer@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mail@aurabindo.in \
--cc=paul.walmsley@sifive.com \
--cc=troy.benjegerdes@sifive.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).