All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Mark Langsdorf" <mark.langsdorf@calxeda.com>,
	"Alexander Graf" <agraf@suse.de>,
	"Fabien Chouteau" <chouteau@adacore.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Blue Swirl" <blauwirbel@gmail.com>,
	"Michael Walle" <michael@walle.cc>,
	"Hervé Poussineau" <hpoussin@reactos.org>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Anthony Liguori" <anthony@codemonkey.ws>,
	"New World" <qemu-ppc@nongnu.org>,
	"Richard Henderson" <rth@twiddle.net>,
	"Aurelien Jarno" <aurelien@aurel32.net>,
	"Andreas Färber" <andreas.faerber@web.de>
Subject: Re: [Qemu-devel] [PATCH] turn firmware image filename into a machine option
Date: Tue, 01 Oct 2013 17:28:34 +0200	[thread overview]
Message-ID: <524AEA22.9000702@redhat.com> (raw)
In-Reply-To: <CAFEAcA_tU89ZO5LunwFyqVxxs4uKm8D-u6KD6pZRxP-NiJvR2g@mail.gmail.com>

Il 01/10/2013 17:12, Peter Maydell ha scritto:
>> > I just need some way to have different default firmware images for
>> > different pc machine type versions.  Requests to considering other
>> > firmware loading needs (such as the two images needed for sPAPR) when
>> > doing this is reasonable.  Blaming me for how inconistent qemu's
>> > firmware loading is today is not ok.
> You're defining new command line syntax -- it seems reasonable
> to think about what it ought to actually mean rather than just
> saying "it should mean the same collection of random stuff
> that -bios means". If you're going to do that you should just stick
> with -bios...

What it ought to mean could be "the ROM that bootstraps the machine by
loading stuff from a drive (could be NAND, SD or a hardware component
such as virtio/IDE/SCSI)".  But most machines sidestep this by loading
the kernel directly in RAM.

Paolo

  reply	other threads:[~2013-10-01 15:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01  9:39 [Qemu-devel] [PATCH] turn firmware image filename into a machine option Gerd Hoffmann
2013-10-01 10:55 ` Peter Maydell
2013-10-01 11:22   ` Gerd Hoffmann
2013-10-01 11:32     ` Peter Maydell
2013-10-01 12:16       ` Gerd Hoffmann
2013-10-01 12:20         ` Andreas Färber
2013-10-01 13:41           ` Gerd Hoffmann
2013-10-01 13:46             ` Andreas Färber
2013-10-01 14:23               ` Alexey Kardashevskiy
2013-10-01 14:40                 ` Gerd Hoffmann
2013-10-01 14:45                   ` Alexander Graf
2013-10-01 21:23                 ` Benjamin Herrenschmidt
2013-10-02  1:18                   ` Alexey Kardashevskiy
2013-10-01 13:00         ` Peter Maydell
2013-10-01 14:57           ` Paolo Bonzini
2013-10-01 15:05           ` Gerd Hoffmann
2013-10-01 15:12             ` Peter Maydell
2013-10-01 15:28               ` Paolo Bonzini [this message]
2013-10-01 15:42                 ` Anthony Liguori
     [not found] ` <524AB29F.3030906@suse.de>
2013-10-01 13:32   ` Gerd Hoffmann

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=524AEA22.9000702@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=andreas.faerber@web.de \
    --cc=anthony@codemonkey.ws \
    --cc=aurelien@aurel32.net \
    --cc=blauwirbel@gmail.com \
    --cc=chouteau@adacore.com \
    --cc=hpoussin@reactos.org \
    --cc=kraxel@redhat.com \
    --cc=mark.langsdorf@calxeda.com \
    --cc=michael@walle.cc \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rth@twiddle.net \
    /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.