From: Alexander Graf <agraf@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>,
KONRAD Frederic <frederic.konrad@adacore.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.11 0/4] ppc64: add e6500
Date: Fri, 11 Aug 2017 10:14:47 +0100 [thread overview]
Message-ID: <d64a5e9f-6d4f-42f0-d771-966fbf3d294e@suse.de> (raw)
In-Reply-To: <20170809071315.GN13670@umbus.fritz.box>
On 09.08.17 08:13, David Gibson wrote:
> On Mon, Aug 07, 2017 at 05:50:44PM +0200, KONRAD Frederic wrote:
>> Hi,
>>
>> Those are some patches to add basic e6500 support for the moment e5500 with a
>> correct MMU configuration and supported instructions.
>> Some (maybe a lot of) things are missing (ie: the thread support) but it is
>> enough to boot a propietary OS on my side.
>>
>> The first two patches are fixes when using MAV 2.0 MMU.
>> The two last patches introduces the e6500.
>>
>> This can be cloned here:
>> https://github.com/FredKonrad/qemu.git branch e6500
>
> Looks sane as best as my minimal knowledge of e500 goes. Applied to
> ppc-for-2.11. Alex, if you (or anyone with knowledge of this
> platform) has objections, I'll reconsider.
I think it's good enough. We're missing a *lot* of e6500 features, but
if this is useful to Frederic, I don't see a good reason to hold it back.
Alex
prev parent reply other threads:[~2017-08-11 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 15:50 [Qemu-devel] [PATCH for-2.11 0/4] ppc64: add e6500 KONRAD Frederic
2017-08-07 15:50 ` [Qemu-devel] [PATCH for-2.11 1/4] booke206: fix booke206_tlbnps for mav 2.0 KONRAD Frederic
2017-08-07 15:50 ` [Qemu-devel] [PATCH for-2.11 2/4] booke206: fix tlbnps for fixed size TLB KONRAD Frederic
2017-08-07 15:50 ` [Qemu-devel] [PATCH for-2.11 3/4] booke206: allow to specify an mmucfg value at the init KONRAD Frederic
2017-08-07 15:50 ` [Qemu-devel] [PATCH for-2.11 4/4] ppc64: introduce e6500 KONRAD Frederic
2017-08-09 7:13 ` [Qemu-devel] [PATCH for-2.11 0/4] ppc64: add e6500 David Gibson
2017-08-11 9:14 ` Alexander Graf [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=d64a5e9f-6d4f-42f0-d771-966fbf3d294e@suse.de \
--to=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=frederic.konrad@adacore.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).