All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL] qemu-sparc update
Date: Sun, 08 Mar 2015 10:04:12 +0000	[thread overview]
Message-ID: <54FC1E9C.4060401@ilande.co.uk> (raw)
In-Reply-To: <CAFEAcA9YrYGZX5zn+1Br3up+BkbR7uK0DQHXBS=QVAnn+=hJzQ@mail.gmail.com>

On 08/03/15 09:47, Peter Maydell wrote:

> On 4 March 2015 at 15:20, Mark Cave-Ayland
> <mark.cave-ayland@ilande.co.uk> wrote:
>> Hi Peter,
>>
>> Here are the updates from my qemu-sparc tree. Please pull.
> 
>>  MAINTAINERS               |    3 +
>>  hw/ppc/ppc.c              |  161 --------------------
>>  hw/ppc/ppc405_boards.c    |    2 +-
>>  hw/ppc/prep.c             |  163 ++++++++++++++++++--
>>  hw/sparc/sun4m.c          |   10 +-
>>  hw/sparc64/sun4u.c        |   20 ++-
>>  hw/timer/m48t59.c         |  359 ++++++++++++++++++++++++++++++++-------------
>>  include/hw/timer/m48t59.h |   61 ++++----
>>  pc-bios/openbios-sparc64  |  Bin 1616768 -> 1616768 bytes
>>  qemu-doc.texi             |    7 +-
> 
> Shouldn't there be an update to roms/openbios to go with the
> pc-bios/openbios-sparc64 binary blob update?

I haven't committed the sun4u MMIO patches to OpenBIOS yet because
without the corresponding QEMU parts OpenBIOS SVN trunk breaks (and the
QEMU parts have taken many weeks to get right which is a long time to
leave things broken). Hence I've gone for just updating the binary which
is SVN trunk plus the NVRAM MMIO accessor changes in order to preserve
bisection.

As soon as this is applied, I can apply my remaining OpenBIOS patches
and then send a separate qemu-openbios pull request which will bring
everything up to date.


ATB,

Mark.

  reply	other threads:[~2015-03-08 10:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  6:20 [Qemu-devel] [PULL] qemu-sparc update Mark Cave-Ayland
2015-03-08  9:47 ` Peter Maydell
2015-03-08 10:04   ` Mark Cave-Ayland [this message]
2015-03-08 10:31     ` Peter Maydell
2015-03-08 10:57       ` Mark Cave-Ayland
2015-03-08 20:48         ` Alexander Graf
2015-03-08 21:03           ` Mark Cave-Ayland
2015-03-08 21:05             ` Alexander Graf
2015-03-09  9:32               ` Mark Cave-Ayland
  -- strict thread matches above, loose matches on Subject: below --
2017-10-31 17:50 Mark Cave-Ayland
2017-11-02 10:10 ` Peter Maydell
2017-04-21 19:17 Mark Cave-Ayland
2017-04-24  9:48 ` Peter Maydell
2016-06-24 17:41 Mark Cave-Ayland
2016-06-27 10:48 ` Peter Maydell
2016-06-20 21:06 Mark Cave-Ayland
2016-06-21 11:58 ` Peter Maydell
2016-04-15  8:40 Mark Cave-Ayland
2016-04-15 10:26 ` Peter Maydell
2016-04-11 15:39 Mark Cave-Ayland
2016-04-11 16:10 ` Peter Maydell
2016-01-16 12:41 Mark Cave-Ayland
2016-01-18 13:38 ` Peter Maydell
2016-01-07 12:24 Mark Cave-Ayland
2016-01-07 13:19 ` Mark Cave-Ayland
2015-01-21 17:06 Mark Cave-Ayland
2015-01-22 12:13 ` Peter Maydell
2014-09-23 22:11 Mark Cave-Ayland
2014-09-24 13:30 ` Peter Maydell
2014-09-09  5:25 Mark Cave-Ayland
2014-09-09 15:15 ` Peter Maydell

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=54FC1E9C.4060401@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=peter.maydell@linaro.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 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.