All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
To: Tom Rini <trini@konsulko.com>
Cc: Rick Chen <rick@andestech.com>, Bin Meng <bmeng.cn@gmail.com>,
	Leo Yu-Chi Liang <ycliang@andestech.com>,
	Sean Anderson <seanga2@gmail.com>,
	Pragnesh Patel <pragnesh.patel@sifive.com>,
	Zong Li <zong.li@sifive.com>,
	Alexandre Ghiti <alexandre.ghiti@canonical.com>,
	u-boot@lists.denx.de,
	Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Subject: [PATCH v2 0/2] board: sifive: unmatched: use zero copy for initrd
Date: Tue,  9 Nov 2021 15:45:59 +0100	[thread overview]
Message-ID: <20211109144601.92326-1-heinrich.schuchardt@canonical.com> (raw)

Booting Ubuntu Impish showed the following output:

    relocaddr   = 0x00000000fff60000

    Loading Ramdisk to fa118000, end fffff19d ...

The initrd is overwriting the U-Boot binary. Booting fails.

There is no need to copy the initrd from $ramdisk_addr_r.
Set init_high = ~0UL to use zero copy. Do the same for the device tree.

Rearrange all load addresses:

* put the small files below $kernel_addr_r to not limit the kernel size.
* ramdisk_addr_r should be the highest of all loading addresses to
  avoid limiting the size of the initial RAM disk.

v2:
	rearrange all more addresses

Heinrich Schuchardt (2):
  board: sifive: unmatched: use zero copy for initrd
  board: sifive: unmatched: rearrange load addresses

 include/configs/sifive-unmatched.h | 17 ++++++++++-------
 1 file changed, 10 insertions(+), 7 deletions(-)

-- 
2.32.0


             reply	other threads:[~2021-11-09 14:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09 14:45 Heinrich Schuchardt [this message]
2021-11-09 14:46 ` [PATCH v2 1/2] board: sifive: unmatched: use zero copy for initrd Heinrich Schuchardt
2021-11-09 15:46   ` Tom Rini
2021-11-09 15:50     ` Heinrich Schuchardt
2021-11-09 16:07       ` Tom Rini
2021-11-09 16:27         ` Heinrich Schuchardt
2021-11-09 17:11           ` Tom Rini
2021-11-11  9:46             ` David Abdurachmanov
2021-11-11 12:26               ` LMB and UEFI memory management not integrated Heinrich Schuchardt
2021-11-09 14:46 ` [PATCH v2 2/2] board: sifive: unmatched: rearrange load addresses Heinrich Schuchardt
2021-11-09 15:43   ` Tom Rini
2021-11-09 15:46     ` Heinrich Schuchardt
2021-11-09 15:48       ` Tom Rini

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=20211109144601.92326-1-heinrich.schuchardt@canonical.com \
    --to=heinrich.schuchardt@canonical.com \
    --cc=alexandre.ghiti@canonical.com \
    --cc=bmeng.cn@gmail.com \
    --cc=pragnesh.patel@sifive.com \
    --cc=rick@andestech.com \
    --cc=seanga2@gmail.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=ycliang@andestech.com \
    --cc=zong.li@sifive.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.