From: Peter Maydell <peter.maydell@linaro.org>
To: Stafford Horne <shorne@gmail.com>
Cc: QEMU Development <qemu-devel@nongnu.org>, Jia Liu <proljc@gmail.com>
Subject: Re: [PATCH v2 4/4] hw/openrisc/openrisc_sim: Add support for initrd loading
Date: Thu, 17 Feb 2022 18:04:32 +0000 [thread overview]
Message-ID: <CAFEAcA8Gn50VHK41M36OzbSYE5Z7WEoOFqsBweFFgCvsoC6DKA@mail.gmail.com> (raw)
In-Reply-To: <20220210123403.2059926-5-shorne@gmail.com>
On Thu, 10 Feb 2022 at 13:13, Stafford Horne <shorne@gmail.com> wrote:
>
> The initrd passed via the command line is loaded into memory. It's
> location and size is then added to the device tree so the kernel knows
> where to find it.
>
> Signed-off-by: Stafford Horne <shorne@gmail.com>
> ---
> hw/openrisc/openrisc_sim.c | 32 +++++++++++++++++++++++++++++++-
> 1 file changed, 31 insertions(+), 1 deletion(-)
>
> diff --git a/hw/openrisc/openrisc_sim.c b/hw/openrisc/openrisc_sim.c
> index d7c26af82c..5354797e20 100644
> --- a/hw/openrisc/openrisc_sim.c
> +++ b/hw/openrisc/openrisc_sim.c
> @@ -187,6 +187,32 @@ static hwaddr openrisc_load_kernel(ram_addr_t ram_size,
> return 0;
> }
>
> +static hwaddr openrisc_load_initrd(Or1ksimState *s, const char *filename,
> + hwaddr load_start, uint64_t mem_size)
Indentation here is off.
Otherwise
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
thanks
-- PMM
next prev parent reply other threads:[~2022-02-17 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 12:33 [PATCH v2 0/4] OpenRISC Device Tree Support Stafford Horne
2022-02-10 12:34 ` [PATCH v2 1/4] hw/openrisc/openrisc_sim: Create machine state for or1ksim Stafford Horne
2022-02-10 12:34 ` [PATCH v2 2/4] hw/openrisc/openrisc_sim: Parameterize initialization Stafford Horne
2022-02-10 12:34 ` [PATCH v2 3/4] hw/openrisc/openrisc_sim; Add support for loading a device tree Stafford Horne
2022-02-10 12:34 ` [PATCH v2 4/4] hw/openrisc/openrisc_sim: Add support for initrd loading Stafford Horne
2022-02-17 18:04 ` Peter Maydell [this message]
2022-02-17 21:17 ` Stafford Horne
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=CAFEAcA8Gn50VHK41M36OzbSYE5Z7WEoOFqsBweFFgCvsoC6DKA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=proljc@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=shorne@gmail.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).