linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Atish Patra <Atish.Patra@wdc.com>
To: "paul.walmsley@sifive.com" <paul.walmsley@sifive.com>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
	"mick@ics.forth.gr" <mick@ics.forth.gr>,
	"palmer@sifive.com" <palmer@sifive.com>,
	"trini@konsulko.com" <trini@konsulko.com>,
	"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Anup Patel <Anup.Patel@wdc.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
	"merker@debian.org" <merker@debian.org>,
	"khilman@baylibre.com" <khilman@baylibre.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v4] RISC-V: Add an Image header that boot loader can parse.
Date: Fri, 28 Jun 2019 19:44:43 +0000	[thread overview]
Message-ID: <c0bdc25bc3aee9eee8bf9ebe561900b88df0540b.camel@wdc.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1906281207290.3867@viisi.sifive.com>

On Fri, 2019-06-28 at 12:09 -0700, Paul Walmsley wrote:
> 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?
> 

2MB/4MB alignment requirement is mandatory for current RISC-V kernel.
Anup had a patch that tried to remove that but not accepted yet.

https://patchwork.kernel.org/patch/10868465/


> 
> - Paul
> 
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
-- 
Regards,
Atish

  reply	other threads:[~2019-06-28 19:44 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
2019-06-28 19:44   ` Atish Patra [this message]
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=c0bdc25bc3aee9eee8bf9ebe561900b88df0540b.camel@wdc.com \
    --to=atish.patra@wdc.com \
    --cc=Anup.Patel@wdc.com \
    --cc=aou@eecs.berkeley.edu \
    --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=paul.walmsley@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).