From: Troy Benjegerdes <troy.benjegerdes@sifive.com>
To: Aurabindo Jayamohanan <mail@aurabindo.in>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>
Subject: Re: [RFC] buildtar: add case for riscv architecture
Date: Wed, 11 Sep 2019 04:05:25 -0500 [thread overview]
Message-ID: <8EF02DA7-46D3-4EA8-96FB-27708BF25DAC@sifive.com> (raw)
In-Reply-To: <NwVOGH2ZdDQaDK35QUy7y8GS__G8IYSIUUIBAJsimZq5BgvI3SzLS3uY6fV7Pgppq-RTRHzpT-8KrsLjDN74CPWwHTCWoSgHkGbeJNvyS30=@aurabindo.in>
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.
> On Sep 11, 2019, at 2:07 AM, Aurabindo Jayamohanan <mail@aurabindo.in> wrote:
>
> Hi,
>
> I would like to know if something extra needs to be done other than copying compressed kernel image, when making tar package for riscv architecture. Please see the attached patch.
>
> --
>
> Thanks and Regards,
> Aurabindo Jayamohanan
> <0001-buildtar-add-riscv-case.patch>_______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-09-11 9:05 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 [this message]
2019-09-11 12:54 ` Aurabindo Jayamohanan
2019-09-14 12:59 ` Palmer Dabbelt
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=8EF02DA7-46D3-4EA8-96FB-27708BF25DAC@sifive.com \
--to=troy.benjegerdes@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=palmer@sifive.com \
--cc=paul.walmsley@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).