From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55013) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XiNgd-0000Uh-5a for qemu-devel@nongnu.org; Sun, 26 Oct 2014 09:16:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XiNgX-0005di-0F for qemu-devel@nongnu.org; Sun, 26 Oct 2014 09:16:47 -0400 Received: from mail-pd0-x22f.google.com ([2607:f8b0:400e:c02::22f]:43815) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XiNgW-0005dY-Px for qemu-devel@nongnu.org; Sun, 26 Oct 2014 09:16:40 -0400 Received: by mail-pd0-f175.google.com with SMTP id y13so4024941pdi.20 for ; Sun, 26 Oct 2014 06:16:39 -0700 (PDT) Content-Type: text/plain; charset=gb2312 Mime-Version: 1.0 (1.0) From: Chen Gang In-Reply-To: <5u43au1mo9g0jew0r43bu8en.1413934331891@email.android.com> Date: Sun, 26 Oct 2014 21:16:32 +0800 Content-Transfer-Encoding: quoted-printable Message-Id: <6F62B4B4-0160-4290-B780-1C16FD057A53@gmail.com> References: <5u43au1mo9g0jew0r43bu8en.1413934331891@email.android.com> Subject: Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Guenter Roeck Cc: Max Filippov , qemu-devel , Peter Maydell And I still shall try qemu and kernel distribution for testing. But excuse me, maybe I can not finish within this month, I shall try to finish within next month. Thanks. =B7=A2=D7=D4=CE=D2=B5=C4 iPad > =D4=DA 2014=C4=EA10=D4=C222=C8=D5=A3=AC=C9=CF=CE=E78:28=A3=ACChen Gang =D0=B4=B5=C0=A3=BA >=20 > 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. >=20 > 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 bi= nutils). So next, I will mainly focus on sim. >=20 > 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). >=20 > Thanks. >=20 > Send from Lenovo A788t. >=20 > Guenter Roeck wrote: >=20 >>> 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: >>>>>>=20 >>>>>> This doesn't use devicetree, but the configurations are known to be w= orking >>>>>> with kernel releases all the way back to kernel version 3.10. >>>>>=20 >>>>> Yeah, really it is ! >>>>>=20 >>>>> 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? >>>>=20 >>>> Difficult to say. >>>>=20 >>>> I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configu= ration >>>> for the microblaze big endian target. No idea if that makes a differenc= e, >>>> but I would suggest to start with those. >>>>=20 >>>> 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. >>>=20 >>> OK, thank you very much for your information. >>>=20 >>> 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). >>>=20 >>> 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 binut= ils >> (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. >>=20 >> Thanks, >> Guenter