qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Trivial <qemu-trivial@nongnu.org>,
	Michael Tokarev <mjt@tls.msk.ru>,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Fabien Chouteau <chouteau@adacore.com>,
	Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] sparc/leon3: Initialize stack pointer
Date: Wed, 12 Feb 2014 17:40:17 +0100	[thread overview]
Message-ID: <52FBA3F1.8080503@suse.de> (raw)
In-Reply-To: <52FB7D13.8050801@embedded-brains.de>

Am 12.02.2014 14:54, schrieb Sebastian Huber:
> On 2014-02-06 09:57, Peter Maydell wrote:
>> On 6 February 2014 08:40, Michael Tokarev<mjt@tls.msk.ru>  wrote:
>>> >03.02.2014 13:18, Sebastian Huber wrote:
>>>> >>A lot of real world LEON3 systems are shipped with the GRMON boot
>>>> >>loader.  This boot loader initializes the stack pointer with the
>>>> end of
>>>> >>RAM address.  The application can use this to detect the RAM size
>>>> of a
>>>> >>particular board variant.
>>> >
>>> >I don't really know much about sparc or leon3 stuff.  But having a
>>> >reviewed-by from Fabien I can apply it to trivial-patches.  I'm not
>>> >really sure why it can't go to sparc tree instead.
>> As far as I'm aware there is currently no sparc tree; Blue is the
>> listed maintainer and typically just applied patches directly.
>> In the absence of Blue, if somebody else who cares about sparc
>> wishes to collect up reviewed sparc patches and submit them as
>> a pull request so they don't just get ignored, I'm willing to apply
>> that pull.
> 
> Ok, how do we want proceed here?  I have an additional patch in the
> queue that adds AMBA plug and play support to the LEON3 support of QEMU
> so that you can run unmodified binaries for RTEMS, eCos and Linux.

Whether or not someone submits a pull for the reviewed patches, you'll
need to post your second patch for review. You can add either a tag in
[PATCH ...] or indicate textually after --- that it depends on this
patch, you don't need to wait for it to get applied first.

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      parent reply	other threads:[~2014-02-12 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03  9:18 [Qemu-devel] [PATCH] sparc/leon3: Initialize stack pointer Sebastian Huber
2014-02-05  9:02 ` Fabien Chouteau
2014-02-05  9:26   ` [Qemu-devel] [Qemu-trivial] " Fabien Chouteau
2014-02-06  8:40 ` Michael Tokarev
2014-02-06  8:52   ` Sebastian Huber
2014-02-06  8:57   ` Peter Maydell
2014-02-12 13:54     ` Sebastian Huber
2014-02-12 14:00       ` Peter Maydell
2014-02-12 16:27         ` Michael Tokarev
2014-02-12 16:40       ` Andreas Färber [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=52FBA3F1.8080503@suse.de \
    --to=afaerber@suse.de \
    --cc=blauwirbel@gmail.com \
    --cc=chouteau@adacore.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=mjt@tls.msk.ru \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=sebastian.huber@embedded-brains.de \
    /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).