From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Alexander Graf <agraf@suse.de>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"<qemu-ppc@nongnu.org>" <qemu-ppc@nongnu.org>,
"Scott Wood" <scottwood@freescale.com>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Andreas Färber" <afaerber@suse.de>,
"Artyom Tarasenko" <atar4qemu@gmail.com>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 3/3] PPC PReP: can run without bios image
Date: Sat, 6 Apr 2013 22:07:16 +0200 [thread overview]
Message-ID: <20130406200716.GA4430@smtp.vpn> (raw)
In-Reply-To: <2B42F309-792B-4CD6-B2A1-8F82B310E0D8@suse.de>
On Sat, Apr 06, 2013 at 01:38:52PM +0200, Alexander Graf wrote:
>
> On 06.04.2013, at 13:27, Peter Maydell wrote:
>
> > On 6 April 2013 10:07, Alexander Graf <agraf@suse.de> wrote:
> >> On ARM, look at highbank. Because we're not running we're lacking
> >> a monitor mode blob that provides sys calls for flushing caches.
> >> Thus today the highbank machine doesn't boot anymore with Linux.
> >> If we ran firmware like the real board, that would provide for the
> >> sys call.
> >
> > We also flat out don't implement enough monitor mode to allow
> > a hypothetical firmware blob to work.
>
> Why don't we implement enough monitor mode? Because we're not running firmware :). It's a chicken and egg thing. Bottom line is that Linux validly expects that firmware exists. If we don't run firmware, we diverge, thus we potentially break.
Hi guys, A question - For linux kernels that depend on preivous stages to setup
HW state. What is the prefered way to handle it?
In particular, if the boot loader chain depends on for example a boot rom
that is not Open Source. Is providing a QEMU specific loader in pc-bios/ a good
option?
Cheers,
Edgar
next prev parent reply other threads:[~2013-04-06 20:07 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 16:40 [Qemu-devel] [PATCH 0/3] PPC PReP: Use ElF kernel on PReP Fabien Chouteau
2013-04-03 16:40 ` [Qemu-devel] [PATCH 1/3] PPC PReP: Load ELF kernel Fabien Chouteau
2013-04-03 16:40 ` [Qemu-devel] [PATCH 2/3] PPC PReP: Use kernel entry to set nip at reset Fabien Chouteau
2013-04-03 16:40 ` [Qemu-devel] [PATCH 3/3] PPC PReP: can run without bios image Fabien Chouteau
2013-04-03 16:59 ` Alexander Graf
2013-04-04 8:37 ` Fabien Chouteau
2013-04-04 9:26 ` Alexander Graf
2013-04-04 16:19 ` Fabien Chouteau
2013-04-04 9:46 ` Artyom Tarasenko
2013-04-04 9:50 ` Alexander Graf
2013-04-04 9:57 ` Artyom Tarasenko
2013-04-04 11:53 ` Andreas Färber
2013-04-04 11:59 ` Alexander Graf
2013-04-05 23:00 ` Scott Wood
2013-04-06 9:01 ` Alexander Graf
2013-04-08 17:52 ` Scott Wood
2013-07-04 8:35 ` Julio Guerra
2013-07-10 9:16 ` Julio Guerra
2013-04-06 9:07 ` Alexander Graf
2013-04-06 11:27 ` Peter Maydell
2013-04-06 11:38 ` Alexander Graf
2013-04-06 13:08 ` Peter Maydell
2013-04-06 20:07 ` Edgar E. Iglesias [this message]
2013-04-06 20:12 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2013-04-07 0:52 ` Edgar E. Iglesias
2013-04-04 12:43 ` [Qemu-devel] " Peter Maydell
2013-04-04 16:17 ` Fabien Chouteau
2013-04-04 16:20 ` Peter Maydell
2013-04-04 16:26 ` Artyom Tarasenko
2013-04-04 16:30 ` Peter Maydell
2013-04-04 16:34 ` Alexander Graf
2013-04-04 16:41 ` Peter Maydell
2013-04-04 16:51 ` Alexander Graf
2013-04-04 16:52 ` Peter Maydell
2013-04-04 22:32 ` Alexander Graf
2013-04-04 22:35 ` Peter Maydell
2013-04-04 16:46 ` Artyom Tarasenko
2013-04-04 16:51 ` Peter Maydell
2013-04-04 17:08 ` Artyom Tarasenko
2013-04-04 17:22 ` Andreas Färber
2013-04-05 9:19 ` Fabien Chouteau
2013-04-05 9:30 ` Peter Maydell
2013-04-04 17:05 ` Andreas Färber
2013-04-05 2:32 ` Rob Landley
2013-04-04 11:16 ` Andreas Färber
2013-04-04 16:18 ` Fabien Chouteau
2013-04-03 16:47 ` [Qemu-devel] [PATCH 0/3] PPC PReP: Use ElF kernel on PReP Alexander Graf
2013-04-03 17:32 ` Andreas Färber
2013-04-04 8:17 ` Fabien Chouteau
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=20130406200716.GA4430@smtp.vpn \
--to=edgar.iglesias@gmail.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=atar4qemu@gmail.com \
--cc=hpoussin@reactos.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=scottwood@freescale.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.