All of lore.kernel.org
 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>,
	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: Mon, 27 Oct 2014 09:47:44 +0800	[thread overview]
Message-ID: <544DA440.2090202@gmail.com> (raw)
In-Reply-To: <544CF6EC.1090507@gmail.com>

On 10/26/14 21:28, Chen Gang wrote:
> Hello Guenter Roeck:
> 
> I still shall try qemu and kernel distribution, next, since it can do
> it successfully (whether 'sim' can be success or not).
> 

I got confirmation from microblaze members, at present, microblaze sim
can not full simulate entire system, so I shall try qemu and kernel
distribution for it (which can do full simulation for microblaze).

I shall try my best to finish it within this month.

Thanks.

> But excuse me, maybe I can not finish microblaze qemu test within this
> month, hope I can finish within next month (2014-11-30).
> 
> Thank your information about qemu, again.
> 
> 
> Thanks.
> 
> On 10/22/2014 08:28 AM, Chen Gang wrote:
>> OK, thanks, there are multiple branches in upstream qemu. Sorry
>> for my original said, and I can only say: for upstream  develop
>> master branch, it does not support microblaze.
>>
>> Excuse me, I does not mainly focus on only using qemu, and I
>> also found another easier way for test microblaze toolchain (use sim of binutils). So next, I will mainly focus on sim.
>>
>> I also met some issues for sim, but I guess, I can analyze it,
>> maybe also have chances to make patch for it (that is the main
>> reason why I want to focus on it).
>>
>> Thanks.
>>
>> Send from Lenovo A788t.
>>
>>
>>
>>
>>
>> Guenter Roeck <linux@roeck-us.net> wrote:
>>
>>
>>
>> On Tue, Oct 21, 2014 at 06:41:14PM +0800, Chen Gang wrote:
>>> 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".
>>>
>> You lost me. qemu 2.1.2 is the upstream qemu, and I do use upstream binutils
>> (2.24 if I recall corectly) as well as upstream gcc and upstream kernel.
>> Did I indicate otherwise in anything I said ? FWIW, should be able to use
>> qemu from distributions without recompiling it.
>>
>> Thanks,
>> Guenter
>>
> 
> 

-- 
Chen Gang

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

  reply	other threads:[~2014-10-27  1:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22  0:28 [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu Chen Gang
2014-10-26 13:16 ` Chen Gang
2014-10-26 13:28 ` Chen Gang
2014-10-27  1:47   ` Chen Gang [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2014-10-19 23:38 Chen Gang
2014-10-19 13:37 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
2014-10-21 16:43             ` Guenter Roeck

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=544DA440.2090202@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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.