From: Paul Walmsley <paul.walmsley@sifive.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: mark.rutland@arm.com, Albert Ou <aou@eecs.berkeley.edu>,
Anup Patel <anup@brainfault.org>,
Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org, Zong Li <zong@andestech.com>,
merker@debian.org, linux-riscv@lists.infradead.org
Subject: Re: [v2 PATCH] RISC-V: Add a PE/COFF compliant Image header.
Date: Fri, 17 May 2019 10:39:31 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1905171017510.9104@viisi.sifive.com> (raw)
In-Reply-To: <20190501195607.32553-1-atish.patra@wdc.com>
On Wed, 1 May 2019, Atish Patra wrote:
> Currently, last stage boot loaders such as U-Boot can accept only
> uImage which is an unnecessary additional step in automating boot flows.
>
> Add a PE/COFF compliant image header that boot loaders can parse and
> directly load kernel flat Image. The existing booting methods will continue
> to work as it is.
One other thought: as I think you or someone else may have pointed out,
this isn't the PE/COFF header itself, but rather an ersatz DOS stub
header, that is apparently quite close to what some EFI bootloaders
require. So from that point of view, it's probably best to just write in
the patch description that the idea is to add something that resembles an
MS-DOS stub header, and that the motivations are that:
1. it resembles what ARM64 is doing, and there's not much point in
inventing another boot header format that's completely different
2. it can be easily converted into an MS-DOS header that some EFI
bootloaders apparently require, by tweaking a few bytes at the beginning
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-05-17 17:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 19:56 [v2 PATCH] RISC-V: Add a PE/COFF compliant Image header Atish Patra
2019-05-05 0:37 ` Karsten Merker
2019-05-11 20:57 ` Karsten Merker
2019-05-13 22:31 ` Paul Walmsley
2019-05-13 23:18 ` Atish Patra
2019-05-14 0:09 ` Paul Walmsley
2019-05-14 0:34 ` Atish Patra
2019-05-14 0:39 ` Paul Walmsley
2019-05-14 1:13 ` Atish Patra
2019-05-16 16:20 ` Paul Walmsley
2019-05-23 18:35 ` Atish Patra
2019-05-23 18:45 ` Paul Walmsley
2019-05-17 17:39 ` Paul Walmsley [this message]
2019-05-17 19:00 ` Atish Patra
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=alpine.DEB.2.21.9999.1905171017510.9104@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=merker@debian.org \
--cc=palmer@sifive.com \
--cc=zong@andestech.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).