qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Stafford Horne <shorne@gmail.com>
Cc: Jia Liu <proljc@gmail.com>,
	qemu-devel@nongnu.org, openrisc@lists.librecores.org
Subject: Re: [Qemu-devel] [PATCH] target-openrisc: Fix exception handling status registers
Date: Wed, 25 Jan 2017 09:27:29 -0800	[thread overview]
Message-ID: <39f927aa-26fe-0e43-7c6b-efe1b70bc5fa@twiddle.net> (raw)
In-Reply-To: <20170125123430.GG7836@lianli.shorne-pla.net>

On 01/25/2017 04:34 AM, Stafford Horne wrote:
> Hmm, I just tried your qemu branch and mine:
> 
>   git@github.com:stffrdhrn/qemu.git or1k-fix-sigill
> 
> Both of them were able to boot fine.
> 
> The opencores,or1200-rtlsvn481 cpu node is in the or1ksim device tree
> definition.  Are you sure your kernel config has this in it?
> 
>   CONFIG_OPENRISC_BUILTIN_DTB="or1ksim"
> 
> Could you send your kernel config?
> 
> I have attached mine, just in case.  For next-20170124

Curious.  The entire diff between our configs is just

--- ../or-config        2017-01-24 09:14:51.918059107 -0800
+++ .config     2017-01-25 09:18:14.153999754 -0800
@@ -18,7 +18,7 @@
 #
 CONFIG_BROKEN_ON_SMP=y
 CONFIG_INIT_ENV_ARG_LIMIT=32
-CONFIG_CROSS_COMPILE="or1k-linux-musl-"
+CONFIG_CROSS_COMPILE="or1k-musl-linux-"
 # CONFIG_COMPILE_TEST is not set
 CONFIG_LOCALVERSION=""
 CONFIG_LOCALVERSION_AUTO=y

So you're saying you *do* get serial port output?

Perhaps you can just send me your kernel...


r~

  reply	other threads:[~2017-01-25 17:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170113215720.29598-1-shorne@gmail.com>
     [not found] ` <20170113220252.GE25986@lianli.shorne-pla.net>
     [not found]   ` <CAJBMM-sX4fGckYy-eNRdZ9dKamOoJoK2fQ4TLS80T5n6jCkpFg@mail.gmail.com>
2017-01-14  8:04     ` [Qemu-devel] [PATCH] target-openrisc: Fix exception handling status registers Stafford Horne
2017-01-20 16:39       ` Stafford Horne
2017-01-23 18:08         ` Richard Henderson
2017-01-24 10:26           ` Stafford Horne
2017-01-24 18:32             ` Richard Henderson
2017-01-25 12:34               ` Stafford Horne
2017-01-25 17:27                 ` Richard Henderson [this message]
2017-01-26 13:12                   ` Stafford Horne
2017-01-26 17:26                     ` Richard Henderson
2017-01-26 22:01                       ` Stafford Horne
2017-02-01 10:04                       ` Stafford Horne
2017-02-01 18:15                         ` Richard Henderson
2017-02-02 14:34                           ` Stafford Horne
2017-02-03 15:14                             ` Stafford Horne
2017-02-07  2:36                               ` Richard Henderson
2017-02-07  5:53                         ` Richard Henderson
2017-02-08 14:01                           ` Stafford Horne
2017-02-08 16:38                             ` Stafford Horne
2017-02-08 20:38                             ` Richard Henderson
2017-01-13 22:00 Stafford Horne

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=39f927aa-26fe-0e43-7c6b-efe1b70bc5fa@twiddle.net \
    --to=rth@twiddle.net \
    --cc=openrisc@lists.librecores.org \
    --cc=proljc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --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).