From: schwab@suse.de (Andreas Schwab)
To: linux-riscv@lists.infradead.org
Subject: Risc-V, qemu, and initrd
Date: Thu, 21 Jun 2018 16:30:55 +0200 [thread overview]
Message-ID: <mvmpo0kjjog.fsf@suse.de> (raw)
In-Reply-To: <64d50cba-8215-763c-a5c9-f384b2901d01@roeck-us.net> (Guenter Roeck's message of "Wed, 20 Jun 2018 23:11:37 -0700")
On Jun 20 2018, Guenter Roeck <linux@roeck-us.net> wrote:
> Loking into the kernel source, I found arch/riscv/kernel/setup.c:setup_initrd().
> Debugging shows that initrd_start and initrd_end is set correctly in
> drivers/of/fdt.c:early_init_dt_check_for_initrd(), but overwritten with the value
> of __initramfs_start / __initramfs_size in setup_initrd(). This doesn't make
> sense to me, since populate_rootfs() tries to populate the root file system
> from both __initramfs_start and initrd_start.
>
> Has anyone else noticed this problem ? Any idea what I need to do to load an
> initrd with the -initrd option of qemu ?
Try removing the offending lines in setup_initrd.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab at suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-06-21 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 6:11 Risc-V, qemu, and initrd Guenter Roeck
2018-06-21 8:11 ` Atish Patra
2018-06-21 14:30 ` Andreas Schwab [this message]
2018-06-21 14:48 ` Guenter Roeck
2018-06-21 14:52 ` Christoph Hellwig
2018-06-21 16:34 ` Guenter Roeck
2018-06-21 17:33 ` Guenter Roeck
2018-06-21 17:55 ` Christoph Hellwig
2018-06-21 22:08 ` Guenter Roeck
2018-06-22 5:38 ` Christoph Hellwig
2018-06-22 16:34 ` Guenter Roeck
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=mvmpo0kjjog.fsf@suse.de \
--to=schwab@suse.de \
--cc=linux-riscv@lists.infradead.org \
/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.