From: Kevin Hilman <khilman@baylibre.com>
To: Atish Patra <atish.patra@wdc.com>, linux-kernel@vger.kernel.org
Cc: Atish Patra <atish.patra@wdc.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Anup Patel <Anup.Patel@wdc.com>, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
Nick Kossifidis <mick@ics.forth.gr>,
Palmer Dabbelt <palmer@sifive.com>, Zong Li <zong@andestech.com>,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
marek.vasut@gmail.com, catalin.marinas@arm.com,
will.deacon@arm.com, trini@konsulko.com,
paul.walmsley@sifive.com
Subject: Re: [v3 PATCH] RISC-V: Add a PE/COFF compliant Image header.
Date: Wed, 05 Jun 2019 09:00:42 -0700 [thread overview]
Message-ID: <7hef48ggyd.fsf@baylibre.com> (raw)
In-Reply-To: <20190523183516.583-1-atish.patra@wdc.com>
Atish Patra <atish.patra@wdc.com> writes:
> 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.
>
> Another goal of this header is to support EFI stub for RISC-V in future.
> EFI specification needs PE/COFF image header in the beginning of the kernel
> image in order to load it as an EFI application. In order to support
> EFI stub, code0 should be replaced with "MZ" magic string and res5(at
> offset 0x3c) should point to the rest of the PE/COFF header (which will
> be added during EFI support).
>
> This patch is based on ARM64 boot image header and provides an opprtunity
> to combine both ARM64 & RISC-V image headers.
>
> Tested on both QEMU and HiFive Unleashed using OpenSBI + U-Boot + Linux.
>
> Signed-off-by: Atish Patra <atish.patra@wdc.com>
Tested booti support on HiFive Unleashed using OpenSBI + U-Boot (master
branch) + Linux.
Tested-by: Kevin Hilman <khilman@baylibre.com>
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Atish Patra <atish.patra@wdc.com>, linux-kernel@vger.kernel.org
Cc: mark.rutland@arm.com, Jonathan Corbet <corbet@lwn.net>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-doc@vger.kernel.org, catalin.marinas@arm.com,
Anup Patel <Anup.Patel@wdc.com>,
will.deacon@arm.com, Zong Li <zong@andestech.com>,
Atish Patra <atish.patra@wdc.com>,
Palmer Dabbelt <palmer@sifive.com>,
trini@konsulko.com, paul.walmsley@sifive.com,
Nick Kossifidis <mick@ics.forth.gr>,
linux-riscv@lists.infradead.org, marek.vasut@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [v3 PATCH] RISC-V: Add a PE/COFF compliant Image header.
Date: Wed, 05 Jun 2019 09:00:42 -0700 [thread overview]
Message-ID: <7hef48ggyd.fsf@baylibre.com> (raw)
In-Reply-To: <20190523183516.583-1-atish.patra@wdc.com>
Atish Patra <atish.patra@wdc.com> writes:
> 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.
>
> Another goal of this header is to support EFI stub for RISC-V in future.
> EFI specification needs PE/COFF image header in the beginning of the kernel
> image in order to load it as an EFI application. In order to support
> EFI stub, code0 should be replaced with "MZ" magic string and res5(at
> offset 0x3c) should point to the rest of the PE/COFF header (which will
> be added during EFI support).
>
> This patch is based on ARM64 boot image header and provides an opprtunity
> to combine both ARM64 & RISC-V image headers.
>
> Tested on both QEMU and HiFive Unleashed using OpenSBI + U-Boot + Linux.
>
> Signed-off-by: Atish Patra <atish.patra@wdc.com>
Tested booti support on HiFive Unleashed using OpenSBI + U-Boot (master
branch) + Linux.
Tested-by: Kevin Hilman <khilman@baylibre.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Atish Patra <atish.patra@wdc.com>, linux-kernel@vger.kernel.org
Cc: mark.rutland@arm.com, Jonathan Corbet <corbet@lwn.net>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-doc@vger.kernel.org, catalin.marinas@arm.com,
Anup Patel <Anup.Patel@wdc.com>,
will.deacon@arm.com, Zong Li <zong@andestech.com>,
Atish Patra <atish.patra@wdc.com>,
Palmer Dabbelt <palmer@sifive.com>,
trini@konsulko.com, paul.walmsley@sifive.com,
Nick Kossifidis <mick@ics.forth.gr>,
linux-riscv@lists.infradead.org, marek.vasut@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [v3 PATCH] RISC-V: Add a PE/COFF compliant Image header.
Date: Wed, 05 Jun 2019 09:00:42 -0700 [thread overview]
Message-ID: <7hef48ggyd.fsf@baylibre.com> (raw)
In-Reply-To: <20190523183516.583-1-atish.patra@wdc.com>
Atish Patra <atish.patra@wdc.com> writes:
> 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.
>
> Another goal of this header is to support EFI stub for RISC-V in future.
> EFI specification needs PE/COFF image header in the beginning of the kernel
> image in order to load it as an EFI application. In order to support
> EFI stub, code0 should be replaced with "MZ" magic string and res5(at
> offset 0x3c) should point to the rest of the PE/COFF header (which will
> be added during EFI support).
>
> This patch is based on ARM64 boot image header and provides an opprtunity
> to combine both ARM64 & RISC-V image headers.
>
> Tested on both QEMU and HiFive Unleashed using OpenSBI + U-Boot + Linux.
>
> Signed-off-by: Atish Patra <atish.patra@wdc.com>
Tested booti support on HiFive Unleashed using OpenSBI + U-Boot (master
branch) + Linux.
Tested-by: Kevin Hilman <khilman@baylibre.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-05 16:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 18:35 [v3 PATCH] RISC-V: Add a PE/COFF compliant Image header Atish Patra
2019-05-23 18:35 ` Atish Patra
2019-05-23 18:35 ` Atish Patra
2019-05-23 21:09 ` Ard Biesheuvel
2019-05-23 21:09 ` Ard Biesheuvel
2019-05-23 21:09 ` Ard Biesheuvel
2019-05-24 0:16 ` Atish Patra
2019-05-24 0:16 ` Atish Patra
2019-05-24 0:16 ` Atish Patra
2019-06-05 16:00 ` Kevin Hilman [this message]
2019-06-05 16:00 ` Kevin Hilman
2019-06-05 16:00 ` Kevin Hilman
2019-06-05 16:26 ` Mark Rutland
2019-06-05 16:26 ` Mark Rutland
2019-06-05 16:26 ` Mark Rutland
2019-06-06 22:41 ` Atish Patra
2019-06-06 22:41 ` Atish Patra
2019-06-06 22:41 ` 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=7hef48ggyd.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=Anup.Patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mick@ics.forth.gr \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=trini@konsulko.com \
--cc=will.deacon@arm.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 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.