[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Consult] microblaze: About running upstream main branc
From: |
Chen Gang |
Subject: |
Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu |
Date: |
Wed, 22 Oct 2014 08:28:31 +0800 |
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 <address@hidden> 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