qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Max Filippov <jcmvbkbc@gmail.com>,
	Richard Henderson <rth@twiddle.net>,
	qemu-devel <qemu-devel@nongnu.org>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu
Date: Tue, 21 Oct 2014 18:41:14 +0800	[thread overview]
Message-ID: <5446384A.1040605@gmail.com> (raw)
In-Reply-To: <5445E327.8030209@roeck-us.net>

On 10/21/14 12:37, Guenter Roeck wrote:
> On 10/20/2014 08:23 AM, Chen Gang wrote:
>> On 10/19/2014 10:58 PM, Guenter Roeck wrote:
>>>
>>> This doesn't use devicetree, but the configurations are known to be working
>>> with kernel releases all the way back to kernel version 3.10.
>>>
>>
>> Yeah, really it is !
>>
>> After try upstream qemu and upstream kernel, for me, neither them can
>> work well. For xilinx qemu with xilinux kernel, it should be well,
>> although I still met issue below, is what I have done incorrect?
>>
> 
> Difficult to say.
> 
> I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configuration
> for the microblaze big endian target. No idea if that makes a difference,
> but I would suggest to start with those.
> 
> For microblazeel I use gcc 4.9.1 built with buildroot 2014.08 for both
> kernel and initramfs. Initramfs for that target is built from busybox.
> 

OK, thank you very much for your information.

But sorry, I have to stop trying, because that is far from upstream qemu
and upstream kernel (at present, I have no enough time resource on it).

My original goal is "use upstream microblaze qemu to test upstream gcc,
binutils and glibc of microblaze". And now I find another ways: "use sim
which is in upstream binutils to perform the related test".


And welcome any new ideas, suggestions, and completions.

Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

  reply	other threads:[~2014-10-21 10:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-19 13:37 [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu Chen Gang
2014-10-19 13:38 ` Max Filippov
2014-10-19 13:58   ` Chen Gang
2014-10-19 14:58     ` Guenter Roeck
2014-10-20 15:23       ` Chen Gang
2014-10-21  4:37         ` Guenter Roeck
2014-10-21 10:41           ` Chen Gang [this message]
2014-10-21 16:43             ` Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2014-10-19 23:38 Chen Gang
2014-10-22  0:28 Chen Gang
2014-10-26 13:16 ` Chen Gang
2014-10-26 13:28 ` Chen Gang
2014-10-27  1:47   ` Chen Gang
2014-10-27 14:47     ` Chen Gang
2014-10-30 14:20       ` Chen Gang
2014-10-31 17:09         ` Chen Gang
2014-11-09 11:57           ` Chen Gang

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=5446384A.1040605@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux@roeck-us.net \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).