OpenBIOS

openbios@openbios.org

4284 discussions

Build sparc32 openbios
by BALARD Arnaud 03 Mar '19

03 Mar '19

Hi, Openbios ! I try to build a bios sparc32 for qemu. I use the script "./config/scripts/switch-arch sparc32" Initializing build tree ok Creating taget config.mak ok Creating taget rules.mak ok Creating config files ok When I do the "make build-verbose" I get the following error : "PATH/openbios/arch/sparc32/context.c: In function 'switch_to': "PATH/openbios/arch/sparc32/context.c:116:5: error: PIC register clobbered by 'l7' in 'asm' Asm_volatile_("\n\tcall_switch_context" ^~~ Rules.mak:219 « target/arch/sparc32/context.o » failed Make[1]: *** [target/arch/sparc32/context.o error 1 Makefile:32 target "subdir-sparc32" failed Make: *** [subdir-sparc32] error 2 I was try to build ppc and sparc64, that's ok, I can boot on my ppc's bios (not on sparc64, I think I need to do another thing). Do you know what I'm doing wrong for sparc 32 ? Thanks, Libre (C=0) Interne (C=1) Restreint (C=2) Confidentiel (C=3) X [X] Arnaud BALARD Chargé d'Exploitation et d'Affaires EDF - DPNT - DAIP - UNITEP AEI - Groupe SIMU UFPI Bugey CD 20 - BP 70130 01155 LAGNIEU arnaud.balard(a)edf.fr Tél. : 04 37 63 62 72 Un geste simple pour l'environnement, n'imprimez ce message que si vous en avez l'utilité. Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse. Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message. Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus. ____________________________________________________ This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message. E-mail communication cannot be guaranteed to be timely secure, error or virus-free.

3 4

[PATCH v2 0/5] SPARC32/SPARC64: allocate and map both kernel and initrd memory
by Mark Cave-Ayland 15 Feb '19

15 Feb '19

Bootloaders such as SILO will have already allocated and mapped the memory for the kernel and initrd before jumping into the kernel, so this patchset does the same for a kernel/initrd loaded directly by QEMU. Otherwise if the kernel/initrd grow beyond the default 1:1 memory region mapped by the PROM then the kernel will panic when clearing the memory on startup. In order for this to work on SPARC32 then the corresponding QEMU patch at https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg06635.html must also be applied. Signed-off-by: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk> v2: - Add missing PAGE_ALIGN() macro around the ofmem_map() size parameter Mark Cave-Ayland (5): SPARC32: fix obp_arg.argv when no kernel command line specified SPARC32: mark kernel memory as mapped SPARC32: mark initrd memory as mapped and in use before booting kernel SPARC64: mark kernel memory as mapped and in use before booting kernel SPARC64: mark initrd memory as mapped and in use before booting kernel arch/sparc32/boot.c | 2 ++ arch/sparc32/openbios.c | 29 ++++++++++++++++++++--------- arch/sparc64/boot.c | 2 ++ arch/sparc64/boot.h | 2 ++ arch/sparc64/openbios.c | 18 +++++++++++++++++- include/drivers/drivers.h | 2 ++ 6 files changed, 45 insertions(+), 10 deletions(-) -- 2.11.0

1 6

[PATCH 0/5] SPARC32/SPARC64: allocate and map both kernel and initrd memory
by Mark Cave-Ayland 01 Feb '19

01 Feb '19

Bootloaders such as SILO will have already allocated and mapped the memory for the kernel and initrd before jumping into the kernel, so this patchset does the same for a kernel/initrd loaded directly by QEMU. Otherwise if the kernel/initrd grow beyond the default 1:1 memory region mapped by the PROM then the kernel will panic when clearing the memory on startup. In order for this to work on SPARC32 then the corresponding QEMU patch at https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg06635.html must also be applied. Signed-off-by: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk> Mark Cave-Ayland (5): SPARC32: fix obp_arg.argv when no kernel command line specified SPARC32: mark kernel memory as mapped SPARC32: mark initrd memory as mapped and in use before booting kernel SPARC64: mark kernel memory as mapped and in use before booting kernel SPARC64: mark initrd memory as mapped and in use before booting kernel arch/sparc32/boot.c | 2 ++ arch/sparc32/openbios.c | 29 ++++++++++++++++++++--------- arch/sparc64/boot.c | 2 ++ arch/sparc64/boot.h | 2 ++ arch/sparc64/openbios.c | 18 +++++++++++++++++- include/drivers/drivers.h | 2 ++ 6 files changed, 45 insertions(+), 10 deletions(-) -- 2.11.0

1 5

[PATCH] SPARC32: divide physical memory reg property into physical SIMM sized ranges
by Mark Cave-Ayland 25 Jan '19

25 Jan '19

Currently the /memory node reg property is set to a single range encompassing the entire physical RAM of the machine. This seems to cause issues with Solaris when booting on QEMU SS-10 and SS-20 machines whereby having just a single entry causes the top of physical memory to be calculated incorrectly and triggers a panic on boot. Instead copy the behaviour of OBP which is to divide the reg property into a set of ranges representing the physical SIMM arrangement in the machine, which fixes the error and allows Solaris to boot under the QEMU SS-10 and SS-20 machines. Signed-off-by: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk> --- arch/sparc32/boot.h | 2 +- arch/sparc32/lib.c | 14 +++++++++----- arch/sparc32/openbios.c | 6 +++++- 3 files changed, 15 insertions(+), 7 deletions(-) diff --git a/arch/sparc32/boot.h b/arch/sparc32/boot.h index e372acc..366e0f6 100644 --- a/arch/sparc32/boot.h +++ b/arch/sparc32/boot.h @@ -33,5 +33,5 @@ extern struct linux_mlist_v0 *ptphys; extern struct linux_mlist_v0 *ptmap; extern struct linux_mlist_v0 *ptavail; -void ob_init_mmu(void); +void ob_init_mmu(uint32_t simm_size); void init_mmu_swift(void); diff --git a/arch/sparc32/lib.c b/arch/sparc32/lib.c index e88c0bf..727929c 100644 --- a/arch/sparc32/lib.c +++ b/arch/sparc32/lib.c @@ -294,12 +294,13 @@ static void ignore_dfault_addr(void) } void -ob_init_mmu(void) +ob_init_mmu(uint32_t simm_size) { ucell *memreg; ucell *virtreg; phys_addr_t virtregsize; ofmem_t *ofmem = ofmem_arch_get_private(); + int i, c; /* Find the phandles for the /memory and /virtual-memory nodes */ push_str("/memory"); @@ -315,14 +316,17 @@ ob_init_mmu(void) ofmem_register(s_phandle_memory, s_phandle_mmu); /* Setup /memory:reg (totphys) property */ - memreg = malloc(3 * sizeof(ucell)); - ofmem_arch_encode_physaddr(memreg, 0); /* physical base */ - memreg[2] = (ucell)ofmem->ramsize; /* size */ + c = ofmem->ramsize / simm_size; + memreg = malloc(3 * c * sizeof(ucell)); + for (i = 0; i < c; i++) { + ofmem_arch_encode_physaddr(&memreg[i * 3], simm_size * i); /* physical base */ + memreg[i * 3 + 2] = simm_size; /* size */ + } push_str("/memory"); fword("find-device"); PUSH(pointer2cell(memreg)); - PUSH(3 * sizeof(ucell)); + PUSH(3 * c * sizeof(ucell)); push_str("reg"); PUSH_ph(s_phandle_memory); fword("encode-property"); diff --git a/arch/sparc32/openbios.c b/arch/sparc32/openbios.c index 3ec8fd7..17a6550 100644 --- a/arch/sparc32/openbios.c +++ b/arch/sparc32/openbios.c @@ -42,6 +42,7 @@ struct hwdef { unsigned long aux1_offset, aux2_offset; uint64_t dma_base, esp_base, le_base; uint64_t tcx_base; + uint32_t simm_size; int intr_ncpu; int mid_offset; int machine_id_low, machine_id_high; @@ -65,6 +66,7 @@ static const struct hwdef hwdefs[] = { .dma_base = 0x78400000, .esp_base = 0x78800000, .le_base = 0x78c00000, + .simm_size = 0x2000000, .mid_offset = 0, .machine_id_low = 32, .machine_id_high = 63, @@ -86,6 +88,7 @@ static const struct hwdef hwdefs[] = { .dma_base = 0xef0400000ULL, .esp_base = 0xef0800000ULL, .le_base = 0xef0c00000ULL, + .simm_size = 0x4000000, .mid_offset = 8, .machine_id_low = 64, .machine_id_high = 65, @@ -107,6 +110,7 @@ static const struct hwdef hwdefs[] = { .dma_base = 0xef0081000ULL, .esp_base = 0xef0080000ULL, .le_base = 0xef0060000ULL, + .simm_size = 0x4000000, .mid_offset = 8, .machine_id_low = 66, .machine_id_high = 66, @@ -874,7 +878,7 @@ arch_init( void ) openbios_init(); modules_init(); - ob_init_mmu(); + ob_init_mmu(hwdef->simm_size); ob_init_iommu(hwdef->iommu_base); bind_func("(sparc32-dma-alloc)", dma_alloc); -- 2.11.0

1 1

Qemu 3.1.0 Sparc still does'nt boot Solaris 8 for SS-20
by Ulrich Gräpel 01 Jan '19

01 Jan '19

Just gave the latest Qemu a try to boot an emulated SparcStation 20 from the original Solaris install CD: /opt/qemu-3.1.0/sparc-softmmu/qemu-system-sparc \ -M SS-20 -m 256 \ -nographic \ -monitor telnet::3001,server,nowait \ -cdrom /mnt/iso/sol-8-hw4-install-sparc32.iso \ -boot d The resulting output: Configuration device id QEMU version 1 machine id 65 Probing SBus slot 0 offset 0 Probing SBus slot 1 offset 0 Probing SBus slot 2 offset 0 Probing SBus slot 3 offset 0 Probing SBus slot 15 offset 0 Invalid FCode start byte CPUs: 1 x TI,TMS390Z55 UUID: 00000000-0000-0000-0000-000000000000 Welcome to OpenBIOS v1.1 built on Oct 5 2018 08:20 Type 'help' for detailed information Trying cdrom:d... Not a bootable ELF image Loading a.out image... Loaded 7680 bytes entry point is 0x4000 bootpath: /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f ,800000/sd@2,0:d switching to new context: SunOS Release 5.8 Version Generic_108528-29 32-bit Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved. \ panic[cpu0]/thread=f0244020: BAD TRAP: type=9 (Data fault) rp=f0243624 addr=0 mmu_fsr=126 rw=1 occurred in module "unix" due to a NULL pointer dereference qemu: fatal: Trap 0x29 while interrupts disabled, Error state pc: f0163298 npc: f016329c %g0-7: 00000000 f00c220c 3024a52c f024fe14 4000020d f0243b88 00000000 f0244020 %o0-7: 00001fff 00001000 00001000 f5c89000 00000000 f5918240 f02500a0 f0074d94 %l0-7: fbcf4834 f013cc18 00000001 f026eb30 f5917c60 f02727e0 f5917c40 00001010 %i0-7: f5c89000 00001000 00000001 00000000 00000000 f5917c68 f0250100 f013d4a4 %f00: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 %f08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 %f16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 %f24: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 psr: 40000fc5 (icc: ---- SPE: SP-) wim: 00000020fsr: 00000000 y: 00000000 Everything works fine though, if configured for the default SparcStation 5 (SS-5). I also tried other machine types: The only working configuration is the SS-5. I guess there is some issue with the device tree.

3 3

openbios support for netboot? (qemu-system-sparc32/solaris)
by Joe Dery 22 Dec '18

22 Dec '18

Intrepid openBIOS developers, Though not new news, thank you for providing an openBIOS that is able to boot solaris in qemu-system-sparc32! While I am able to disk boot (with qcow2 image containing ufs filesystems), but would prefer to serve as much of my guest filesystem from NFS as possible. Netboot allows a 'diskless' system, so that is the most extreme case, but I'm open to other suggestions. Does OpenBIOS 1.1 (eg the snapshot attached to QEMU GIT HEAD as of last Friday) support boot net:rarp, boot net:dhcp, or any other more manual method of providing the kernel&parameters? I haven't been able to find this in the documentation or code so I imagine it does not. PS - FWIW this is the command line I am presently using for a 'disk0' boot. Note that the tftp/bootfile do not do anything, but I included them as an example based on the other qemu documentation. qemu/sparc-softmmu/qemu-system-sparc \ -net nic,macaddr=00:03:BA:04:A5:AD -net user,hostfwd=tcp::8023-:23,hostfwd=tcp::5911-:5911,tftp=/tftpboot,bootfile=inetboot.sun4m \ -hda sol8_36G.disk.install \ -nographic -serial telnet:0.0.0.0:3000,server \ -m 256 PPS Mark Cave-Ayland, it appears you're active on this list. Thanks again for your help (now years ago!) fixing the MUTEX_HELD & related problems in 2.6.... the current GIT still runs clean. I have not really worked with QEMU since ~2.6, around that time I picked up a SunBlade 1000, which is supported by the old kernel I need, and is able to run the (mostly CC compile) workloads an order of magnitude faster. QEMU remains interesting for applications requiring less performance, e.g. lmgrd license server.

2 1

SVN to github migration
by BALATON Zoltan 09 Dec '18

09 Dec '18

Hello, The links on the pages https://www.openfirmware.org/Open_Firmware https://www.openfirmware.org/SmartFirmware https://www.openfirmware.org/OpenBOOT seem to be broken since the SVN to github migration. I think these are now at https://github.com/openbios but the above pages should also be updated to point to there instead. Thank you, BALATON Zoltan

2 1

Need help : sparc64 ULTRA5 under Solaris 7 64 bits
by BALARD Arnaud 07 Dec '18

07 Dec '18

Bonjour, je vous envoie un mail car j'essaie de virtualiser une machine ULTRA5 sous solaris 7 en 64 bits. j'ai réussi à démarrer sur un cd solaris 7 32bits pour restaurer les partitions sur mon disque virtuel (ufsrestore). Quand j'essaie de démarrer avec qemu-system-sparc64 j'obtiens l'erreur "no valid state has been set by load or init-program" dans le prompt qemu "Not linux kernel image, Not a bootable ELF image, Not a bootable a.out image, Not a bootable FCode image" au bout d'un certain nombre de test ma dernière commande ressemble à ca : sparc64-softmmu#./qemu-system-sparc64 -M sun4u -bios /usr/local/share/qemu/openbios-sparc64 -m 256 -drive file=/home/qemu/QEMU_SRV/SRV.qcow2 -prom-env "auto-boot?=flase" Je vois bien mon disque présent sur /pci@1fe,0/pci@1,1/ide@3/ide@0/disk@0 est-t 'il possible de virtualiser une machine ultra5 sous solaris 7 64bits ? La barrière de ma machine réel ressemble à ca : Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 400MHz),OpenBoot 3.25 256 MB.... J'ai entendu parler de ce patch : https://patchwork.kernel.org/patch/9175879/ ou est-ce qu'il y a une configuration à faire dans sparc64-softmmu ? Je ne sais pas si il peut m'aider à trouver mon bonheur. Dans l'attente de votre réponse, merci. **************************************************************************************************************************************************************** Hello, I send you an email because I try to virtualize an ULTRA5 machine under solaris 7 in 64 bits. I managed to boot on a cd solaris 7 32bits to restore the partitions on my virtual disk (ufsrestore). When I try to start with qemu-system-sparc64 I get the error "no valid state has been set by load or init-program" in the qemu prompt "Not linux kernel image, Not a bootable ELF image, Not a bootable a.out image, Not a bootable Image mode " after a certain number of tests my last command looks like this: sparc64-softmmu#./qemu-system-sparc64 -M sun4u -bios /usr/local/share/qemu/openbios-sparc64 -m 256 -drive file=/home/qemu/QEMU_SRV/SRV.qcow2 -prom-env "auto-boot? = flase" I can see my disk present on /pci@1fe,0/pci@1,1/ide@3/ide@0/disk@0 is it possible to virtualize an ultra5 machine under solaris 7 64bits? The barrier of my real machine looks like this: Sun Ultra 5/10 UPA / PCI (UltraSPARC-IIi 400MHz), OpenBoot 3.25 256 MB .... I heard about this patch: https://patchwork.kernel.org/patch/9175879/ or is there a configuration to do in sparc64-softmmu? I do not know if he can help me find my happiness. Looking forward to your reply, thank you. Libre (C=0) Interne (C=1) Restreint (C=2) Confidentiel (C=3) X [X] Arnaud BALARD Chargé d'Exploitation et d'Affaires EDF - DPNT - DAIP - UNITEP AEI - Groupe SIMU UFPI Bugey CD 20 - BP 70130 01155 LAGNIEU arnaud.balard(a)edf.fr Tél. : 04 37 63 62 72 Un geste simple pour l'environnement, n'imprimez ce message que si vous en avez l'utilité. Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse. Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message. Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus. ____________________________________________________ This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message. E-mail communication cannot be guaranteed to be timely secure, error or virus-free.

2 1

[PATCH 0/4] Add virtio-blk driver support
by Mark Cave-Ayland 18 Oct '18

18 Oct '18

These patches add support for booting from virtio-blk (PCI) devices as used by QEMU. Patches 1 and 2 add bootindex support which is the new way for passing boot order information from QEMU to OpenBIOS. Note that there are also corresponding patches for QEMU required, without which the generated device paths will be incorrect and cause virtio boot to fail. Patch 3 adds the legacy virtio-blk driver (it follows the 0.9 rather than the 1.0 specification). Patch 4 enables the new driver for both PPC and SPARC64 architectures so that virtio-blk devices will be usable out-of-the-box with QEMU. Once these patches have been applied to OpenBIOS (along with the corresponding fw path fixes for QEMU) it is possible to boot from virtio-blk devices like this: PPC: ./qemu-system-ppc -drive file=debian-9.0-powerpc-NETINST.iso,if=none,index=0,id=cd,media=cdrom \ -device virtio-blk-pci,drive=cd,bootindex=0 -m 256 -boot d SPARC: ./qemu-system-sparc64 -drive debian-9.0-sparc64-NETINST.iso,if=none,index=0,id=cd,media=cdrom \ -device virtio-blk-pci,bus=pciB,drive=cd,bootindex=0 -m 256 -boot d -nographic Signed-off-by: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk> Mark Cave-Ayland (4): ppc: add bootindex support SPARC64: add bootindex support drivers: add legacy virtio-blk driver config: enable virtio-blk driver for default PPC and SPARC64 builds arch/ppc/qemu/init.c | 55 ++++- arch/sparc64/boot.c | 2 +- arch/sparc64/boot.h | 2 +- arch/sparc64/openbios.c | 38 +++- config/examples/ppc_config.xml | 1 + config/examples/sparc64_config.xml | 1 + drivers/build.xml | 1 + drivers/pci.c | 18 ++ drivers/pci_database.c | 4 +- drivers/pci_database.h | 1 + drivers/virtio.c | 424 +++++++++++++++++++++++++++++++++++++ drivers/virtio.h | 331 +++++++++++++++++++++++++++++ include/drivers/drivers.h | 4 + 13 files changed, 862 insertions(+), 20 deletions(-) create mode 100644 drivers/virtio.c create mode 100644 drivers/virtio.h -- 2.11.0

3 8

Ppc guest debugging?
by Jd Lyons 14 Oct '18

14 Oct '18

I need to try and debug the macOS trampoline inits during the early boot process of OS 9. I’m thinking Qemu supports this, but I’m unsure how to set it up? I installed gdb-multiarch and started qemu with: Qemu-system-ppc -s -S The launched gdb-multiarch and connected to port 1234. Is this the correct toolchain for debugging PPC code on an X86 host, or do I need to do something else?

3 11

← Newer
1
...
7
8
9
10
11
12
13
...
429
Older →

Jump to page: