All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL] qemu-sparc update
Date: Sun, 8 Mar 2015 17:05:20 -0400	[thread overview]
Message-ID: <FF373C1B-90E8-4C5E-B055-8986CC11D4FF@suse.de> (raw)
In-Reply-To: <54FCB909.7000105@ilande.co.uk>




> Am 08.03.2015 um 17:03 schrieb Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>:
> 
>> On 08/03/15 20:48, Alexander Graf wrote:
>> 
>>> On 08.03.15 06:57, Mark Cave-Ayland wrote:
>>>> On 08/03/15 10:31, Peter Maydell wrote:
>>>> 
>>>> On 8 March 2015 at 19:04, Mark Cave-Ayland
>>>> <mark.cave-ayland@ilande.co.uk> wrote:
>>>>> 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.
>>>> 
>>>> Hmm. I'm not a huge fan of having the binary in git and the submodule
>>>> reference be out of step...
>>> 
>>> Alternatively if you have shell access to git.qemu.org then I can commit
>>> just the MMIO accessor changes to SVN trunk now and then with a manual
>>> update to the OpenBIOS git mirror I can re-send the signed pull request
>>> with updated binaries? I've deliberately held off applying patches to
>>> OpenBIOS SVN trunk in case this was the preferred method as I'm keen to
>>> be able to bisect down to this particular change on SPARC64.
>> 
>> Is there any way to make the change backwards compatible, so that we
>> don't need to sync versions?
> 
> Not without refactoring to enable more than one type of NVRAM accessor
> in OpenBIOS, plus a fw_cfg variable to enable the switch between the two
> for SPARC64.
> 
> Given that SPARC64 is still more experimental than stable plus newer
> versions of OpenBIOS aren't guaranteed to work with older versions of
> QEMU anyhow, I just can't see that this is worth all the extra effort
> for the sake of a follow-up pull request within a day or so that will
> bring everything up to date whilst still allowing a proper bisection.
> 
> Now if Peter is still keen to keep the git submodule reference intact
> then I'm happy to commit just the MMIO accessor changes to OpenBIOS SVN
> trunk as long as we can minimise the time between the QEMU changes and
> the OpenBIOS changes.

Yes, I think that's a reasonable way forward. Maybe add a fw_cfg and assert() on it nevertheless, so people don't fall into pits ;).


Alex

  reply	other threads:[~2015-03-08 21:05 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
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 [this message]
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=FF373C1B-90E8-4C5E-B055-8986CC11D4FF@suse.de \
    --to=agraf@suse.de \
    --cc=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.