From: "Andreas Färber" <afaerber@suse.de>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-devel@nongnu.org, agraf@suse.de
Cc: qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1] virtex_ml507: Add support for loading initrd images
Date: Mon, 03 Feb 2014 19:47:47 +0100 [thread overview]
Message-ID: <52EFE453.8020705@suse.de> (raw)
In-Reply-To: <1391440820-4736-1-git-send-email-edgar.iglesias@gmail.com>
Am 03.02.2014 16:20, schrieb Edgar E. Iglesias:
> From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
>
> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
> ---
> hw/ppc/virtex_ml507.c | 34 +++++++++++++++++++++++++++++++++-
> 1 file changed, 33 insertions(+), 1 deletion(-)
>
> diff --git a/hw/ppc/virtex_ml507.c b/hw/ppc/virtex_ml507.c
> index bdb057e..19083d4 100644
> --- a/hw/ppc/virtex_ml507.c
> +++ b/hw/ppc/virtex_ml507.c
> @@ -166,6 +166,19 @@ static int xilinx_load_device_tree(hwaddr addr,
> if (!fdt) {
> return 0;
> }
> +
> + r = qemu_fdt_setprop_cell(fdt, "/chosen", "linux,initrd-start",
> + initrd_base);
> + if (r < 0) {
> + error_report("couldn't set /chosen/linux,initrd-start'");
Both this ...
> + }
> +
> + r = qemu_fdt_setprop_cell(fdt, "/chosen", "linux,initrd-end",
> + (initrd_base + initrd_size));
> + if (r < 0) {
> + error_report("couldn't set /chosen/linux,initrd-end'");
... and the other error_report() have either a stray trailing
single-quote or one missing before the path.
> + }
> +
> r = qemu_fdt_setprop_string(fdt, "/chosen", "bootargs", kernel_cmdline);
> if (r < 0)
> fprintf(stderr, "couldn't set /chosen/bootargs\n");
> @@ -179,6 +192,8 @@ static void virtex_init(QEMUMachineInitArgs *args)
> const char *cpu_model = args->cpu_model;
> const char *kernel_filename = args->kernel_filename;
> const char *kernel_cmdline = args->kernel_cmdline;
> + hwaddr initrd_base = 0;
> + int initrd_size = 0;
> MemoryRegion *address_space_mem = get_system_memory();
> DeviceState *dev;
> PowerPCCPU *cpu;
> @@ -242,10 +257,27 @@ static void virtex_init(QEMUMachineInitArgs *args)
>
> boot_info.ima_size = kernel_size;
>
> + /* Load initrd. */
> + if (args->initrd_filename) {
> + initrd_base = high = ROUND_UP(high, 4);
> + initrd_size = load_image_targphys(args->initrd_filename,
> + high, ram_size - high);
> +
> + if (initrd_size < 0) {
> + error_report("couldn't load ram disk '%s'\n",
And here's a stray \n.
Andreas
> + args->initrd_filename);
> + exit(1);
> + }
> + high = ROUND_UP(high + initrd_size, 4);
> + }
> +
> /* Provide a device-tree. */
> boot_info.fdt = high + (8192 * 2);
> boot_info.fdt &= ~8191;
> - xilinx_load_device_tree(boot_info.fdt, ram_size, 0, 0, kernel_cmdline);
> +
> + xilinx_load_device_tree(boot_info.fdt, ram_size,
> + initrd_base, initrd_size,
> + kernel_cmdline);
> }
> env->load_info = &boot_info;
> }
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-02-03 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 15:20 [Qemu-devel] [PATCH v1] virtex_ml507: Add support for loading initrd images Edgar E. Iglesias
2014-02-03 18:36 ` Alexander Graf
2014-02-03 18:47 ` Andreas Färber [this message]
2014-02-03 19:02 ` Alexander Graf
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=52EFE453.8020705@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=edgar.iglesias@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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 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).