From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56290) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XiNs2-0003EC-KF for qemu-devel@nongnu.org; Sun, 26 Oct 2014 09:28:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XiNrw-000171-96 for qemu-devel@nongnu.org; Sun, 26 Oct 2014 09:28:34 -0400 Received: from mail-pd0-x231.google.com ([2607:f8b0:400e:c02::231]:41490) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XiNrw-00016q-15 for qemu-devel@nongnu.org; Sun, 26 Oct 2014 09:28:28 -0400 Received: by mail-pd0-f177.google.com with SMTP id v10so4013675pde.22 for ; Sun, 26 Oct 2014 06:28:26 -0700 (PDT) Message-ID: <544CF6EC.1090507@gmail.com> Date: Sun, 26 Oct 2014 21:28:12 +0800 From: Chen Gang MIME-Version: 1.0 References: <5u43au1mo9g0jew0r43bu8en.1413934331891@email.android.com> In-Reply-To: <5u43au1mo9g0jew0r43bu8en.1413934331891@email.android.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 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). 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 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