qemu-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: QEMU boot kernel for ppc e300c3 problem


From: Ali Vatankhah
Subject: Re: QEMU boot kernel for ppc e300c3 problem
Date: Mon, 6 Sep 2021 12:10:54 +0430

Thank you Thomas for your reply.
> You definitly need to select the right CPU type, too. So for your case,
> you'd need to add the "-cpu e300c3" command line switch
 Also added this option but nothing changed and the command does not print anything.
> But the CPU is only a part of the hardware, you also need to select a
> supported board with the "-M" command line parameter
 How can I add a machine to Qemu for this CPU? I have a real MPC8308 board and am really interested in contributing to Qemu.
and another question, is it required to specify a machine type? I built a kernel for Powerpc g4 (7400) with the same Yocto (standard qemuppc machine) and Qemu runs the kernel without specifying cpu or machine, although Qemu supports PowerPC 7400 (g4) and a machine that uses this CPU (mac99):
qemu-system-ppc -kernel vmlinux -nographic

>> =============================================================
>> OpenBIOS 1.1 [Mar 16 2021 08:16]
>> Configuration device id QEMU version 1 machine id 2
>> CPUs: 1
>> Memory: 128M
>> UUID: 00000000-0000-0000-0000-000000000000
>> CPU type PowerPC,750
milliseconds isn't unique.
Welcome to OpenBIOS v1.1 built on Mar 16 2021 08:16
>> [ppc] Kernel already loaded (0x01000000 + 0x00c7d3f8) (initrd 0x00000000 + 0x00000000)
>> [ppc] Kernel command line:
>> switching to new context:
OF stdout device is: /pci@80000000/mac-io@10/escc@13000/ch-a@13020
Preparing to boot Linux version 4.14.79-yocto-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 PREEMPT Thu Sep 2 08:18:46 UTC 2021
Detected machine type: 00000400
command line:
memory layout at init:
  memory_limit : 00000000 (16 MB aligned)
  alloc_bottom : 01c82000
  alloc_top    : 08000000
  alloc_top_hi : 08000000
  rmo_top      : 08000000
  ram_top      : 08000000
found display   : /pci@80000000/QEMU,VGA@1, opening... done
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x01c83000 -> 0x01c83552
Device tree struct  0x01c84000 -> 0x01c8b000
Quiescing Open Firmware ...
Booting Linux via __start() @ 0x01000000 ...
Hello World !
[    0.000000] Total memory = 128MB; using 256kB for hash table (at c7fc0000)
[    0.000000] Linux version 4.14.79-yocto-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 PREEMPT Thu Sep 2 08:18:46 UTC 2021
[    0.000000] Found a Heathrow mac-io controller, rev: 0, mapped at 0xfdf80000
[    0.000000] PowerMac motherboard: PowerMac G3 (Silk)
[    0.000000] Using PowerMac machine description
[    0.000000] bootconsole [udbg0] enabled
[    0.000000] -----------------------------------------------------
[    0.000000] Hash_size         = 0x40000
[    0.000000] phys_mem_size     = 0x8000000
[    0.000000] dcache_bsize      = 0x20
[    0.000000] icache_bsize      = 0x20
[    0.000000] cpu_features      = 0x0000000000200472
[    0.000000]   possible        = 0x0000000005a6fd7f
[    0.000000]   always          = 0x0000000000000000
[    0.000000] cpu_user_features = 0x8c000001 0x00000000
[    0.000000] mmu_features      = 0x00000001
[    0.000000] Hash              = 0xc7fc0000
[    0.000000] Hash_mask         = 0xfff
[    0.000000] -----------------------------------------------------
[    0.000000] Found Grackle (MPC106) PCI host bridge at 0x0000000080000000. Firmware bus number: 0->0
[    0.000000] PCI host bridge /pci@80000000 (primary) ranges:
.....
.....

It seems that Qemu selects an appropriate CPU and machine for that, is it true?

Thanks


reply via email to

[Prev in Thread] Current Thread [Next in Thread]