qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Programmingkid <programmingkidx@gmail.com>
To: Richard Henderson <rth@twiddle.net>
Cc: Stafford Horne <shorne@gmail.com>,
	Openrisc <openrisc@lists.librecores.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 00/22] target/openrisc updates
Date: Mon, 13 Feb 2017 22:33:09 -0500	[thread overview]
Message-ID: <4BE06A79-02EC-48A8-8081-F21CEACE396F@gmail.com> (raw)
In-Reply-To: <ec491d8c-3fb0-3ce9-5558-ac4ab1455f7f@twiddle.net>


On Feb 13, 2017, at 10:25 PM, Richard Henderson wrote:

> On 02/10/2017 11:39 AM, Stafford Horne wrote:
>> On Thu, Feb 09, 2017 at 09:10:51AM -0500, G 3 wrote:
>>> 
>>> On Feb 8, 2017, at 11:52 PM, qemu-devel-request@nongnu.org wrote:
>>> 
>>>> Message: 6
>>>> Date: Wed,  8 Feb 2017 20:51:32 -0800
>>>> From: Richard Henderson <rth@twiddle.net>
>>>> To: qemu-devel@nongnu.org
>>>> Cc: shorne@gmail.com
>>>> Subject: [Qemu-devel] [PATCH 00/22] target/openrisc updates
>>>> Message-ID: <20170209045154.16868-1-rth@twiddle.net>
>>>> 
>>>> The bulk of this patch set is 2-3 years old, and was mostly
>>>> reviewed by Bastian Koppelmann.  But it languished because
>>>> there were reports of it not booting kernel images, and I
>>>> had problems putting together a set of tools that could even
>>>> build a kernel.
>>>> 
>>>> The OpenRISC community has picked up activity recently,
>>>> with Stafford Horne upstreaming some of the compiler tools.
>>>> He has even done some testing for me of this patch set.
>>>> 
>>>> 
>>>> r~
>>> 
>>> I see you are working on OpenRISC. Would you be able to help
>>> me improve its wiki page?
>>> 
>>> http://wiki.qemu-project.org/Documentation/Platforms/OpenRISC
>>> 
>>> Right now there isn't much information on OpenRISC here. I'm
>>> hoping to make it a lot useful to anyone who is interesting in this
>>> platform.
>>> 
>>> Would you know of any links to software that works in OpenRISC?
>>> 
>>> Pictures of the OpenRISC target running anything would be great also.
>>> 
>>> What is your suggested command-line for using OpenRISC?
>>> 
>>> If you have any suggestions on how to improve the page place don't
>>> hesitate to let me know.
>>> 
>> 
>> Hi Richard, G 3,
>> 
>> I am not sure if Richard has the time for this.  But I kind of got him
>> started back on the openrisc work, it would be my fault to burden him
>> with even more work :).  Also, I was helping to do some tests so I have
>> some example commands.
> 
> :-)
> 
>> I don't have a lot of time, but I think I can help to update the above.
>> Probably Richard and I could work together?
>> 
>> I was recently working on updating the openrisc page
>> 
>>  http://openrisc.io
>> 
>> I think I could link between the two for toolchain compile guides and
>> software guides (i.e. debugging and linux).
>> 
>> Richard what do you think?
> 
> Probably the most beneficial thing that we can do is create a kernel+initrd that boots into a busybox root shell.  Similar to the other test images that we have at
> 
>  http://wiki.qemu-project.org/Testing/System_Images
> 
> 
> r~
> 

We could do both the test image and a wiki page.

  reply	other threads:[~2017-02-14  3:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.51026.1486615955.22738.qemu-devel@nongnu.org>
2017-02-09 14:10 ` [Qemu-devel] [PATCH 00/22] target/openrisc updates G 3
2017-02-10  0:39   ` Stafford Horne
2017-02-14  3:25     ` Richard Henderson
2017-02-14  3:33       ` Programmingkid [this message]
2017-02-15 13:26         ` Stafford Horne
2017-02-20 13:22         ` Stafford Horne
2017-02-23 14:09         ` Stafford Horne
2017-02-23 15:54           ` G 3
2017-02-25  6:17             ` Stafford Horne
2017-02-23 22:41           ` Richard Henderson
2017-02-09  4:51 Richard Henderson

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=4BE06A79-02EC-48A8-8081-F21CEACE396F@gmail.com \
    --to=programmingkidx@gmail.com \
    --cc=openrisc@lists.librecores.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=shorne@gmail.com \
    /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).