lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 28 Jun 2019 19:44:43 +0000
From:   Atish Patra <Atish.Patra@....com>
To:     "paul.walmsley@...ive.com" <paul.walmsley@...ive.com>
CC:     "corbet@....net" <corbet@....net>,
        "mick@....forth.gr" <mick@....forth.gr>,
        "palmer@...ive.com" <palmer@...ive.com>,
        "trini@...sulko.com" <trini@...sulko.com>,
        "aou@...s.berkeley.edu" <aou@...s.berkeley.edu>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "will.deacon@....com" <will.deacon@....com>,
        "catalin.marinas@....com" <catalin.marinas@....com>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
        Anup Patel <Anup.Patel@....com>,
        "mark.rutland@....com" <mark.rutland@....com>,
        "marek.vasut@...il.com" <marek.vasut@...il.com>,
        "merker@...ian.org" <merker@...ian.org>,
        "khilman@...libre.com" <khilman@...libre.com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>
Subject: Re: [PATCH v4] RISC-V: Add an Image header that boot loader can
 parse.

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@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
-- 
Regards,
Atish

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ