From: Paul Walmsley <paul.walmsley@sifive.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"trini@konsulko.com" <trini@konsulko.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Jonathan Corbet <corbet@lwn.net>,
Kevin Hilman <khilman@baylibre.com>,
Anup Patel <Anup.Patel@wdc.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"will.deacon@arm.com" <will.deacon@arm.com>,
Nick Kossifidis <mick@ics.forth.gr>,
Palmer Dabbelt <palmer@sifive.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
Karsten Merker <merker@debian.org>,
linux-riscv@lists.infradead.org,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4] RISC-V: Add an Image header that boot loader can parse.
Date: Fri, 28 Jun 2019 12:09:04 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1906281207290.3867@viisi.sifive.com> (raw)
In-Reply-To: <20190606230800.19932-1-atish.patra@wdc.com>
On Thu, 6 Jun 2019, Atish Patra wrote:
> Currently, the last stage boot loaders such as U-Boot can accept only
> uImage which is an unnecessary additional step in automating boot
> process.
>
> Add an image header that boot loader understands and boot Linux from
> flat Image directly.
...
> +#if __riscv_xlen == 64
> + /* Image load offset(2MB) from start of RAM */
> + .dword 0x200000
> +#else
> + /* Image load offset(4MB) from start of RAM */
> + .dword 0x400000
> +#endif
Is there a rationale behind these load offset values?
- 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-06-28 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 23:08 [PATCH v4] RISC-V: Add an Image header that boot loader can parse Atish Patra
2019-06-28 19:09 ` Paul Walmsley [this message]
2019-06-28 19:44 ` Atish Patra
2019-07-11 19:42 ` Paul Walmsley
2019-07-11 21:42 ` 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.1906281207290.3867@viisi.sifive.com \
--to=paul.walmsley@sifive.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=khilman@baylibre.com \
--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=merker@debian.org \
--cc=mick@ics.forth.gr \
--cc=palmer@sifive.com \
--cc=trini@konsulko.com \
--cc=will.deacon@arm.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).