From: "Cédric Le Goater" <clg@kaod.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Alistair Francis <alistair@alistair23.me>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] aspeed: add MMIO exec support to the FMC controller
Date: Tue, 5 Jun 2018 15:43:57 +0200 [thread overview]
Message-ID: <e4840353-abf9-868f-20f1-3f07d13b84c8@kaod.org> (raw)
In-Reply-To: <CAFEAcA_a+nduAKWhLiwoKvoybL+cKN=51xV5M9f-VatPdbnf6w@mail.gmail.com>
On 05/30/2018 02:40 PM, Peter Maydell wrote:
> On 30 May 2018 at 08:49, Cédric Le Goater <clg@kaod.org> wrote:
>> Hello,
>>
>> When MMIO execution support is active, these changes let the Aspeed
>> SoC machine boot directly from CE0. As there is still some
>> issues, the feature is disabled by default and should be activated
>> with :
>>
>> -global driver=aspeed.smc,property=mmio-exec,value=true
>
> I'd really rather not add another mmio-exec device until
> we've sorted out making it actually work properly...
Could we still take patch 1-2 which are good model cleanups
for the flash controller ?
Thanks,
C.
prev parent reply other threads:[~2018-06-05 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 7:49 [Qemu-arm] [PATCH 0/4] aspeed: add MMIO exec support to the FMC controller Cédric Le Goater
2018-05-30 7:49 ` [Qemu-arm] [PATCH 1/4] aspeed/smc: fix HW strapping Cédric Le Goater
2018-05-30 7:50 ` [Qemu-devel] [PATCH 2/4] aspeed/smc: rename aspeed_smc_flash_send_addr() to aspeed_smc_flash_setup() Cédric Le Goater
2018-05-30 7:50 ` [Qemu-devel] [PATCH 3/4] aspeed/smc: add a new memory region dedicated to MMIO execution Cédric Le Goater
2018-05-30 7:50 ` [Qemu-devel] [PATCH 4/4] hw/arm/aspeed: boot from the FMC CE0 flash module Cédric Le Goater
2018-05-30 12:40 ` [Qemu-arm] [PATCH 0/4] aspeed: add MMIO exec support to the FMC controller Peter Maydell
2018-05-30 12:47 ` Cédric Le Goater
2018-06-05 13:43 ` Cédric Le Goater [this message]
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=e4840353-abf9-868f-20f1-3f07d13b84c8@kaod.org \
--to=clg@kaod.org \
--cc=alistair@alistair23.me \
--cc=crosthwaite.peter@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@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).