All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Max Filippov <jcmvbkbc@gmail.com>,
	Richard Henderson <rth@twiddle.net>,
	qemu-devel <qemu-devel@nongnu.org>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu
Date: Mon, 20 Oct 2014 23:23:51 +0800	[thread overview]
Message-ID: <54452907.1080501@gmail.com> (raw)
In-Reply-To: <5443D191.40107@roeck-us.net>

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?

For kernel:

  put rootfs.cpio in kernel root directory,
  mv qemu_microblaze_defconfig to arch/microblaze/config/mmu_defconfig
  make ARCH=microblaze CROSS_COMPILE=/usr/bin/microblaze-linux-gnu- mmu_defconfig
  make -j4

For qemu:

  ./configure --target-list="microblaze-softmmu" --enable-fdt --disable-kvm
  make -j4
  /upstream/xilinx/qemu/microblaze-softmmu/qemu-system-microblaze -M petalogix-s3adsp1800 -kernel ../linux-xlnx/arch/microblaze/boot/linux.bin  -no-reboot -append "console=ttyUL0,115200 doreboot" -nographic
  Early console on uartlite at 0x84000000
  bootconsole [earlyser0] enabled
  Ramdisk addr 0x00000000, 
  FDT at 0x905413f4
  Linux version 3.14.0-dirty (root@localhost.localdomain) (gcc version 4.9.1 20140717 (Red Hat Cross 4.9.1-1) (GCC) ) #1 Mon Oct 20 23:15:34 CST 2014
  setup_cpuinfo: initialising
  setup_cpuinfo: No PVR support. Using static CPU info from FDT
  wt_msr
  setup_memory: max_mapnr: 0x8000
  setup_memory: min_low_pfn: 0x90000
  setup_memory: max_low_pfn: 0x98000
  setup_memory: max_pfn: 0x98000
  Zone ranges:
    DMA      [mem 0x90000000-0x97ffffff]
    Normal   empty
  Movable zone start for each node
  Early memory node ranges
    node   0: [mem 0x90000000-0x97ffffff]
  On node 0 totalpages: 32768
  free_area_init_node: node 0, pgdat c03b4774, node_mem_map c0574000
    DMA zone: 256 pages used for memmap
    DMA zone: 0 pages reserved
    DMA zone: 32768 pages, LIFO batch:7
  early_printk_console remapping from 0x84000000 to 0xffffd000
  pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
  pcpu-alloc: [0] 0 
  Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
  Kernel command line: console=ttyUL0,115200
  PID hash table entries: 512 (order: -1, 2048 bytes)
  Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
  Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
  Memory: 124192K/131072K available (2883K kernel code, 120K rwdata, 752K rodata, 1572K init, 198K bss, 6880K reserved)
  Kernel virtual memory layout:
    * 0xffffe000..0xfffff000  : fixmap
    * 0xffffd000..0xffffe000  : early ioremap
    * 0xf0000000..0xffffd000  : vmalloc & ioremap
  NR_IRQS:33
  /plb@0/interrupt-controller@81800000: num_irq=4, edge=0xa
  ERROR: CPU CCF input clock not found
  /plb@0/timer@83c00000: irq=1
  ERROR: timer CCF input clock not found
  ERROR: Using CPU clock frequency
  xilinx_timer_set_mode: shutdown
  xilinx_timer_set_mode: periodic
  sched_clock: 32 bits at 62MHz, resolution 16ns, wraps every 68719476720ns
  Calibrating delay loop... Killed

The compiler information:

  [root@localhost qemu]# gcc -v
  Using built-in specs.
  COLLECT_GCC=gcc
  COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.3/lto-wrapper
  Target: x86_64-redhat-linux
  Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-initfini-array --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-isl=/builddir/build/BUILD/gcc-4.8.3-20140624/obj-x86_64-redhat-linux/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.8.3-20140624/obj-x86_64-redhat-linux/cloog-install --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
  Thread model: posix
  gcc version 4.8.3 20140624 (Red Hat 4.8.3-1) (GCC) 
  [root@localhost qemu]# ld -v
  GNU ld version 2.23.2
  [root@localhost linux-xlnx]# /usr/bin/microblaze-linux-gnu-gcc -v
  Using built-in specs.
  COLLECT_GCC=/usr/bin/microblaze-linux-gnu-gcc
  COLLECT_LTO_WRAPPER=/usr/libexec/gcc/microblaze-linux-gnu/4.9.1/lto-wrapper
  Target: microblaze-linux-gnu
  Configured with: ../gcc-4.9.1-20140717/configure --bindir=/usr/bin --build=x86_64-redhat-linux-gnu --datadir=/usr/share --disable-decimal-float --disable-dependency-tracking --disable-gold --disable-libgomp --disable-libmudflap --disable-libquadmath --disable-libssp --disable-nls --disable-plugin --disable-shared --disable-silent-rules --disable-sjlj-exceptions --disable-threads --enable-checking= --enable-gnu-unique-object --enable-initfini-array --enable-languages=c,c++ --enable-linker-build-id --enable-nls --enable-obsolete --enable-targets=all --exec-prefix=/usr --host=x86_64-redhat-linux-gnu --includedir=/usr/include --infodir=/usr/share/info --libexecdir=/usr/libexec --localstatedir=/var --mandir=/usr/share/man --prefix=/usr --program-prefix=microblaze-linux-gnu- --sbindir=/usr/sbin --sharedstatedir=/var/lib --sysconfdir=/etc --target=microblaze-linux-gnu --with-bugurl=http://bugzilla.redhat.com/bugzilla/ --with-linker-hash-style=gnu --with-newlib --with-sysroot=/usr/microblaz
e-linux-gnu/sys-root --with-system-libunwind --with-system-zlib --without-headers --with-isl=/builddir/build/BUILD/gcc-4.9.1-20140717/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.9.1-20140717/cloog-install
  Thread model: single
  gcc version 4.9.1 20140717 (Red Hat Cross 4.9.1-1) (GCC) 
  [root@localhost linux-xlnx]# /usr/bin/microblaze-linux-gnu-ld -v
  GNU ld version 2.24.0-5.fc20 20140613

Welcome any suggestions or completions.

Thanks.
-- 
Chen Gang

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

  reply	other threads:[~2014-10-20 15:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-19 13:37 [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu Chen Gang
2014-10-19 13:38 ` Max Filippov
2014-10-19 13:58   ` Chen Gang
2014-10-19 14:58     ` Guenter Roeck
2014-10-20 15:23       ` Chen Gang [this message]
2014-10-21  4:37         ` Guenter Roeck
2014-10-21 10:41           ` Chen Gang
2014-10-21 16:43             ` Guenter Roeck
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=54452907.1080501@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=jcmvbkbc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.