qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: Julian Brown <julian@codesourcery.com>, Marek Vasut <marex@denx.de>
Cc: qemu-devel@nongnu.org, Chris Wulff <crwulff@gmail.com>,
	Andrew Jenner <Andrew_Jenner@mentor.com>
Subject: Re: [Qemu-devel] [PATCH v3 2/2] Add Nios II semihosting support.
Date: Thu, 2 Aug 2018 15:56:47 -0600	[thread overview]
Message-ID: <93a94aa5-2143-8079-3e0c-02364d0fab22@codesourcery.com> (raw)
In-Reply-To: <08f92788-6380-35fe-e237-aa80f075519e@codesourcery.com>

On 05/18/2018 03:35 PM, Sandra Loosemore wrote:
> On 05/18/2018 02:19 PM, Julian Brown wrote:
>> On Fri, 18 May 2018 21:52:04 +0200
>> Marek Vasut <marex@denx.de> wrote:
>>
>>> On 05/18/2018 09:23 PM, Julian Brown wrote:
>>>> This patch (by Sandra Loosemore, mildly rebased) adds support for
>>>> semihosting for Nios II bare-metal emulation.
>>>>
>>>> Signed-off-by: Julian Brown <julian@codesourcery.com>
>>>> Signed-off-by: Sandra Loosemore <sandra@codesourcery.com>
>>>
>>> Is there some documentation for this stuff ? It looks interesting, but
>>> how can I try it here ?
>>
>> There's no documentation AFAIK apart from that the entry points are
>> the same as m68k, semihosting is invoked with "break 1", and r4/r5 are
>> used for passing arguments. I'm not actually sure how you can try this
>> stuff without our startup code or other infrastructure (that I'm pretty
>> sure we can't divulge). Sandra, any ideas?
> 
> I don't see any reason why we couldn't contribute libgloss support, 
> except that I don't have time to write such a BSP right now.  :-(  I 
> recently did this for C-SKY, though, and the semihosting parts were just 
> a straightforward copy from the m68k port.

I've posted a patch with libgloss semihosting support for nios2 here:

https://sourceware.org/ml/newlib/2018/msg00610.html

I hope this is enough to unblock consideration of the corresponding QEMU 
patch set now.  Here's a link to the original patch posting:

http://lists.nongnu.org/archive/html/qemu-devel/2018-05/msg04571.html

-Sandra

  reply	other threads:[~2018-08-02 21:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 19:23 [Qemu-devel] [PATCH v3 0/2] Nios II generic board config and semihosting support Julian Brown
2018-05-18 19:23 ` [Qemu-devel] [PATCH v3 1/2] Add generic Nios II board Julian Brown
2018-05-18 19:50   ` Marek Vasut
2018-05-18 20:16     ` Julian Brown
2018-05-21  9:46       ` Andrew Jenner
2018-05-18 19:23 ` [Qemu-devel] [PATCH v3 2/2] Add Nios II semihosting support Julian Brown
2018-05-18 19:52   ` Marek Vasut
2018-05-18 20:19     ` Julian Brown
2018-05-18 20:28       ` Marek Vasut
2018-05-18 21:35       ` Sandra Loosemore
2018-08-02 21:56         ` Sandra Loosemore [this message]
2018-08-13  1:03           ` Julian Brown
2018-05-18 19:49 ` [Qemu-devel] [PATCH v3 0/2] Nios II generic board config and " Marek Vasut
2018-05-18 22:33 ` no-reply

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=93a94aa5-2143-8079-3e0c-02364d0fab22@codesourcery.com \
    --to=sandra@codesourcery.com \
    --cc=Andrew_Jenner@mentor.com \
    --cc=crwulff@gmail.com \
    --cc=julian@codesourcery.com \
    --cc=marex@denx.de \
    --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).