From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37158) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XkEOj-0004Wh-3V for qemu-devel@nongnu.org; Fri, 31 Oct 2014 11:46:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XjqUp-0004iQ-0L for qemu-devel@nongnu.org; Thu, 30 Oct 2014 10:14:46 -0400 Received: from mail-pa0-x235.google.com ([2607:f8b0:400e:c03::235]:55987) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjqUo-0004i3-LD for qemu-devel@nongnu.org; Thu, 30 Oct 2014 10:14:38 -0400 Received: by mail-pa0-f53.google.com with SMTP id kx10so5557678pab.12 for ; Thu, 30 Oct 2014 07:14:36 -0700 (PDT) Message-ID: <5452493B.7070906@gmail.com> Date: Thu, 30 Oct 2014 22:20:43 +0800 From: Chen Gang MIME-Version: 1.0 References: <5u43au1mo9g0jew0r43bu8en.1413934331891@email.android.com> <544CF6EC.1090507@gmail.com> <544DA440.2090202@gmail.com> <544E5B0C.7000601@gmail.com> In-Reply-To: <544E5B0C.7000601@gmail.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 On 10/27/14 22:47, Chen Gang wrote: > > After a little try, I succeed run microblaze under upstream qemu 2.1.2 > and upstream Linux kernel 3.17-rc7, with the xilinux own ramdisk: > "microblaze_complete.cpio.gz". :-) > > Compiler is "gcc version 4.9.1 20140717 (Red Hat Cross 4.9.1-1) (GCC)" > for microblaze, and "gcc version 4.8.3 20140624 (Red Hat 4.8.3-1) (GCC)" > for x86_64 qemu. > > Next I shall try to use virtio file to share the local data to virtual > guest (I guess, it should be OK). > I finished testing the microblaze hello world program with both dynamic glibc and static glibc under qemu (I put it to 'ramfs' manualy, and it runs well) :-) Next, I need focus on networking (I have found qemu related device, and kernel related device, and I also know, it needs telnetd in busy box). But sorry, it seems I can not finish within this month :-( - I wasted much time resources on choosing qemu or sim, next I should notice about it (do not waste time, again). - and another excuse is: I have to do it in my free time (within 2.5 hours per day, in average). My current job is not related with it (at present, it is about Global Platform Java applet for iPhone OS). Next month: - I should finish microblaze qemu test under DejaGNU, should finish within next month (2014-11-30). - I also shall start tile cross compiling for gcc/binutils, and use it to Linux kernel, and test it with qemu. I shall try to finish them within 2 months (finish before 2014-12-31). - At least, finish 1 patch for gcc, 1 patch for binutils, 1 patch for qemu/kvm/xen, 3 patches for kernel, within next month (2014-11-30). Welcome any ideas, suggestions or completions (especially for net device, net drivers, busy box for telnet ...). Thanks. > > Thanks again! > > > > On 10/27/2014 09:47 AM, Chen Gang wrote: >> 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 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