qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	linux@roeck-us.net, rth@twiddle.net,
	qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu
Date: Sun, 19 Oct 2014 21:37:48 +0800	[thread overview]
Message-ID: <5443BEAC.2070107@gmail.com> (raw)

Hello microblaze maintainers:

I tried to run upstream qemu for microblaze, but failed. It seems only
special qemu branch can run it. And after try Xilinx qemu branch, I got
"segment fault" which is related with "-dtb".  So I want to consult:

 - Can our main upstream qemu (not other branches) run microblaze?

 - Is what I have done for Xilinx related qemu correct?

The related operation for Xilinx related qemu is below:

 * For kernel:

   - building:

     git clone https://github.com/Xilinx/linux-xlnx.git
     cd linux-xlnx
     make ARCH=microblaze CROSS_COMPILE=/upstream/release/bin/microblaze-gchen-linux- mmu_config
     make ARCH=microblaze CROSS_COMPILE=/upstream/release/bin/microblaze-gchen-linux-

   - output:

     arch/microblaze/boot/linux.bin
     scripts/dtc/dtc

   - get 'system.dtb':

     ./scripts/dtc/dtc -I dts -O dtb -o system.dtb arch/microblaze/boot/dts/system.dts

 * For ramdisk:

   wget http://www.wiki.xilinx.com/file/view/microblaze_complete.cpio.gz/419243588/microblaze_complete.cpio.gz

 * For qemu:

   - building:

     git clone git://github.com/Xilinx/qemu.git
     ./configure --target-list="arm-softmmu,microblazeel-softmmu" --enable-fdt --disable-kvm
     make

   - running:

     ./arm-softmmu/qemu-system-arm -M arm-generic-fdt -nographic -smp 2 -machine linux=on -serial mon:stdio -dtb ../linux-xlnx/system.dtb \
       -kernel ../linux-xlnx/arch/microblaze/boot/linux.bin -initrd ../microblaze_complete.cpio.gz

   - result:

     Segmentation fault (core dumped) (after a simple try, I am sure, it is caused by "dtb").

And excuse me, at present, I have to only focus on fixing upstream qemu
issues (I have no enough time resource for other qemu branches), please
understand.

Thanks.
-- 
Chen Gang

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

             reply	other threads:[~2014-10-19 13:32 UTC|newest]

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

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=5443BEAC.2070107@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=linux@roeck-us.net \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).