qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Alistair Francis <alistair.francis@xilinx.com>
Cc: edgar.iglesias@xilinx.com, peter.crosthwaite@xilinx.com,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 0/9]  Extend Microblaze Properties
Date: Sun, 21 Jun 2015 21:44:55 +1000	[thread overview]
Message-ID: <20150621114455.GL5149@toto> (raw)
In-Reply-To: <cover.1434686378.git.alistair.francis@xilinx.com>

On Thu, Jun 18, 2015 at 09:16:21PM -0700, Alistair Francis wrote:
> This patch series extends the MicroBlaze properties
> that I have been working on. It applies on top of my
> original work:
> 'Add Microblaze configuration options'.
> 
> This patch series converts various MicroBlaze PVR registers
> to properties. This then allows the individual Microblaze
> machine reset functions to be removed as well as some other
> dead code.

Thanks Alistair, I've merged this into the mb queue.

Cheers,
Edgar



> 
> V4:
>  - Add some macros
> V3:
>  - Update the pvr register to be a uint8
>  - Add the 8.50.a version to the version_mask
> 
> 
> Alistair Francis (9):
>   target-microblaze: Rename the usefpu variable
>   target-microblaze: Convert use-mmu to a CPU property
>   target-microblaze: Convert dcache-writeback to a CPU property
>   target-microblaze: Convert endi to a CPU property
>   target-microblaze: Convert version_mask to a CPU property
>   target-microblaze: Convert pvr-full to a CPU property
>   ml605_mmu: Move the hardcoded values to the init function
>   s3adsp1800: Remove the hardcoded values from the reset
>   target-microblaze: Remove dead code
> 
>  hw/microblaze/petalogix_ml605_mmu.c      |   23 +++-----
>  hw/microblaze/petalogix_s3adsp1800_mmu.c |    9 +---
>  target-microblaze/cpu-qom.h              |    7 ++-
>  target-microblaze/cpu.c                  |   79 +++++++++++++++++++++++++----
>  target-microblaze/cpu.h                  |    8 ++-
>  target-microblaze/helper.c               |    6 +-
>  target-microblaze/translate.c            |    6 +-
>  7 files changed, 95 insertions(+), 43 deletions(-)
> 

      parent reply	other threads:[~2015-06-21 11:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19  4:16 [Qemu-devel] [PATCH v4 0/9] Extend Microblaze Properties Alistair Francis
2015-06-19  4:16 ` [Qemu-devel] [PATCH v4 1/9] target-microblaze: Rename the usefpu variable Alistair Francis
2015-06-19  4:16 ` [Qemu-devel] [PATCH v4 4/9] target-microblaze: Convert endi to a CPU property Alistair Francis
2015-06-19  4:16 ` [Qemu-devel] [PATCH v4 6/9] target-microblaze: Convert pvr-full " Alistair Francis
2015-06-19  4:16 ` [Qemu-devel] [PATCH v4 7/9] ml605_mmu: Move the hardcoded values to the init function Alistair Francis
2015-06-19  4:16 ` [Qemu-devel] [PATCH v4 8/9] s3adsp1800: Remove the hardcoded values from the reset Alistair Francis
2015-06-19  4:16 ` [Qemu-devel] [PATCH v4 9/9] target-microblaze: Remove dead code Alistair Francis
2015-06-21 11:44 ` Edgar E. Iglesias [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=20150621114455.GL5149@toto \
    --to=edgar.iglesias@gmail.com \
    --cc=alistair.francis@xilinx.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=peter.crosthwaite@xilinx.com \
    --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).