OpenBIOS

openbios@openbios.org

3 participants
4293 discussions

Re: Openbios code for IRQ or interrupt handling?
by Jd Lyons 20 Feb '25

20 Feb '25

I can’t figure out this race condition but it causes an IRQ storm. I feel like I’m in the old days of PC’s when to had IRQ conflicts and had to sort them yourself deep in the bios. As a Mac person I only had to deal with that on a few friends PC’s. Starting the second CPU in a on state rather than halted just makes the race condition worse, twice as fast, and Openbios doesn’t want to get to the prompt, but throwing 3, 8, or 9 CPUs at it in a running state gets me to the prompt, but it ignores -prom-env setting with anything more that three. 300% cpu usage just speeds up the race condition and IRQ storm so IDE craps out before you can load BootX or a linux kernel. Then noting happens but the IRG storm and GPIO 1 asserting 0, likely to all the other CPUs, and that is likely the race conditions and pulling that low trigger the IRQ storm. I can’t make it stop, I even tied all IRQ and Interrupts handling to CPU0, and that working until the OS Kenral loads and starts sending stuff to CPU1, which is still in a halted state unless I start it with my hack. Even with only CPU0 dealing with IRQs and Interrupts the race condition is still there and the IRQ storm. I have to figure out why GPIO 1keeps getting triggered in a loop to pull low???? > On Feb 19, 2025, at 1:29 AM, Jd Lyons <lyons_dj(a)yahoo.com> wrote: > > Thanks Mark, I got side traced thinking open-pic when I should have been looking at GPIO because it is the one that is the gpio-parent there should be no interrupt-parent property. I think the gpio phandle is 7. > > Can you tell me how IRQ’s get assigned to CPU0? > > Interrupts? > >> On Feb 18, 2025, at 5:00 PM, Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk> wrote: >> >> On 18/02/2025 21:34, Jd Lyons via OpenBIOS wrote: >> >>> I don’t know why, I can’t seem to get Openbios to set and interrupt-parent in the init.c for any /cpus, this code should work, no? >>> void add_cpu_nodes(void) { >>> int num_cpus = fw_cfg_read_i32(FW_CFG_NB_CPUS); >>> printk("Detected %d CPUs\\n", num_cpus); >>> /* Ensure /cpus node exists */ >>> phandle cpus_node = dt_find_by_path("/cpus"); >>> if (!cpus_node) { >>> printk("ERROR: /cpus node not found! Delaying CPU setup.\\n"); >>> return; >>> } >>> /* Wait until the interrupt controller exists */ >>> phandle intc_node = NULL; >>> int retries = 5; >>> while (retries-- > 0) { >>> intc_node = dt_find_by_path("/pci/mac-io/@40000"); >> >> Is this for the mac99 machine? If so you probably want /pci@f2000000/mac-io@c/interrupt-controller@40000 (see the output of show-devs for the full device paths). >> >>> if (intc_node) { >>> break; >>> } >>> printk("Waiting for /pci/mac-io/@40000...\\n"); >>> msleep(100); // Wait 100ms before retrying >>> } >>> if (!intc_node) { >>> printk("ERROR: Interrupt controller (/pci/mac-io/@40000) not found! SMP will not work.\\n"); >>> return; >>> } >>> for (int i = 0; i < num_cpus; i++) { >>> phandle cpu_node = dt_new_node(cpus_node); >>> if (!cpu_node) { >>> printk("ERROR: Failed to create CPU node for CPU %d!\\n", i); >>> continue; >>> } >>> dt_set_property_string(cpu_node, "device_type", "cpu"); >>> dt_set_property_string(cpu_node, "compatible", "PowerPC,G4"); >>> /* Assign a unique CPU interrupt */ >>> int cpu_irq[2] = { 16 + i, 0 }; >>> dt_set_property_cells(cpu_node, "interrupts", cpu_irq, 2); >>> printk("CPU %d assigned IRQ %d\\n", i, cpu_irq[0]); >>> /* Ensure interrupt-parent is set */ >>> dt_set_property_phandle(cpu_node, "interrupt-parent", intc_node); >>> printk("CPU %d linked to interrupt-parent /pci/mac-io/@40000\\n", i); >>> /* Register CPU ID */ >>> PUSH(i); >>> fword("encode-int"); >>> push_str("reg"); >>> fword("property"); >>> fword("finish-device"); >>> printk("Initialized CPU %d\\n", i); >>> } >>> } >> >> >> ATB, >> >> Mark. >

3 13

Openbios code for IRQ or interrupt handling?
by Jd Lyons 18 Feb '25

18 Feb '25

Mark, anyone, is there code in Openbios that deals with IRQ’s or Interrupts? I’m tracking down an issue with IRQ’s casing the IDE,, RTC, USB…… not to work with SMP patches and I’m not sure if it’s an issue with QEMU or Openbios patches I have applied.

2 4

Re: OpenMPIC controller emulation in qemu
by Jd Lyons 15 Feb '25

15 Feb '25

I think the soft-reset is what we may need but the gpio stuff may also be important. Last login: Sat Feb 15 12:30:21 on ttys000 jam@Mac ~ % cd q3/qemu/build jam@Mac build % ./qemu-system-ppc64-unsigned -m 1024 -cpu 7455 -hda ~/Snow*.img -prom-env 'boot-args=-v -x -s' -smp 2,cores=1,threads=1,sockets=2 -accel tcg,thread=multi -d guest_errors -cdrom /Users/jam/Downloads/ubuntu-mate-16.04.1-desktop-powerpc.iso -boot d -device usb-mouse -boot d -prom-env 'auto-boot?=false' -M mac99,via=pmu -nographic -bios /Users/jam/Documents/openbios-qemu.elf WARNING: Image format was not specified for '/Users/jam/SnowLeopardPPC.img' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. s>> et_property: NULL phandle >> ============================================================= >> OpenBIOS 1.1 [Feb 14 2025 10:28] >> Configuration device id QEMU version 1 machine id 1 >> CPUs: 2 >> Memory: 1024M >> UUID: 00000000-0000-0000-0000-000000000000 >> CPU type PowerPC,G4 >> CPU type PowerPC,G4 milliseconds isn't unique. Welcome to OpenBIOS v1.1 built on Feb 14 2025 10:28 0 > dev /cpus/@0 .properties name "PowerPC,G4" device_type "cpu" cpu-version 80010302 d-cache-size 8000 i-cache-size 8000 d-cache-sets 80 i-cache-sets 80 d-cache-block-size 20 i-cache-block-size 20 tlb-sets 40 tlb-size 80 timebase-frequency 17d7840 clock-frequency 35a4e900 bus-frequency 5f5e100 state "running" reservation-granule-size 20 reg 00000000 available 00004000 03ffc000 04800000 3b458000 3fe10000 401f0000 translations 04000000 00800000 04000000 00000000 3fc58000 001b8000 3fc58000 00000000 fff00000 00100000 3ff00000 00000000 ok 0 > dev /cpus/@1 .properties name "PowerPC,G4" device_type "cpu" cpu-version 80010302 d-cache-size 8000 i-cache-size 8000 d-cache-sets 80 i-cache-sets 80 d-cache-block-size 20 i-cache-block-size 20 tlb-sets 40 tlb-size 80 timebase-frequency 17d7840 clock-frequency 35a4e900 bus-frequency 5f5e100 state "running" reservation-granule-size 20 reg 00000001 ok 0 > > On Feb 15, 2025, at 12:24 PM, Jd Lyons <lyons_dj(a)yahoo.com> wrote: > > Don’t give up yet, we can get more people involved….. > > Here is the dump of the DP MDD /cpus node, there is some interesting stuff there…. > > > > > > > > > > > > 0 > dev /cpus/@0 .properties > name PowerPC,G4 > > device_type cpu > reg 00000000 > cpu-version 80010201 > state running > clock-frequency 33a848a8 > bus-frequency 07f0db85 > config-bus-frequency 07f0b5db > timebase-frequency 01fc36e1 > reservation-granule-size00000020 > tlb-sets 00000040 > tlb-size 00000080 > d-cache-size 00008000 > i-cache-size 00008000 > d-cache-sets 00000080 > i-cache-sets 00000080 > i-cache-block-size 00000020 > d-cache-block-size 00000020 > graphics > performance-monitor > altivec > data-streams > l2-cache ff87fd10 > l2cr 80080000 > existing 00000000 80000000 80000000 80000000 > available 00003000 7fffd000 d0000000 20000000 > translations 00000000 00003000 00000000 00000010 80000000 00080000 > 80000000 00000028 80080000 00001000 80080000 00000028 > 80081000 00001000 80081000 00000028 f0000000 00010000 > f0000000 00000028 f0800000 00001000 f0800000 00000028 > f0c00000 00001000 f0c00000 00000028 f2000000 00010000 > f2000000 00000028 f2800000 00001000 f2800000 00000028 > f2c00000 00001000 f2c00000 00000028 f4000000 00010000 > f4000000 00000028 f4800000 00001000 f4800000 00000028 > f4c00000 00001000 f4c00000 00000028 f5000000 00001000 > f5000000 00000028 f5200000 00200000 f5200000 00000028 > f5200000 00200000 f5200000 00000028 > ... 00000140 bytes total > cpu-info 8410c0bc 80080000 80010201 00000400 00000000 00000000 > 00000000 00000000 > soft-reset 00000071 <<—————————Here > gpio-mask 00000001 <<—————————Here > gpio-value 00000001 <<—————————Here > performance-monitor-cnt-enable 00000072 > timebase-enable 00000073 <<—————————Here > gpio-parent ff95c318 <<—————————Here > > ok > 0 > dev /cpus/@1 ok > 0 > .properties > name PowerPC,G4 > > device_type cpu > reg 00000001 > cpu-version 80010201 > state stopped > clock-frequency 33a848a8 > bus-frequency 07f0db85 > config-bus-frequency 07f0b5db > timebase-frequency 01fc36e1 > reservation-granule-size00000020 > tlb-sets 00000040 > tlb-size 00000080 > d-cache-size 00008000 > i-cache-size 00008000 > d-cache-sets 00000080 > i-cache-sets 00000080 > i-cache-block-size 00000020 > d-cache-block-size 00000020 > graphics > performance-monitor > altivec > data-streams > l2-cache ff880fd0 > l2cr 80080000 > cpu-info 8431c0bc 00000000 80010201 00000400 fff0376c 0000b010 > 00060110 21524110 > soft-reset 00000072 <<—————————Here > gpio-mask 00000001 <<—————————Here > gpio-value 00000001 <<—————————Here > timebase-enable 00000073 > cpu-interrupt-enable 00000074 <<—————————Here > gpio-parent ff95c318 <<—————————Here > > > > > > > > > > > > > > > > > > > > > customer-sw-config 694-4782 > > > color-code ff11 > scb# 00000000 > display-config-info ffffffff ffffffff > name device-tree > copyright Copyright 1983-2002 Apple Computer, Inc. All Rights Reserved > device_type bootrom > system-id 0000000000000 > #address-cells 00000001 > #size-cells 00000001 > clock-frequency 07f0db85 > AAPL,add-fcode-file ff860928 > > ok > 0 > > >> On Feb 15, 2025, at 11:53 AM, Andrew Randrianasulu <randrianasulu(a)gmail.com> wrote: >> >> >> >> сб, 15 февр. 2025 г., 19:37 Jd Lyons <lyons_dj(a)yahoo.com <mailto:lyons_dj@yahoo.com>>: >>> Mate Live CD does default to SMP: >> >> >> Thanks for testing. >> >> Unfortunately,I think I just fundamentally misunderstood how IRQ vs IPI works so .. in absence of someone with working understanding of how all this really work this probably will not progress much ... >> >> sorry! >> >> >>> >>> >> ============================================================= >>> >> OpenBIOS 1.1 [Feb 14 2025 10:28] >>> >> Configuration device id QEMU version 1 machine id 1 >>> >> CPUs: 2 >>> >> Memory: 1024M >>> >> UUID: 00000000-0000-0000-0000-000000000000 >>> >> CPU type PowerPC,G4 >>> >> CPU type PowerPC,G4 >>> milliseconds isn't unique. >>> Welcome to OpenBIOS v1.1 built on Feb 14 2025 10:28 >>> >>> 0 > boot Trying cd:,\\:tbxi... >>> >> switching to new context: >>> >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> call-method color!: exception -21 >>> >> call-method color! failed with error ffffffdf >>> >>> Config file read, 2702 bytes >>> >>> Welcome to Ubuntu MATE 16.04.1 LTS (Xenial Xerus)! >>> >>> This is an Ubuntu MATE live CDROM, >>> built on 20160719. >>> >>> The default option is 'live'. >>> >>> If the system fails to boot at all (the typical >>> symptom is a white screen which doesn't go away), >>> use 'live video=ofonly'. >>> >>> Press the tab key for a list of options, or type >>> 'help' for help. >>> >>> ************************************ >>> If in doubt, just press Enter, and if that >>> doesn't work, type 'live video=ofonly'. >>> ************************************ >>> Welcome to yaboot version 1.3.16 >>> Enter "help" to get some basic usage information >>> >>> WARNING: Bootstrap partition type is wrong: "Apple_HFS" >>> type should be: "Apple_Bootstrap" >>> >>> boot: live >>> Please wait, loading kernel... >>> Elf32 kernel loaded... >>> Loading ramdisk... >>> ramdisk loaded at 01b00000, size: 22562 Kbytes >>> OF stdout device is: /pci@f2000000/mac-io@c/escc@13000/ch-a@13020 >>> Preparing to boot Linux version 4.4.0-31-powerpc-smp (buildd@denneed03) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 13 00:23:04 UTC 2016 (Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13) >>> Detected machine type: 00000400 >>> command line: >>> memory layout at init: >>> memory_limit : 00000000 (16 MB aligned) >>> alloc_bottom : 03109000 >>> alloc_top : 30000000 >>> alloc_top_hi : 40000000 >>> rmo_top : 30000000 >>> ram_top : 40000000 >>> found display : /pci@f2000000/QEMU,VGA@e, opening... done >>> copying OF device tree... >>> Building dt strings... >>> Building dt structure... >>> Device tree strings 0x0320a000 -> 0x0320a5ea >>> Device tree struct 0x0320b000 -> 0x03212000 >>> Quiescing Open Firmware ... >>> Booting Linux via __start() ... >>> Trying to read invalid spr 1012 (0x3f4) at 00000000c0015f18 >>> Hello World ! >>> setup_arch: initmem >>> arch: exit >>> smp_core99_probe >>> smp_core99_kick_cpu >>> smp_core99_kick_cpu done >>> [ 5.131667] Processor 1 is stuck. >>> [ 5.131667] Processor 1 is stuck. >>> >>> It tries to kickstart SMP but Processor 1 is stuck! >>> >>> >>> >>> [ 54.955254] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 54.955664] ata1.00: failed command: READ DMA >>> [ 54.955950] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 54.955950] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 54.956472] ata1.00: status: { DRDY } >>> [ 85.930746] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 85.931000] ata1.00: failed command: READ DMA >>> [ 85.931149] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 85.931149] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 85.931569] ata1.00: status: { DRDY } >>> [ 116.970014] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 116.970250] ata1.00: failed command: READ DMA >>> [ 116.970402] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 116.970402] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 116.970814] ata1.00: status: { DRDY } >>> [ 148.010809] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 148.011048] ata1.00: failed command: READ DMA >>> [ 148.011195] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 148.011195] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 148.011610] ata1.00: status: { DRDY } >>> [ 178.986502] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 178.986758] ata1.00: failed command: READ DMA >>> [ 178.986906] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 178.986906] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 178.987328] ata1.00: status: { DRDY } >>> [ 209.962237] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 209.962474] ata1.00: failed command: READ DMA >>> [ 209.962622] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 209.962622] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 209.963038] ata1.00: status: { DRDY } >>> [ 209.966227] blk_update_request: I/O error, dev sda, sector 0 >>> [ 209.966534] Buffer I/O error on dev sda, logical block 0, async page read >>> [ 240.937824] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 240.938059] ata1.00: failed command: READ DMA >>> [ 240.938205] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 240.938205] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 240.938642] ata1.00: status: { DRDY } >>> [ 245.234331] INFO: task swapper/0:1 blocked for more than 120 seconds. >>> [ 245.234688] Not tainted 4.4.0-31-powerpc-smp #50-Ubuntu >>> [ 245.234864] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. >>> [ 245.235822] INFO: task kworker/0:1:30 blocked for more than 120 seconds. >>> [ 245.236016] Not tainted 4.4.0-31-powerpc-smp #50-Ubuntu >>> [ 245.236176] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. >>> [ 271.977850] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 271.978090] ata1.00: failed command: READ DMA >>> [ 271.978241] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 271.978241] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 271.978653] ata1.00: status: { DRDY } >>> [ 302.122355] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 302.122600] ata1.00: failed command: READ DMA >>> [ 302.122746] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 302.122746] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 302.123172] ata1.00: status: { DRDY } >>> [ 333.162381] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 333.162651] ata1.00: failed command: READ DMA >>> [ 333.162795] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 333.162795] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 333.163229] ata1.00: status: { DRDY } >>> [ 364.138445] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 364.138696] ata1.00: failed command: READ DMA >>> [ 364.138844] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 364.138844] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 364.139276] ata1.00: status: { DRDY } >>> [ 365.233579] INFO: task swapper/0:1 blocked for more than 120 seconds. >>> [ 365.233825] Not tainted 4.4.0-31-powerpc-smp #50-Ubuntu >>> [ 365.233992] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. >>> [ 365.234445] INFO: task kworker/0:1:30 blocked for more than 120 seconds. >>> [ 365.234633] Not tainted 4.4.0-31-powerpc-smp #50-Ubuntu >>> [ 365.234792] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. >>> [ 365.235276] INFO: task kworker/u4:2:79 blocked for more than 120 seconds. >>> [ 365.235467] Not tainted 4.4.0-31-powerpc-smp #50-Ubuntu >>> [ 365.235625] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. >>> [ 395.178285] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 395.178536] ata1.00: failed command: READ DMA >>> [ 395.178681] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 395.178681] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 395.179112] ata1.00: status: { DRDY } >>> [ 395.180504] blk_update_request: I/O error, dev sda, sector 0 >>> [ 395.180710] Buffer I/O error on dev sda, logical block 0, async page read >>> [ 426.154784] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 426.155025] ata1.00: failed command: READ DMA >>> [ 426.155173] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 426.155173] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 426.155585] ata1.00: status: { DRDY } >>> [ 457.130476] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 >>> [ 457.130713] ata1.00: failed command: READ DMA >>> [ 457.130859] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in >>> [ 457.130859] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) >>> [ 457.131276] ata1.00: status: { DRDY } >>> [ 485.233894] INFO: task swapper/0:1 blocked for more than 120 seconds. >>> [ 485.234188] Not tainted 4.4.0-31-powerpc-smp #50-Ubuntu >>> [ 485.234347] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. >>> [ 485.234787] INFO: task kworker/0:1:30 blocked for more than 120 seconds. >

1 0

Re: OpenMPIC controller emulation in qemu ?
by Jd Lyons 12 Feb '25

12 Feb '25

Did you guys ever make more progress on adding spm to the Mac99 machine? Any patches?

1 0

[PATCH v3 0/3] esp: fixups to correctly terminate successful SCSI commands
by Mark Cave-Ayland 22 Sep '24

22 Sep '24

This series is an extension of the v2 patch with a couple of modifications to clear the FIFO at the start of the command, and to poll the ESP interrupt register to detect the end of the transfer. Signed-off-by: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk> v3: - Clear FIFO before issuing ESP command - Poll ESP interrupt register to detect end of transfer v2: - Fix typo in commit message spotted by Zoltan Mark Cave-Ayland (3): esp: clear FIFO before issuing ESP command esp: use ESP rather than DMA interrupt to detect end of transfer esp: correctly terminate successful SCSI commands drivers/esp.c | 37 ++++++++++++++++++++++++------------- 1 file changed, 24 insertions(+), 13 deletions(-) -- 2.39.2

1 4

[PATCH v2] README: change reference from LinuxBIOS to coreboot
by Mark Cave-Ayland 22 Sep '24

22 Sep '24

The linuxbios.org website does not exist anymore, so point the reader towards coreboot.org instead. Signed-off-by: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk> Resolves: https://github.com/openbios/openbios/issues/17 Reviewed-by: Philippe Mathieu-Daudé <philmd(a)linaro.org> Tested-by: Philippe Mathieu-Daudé <philmd(a)linaro.org> --- README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) v2: - Add R-B and T-B tags from Phil - Replace Coreboot with coreboot as indicated by Segher diff --git a/README b/README index 9f4b705..bf7684a 100644 --- a/README +++ b/README @@ -17,8 +17,8 @@ kernel and three interfaces for user interaction, device initialization and client (operating system) control. While far not all possible applications of OpenBIOS are implemented yet, -a lot of functionality is already there. OpenBIOS can be used to enhance -LinuxBIOS (http://www.linuxbios.org), or be booted from any multiboot +a lot of functionality is already there. OpenBIOS can be used as a payload +for coreboot (http://www.coreboot.org), or be booted from any multiboot capable bootloader to bring Open Firmware to your machine. OpenBIOS can also be used when an operating system is already running. It provides the needed OpenFirmware functionality to MOL (MacOnLinux) to boot MacOS -- 2.39.2

1 1

[PATCH] cuda: fix len calculation in cuda_adb_req
by Amadeusz Sławiński 22 Sep '24

22 Sep '24

When advancing buffer by 1, len should be shorthened by appropriate amount, instead of setting it to -1. Found with cppcheck. Signed-off-by: Amadeusz Sławiński <amade(a)asmblr.net> --- drivers/cuda.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/cuda.c b/drivers/cuda.c index 86d2ddb..93a935a 100644 --- a/drivers/cuda.c +++ b/drivers/cuda.c @@ -162,7 +162,7 @@ static int cuda_adb_req (void *host, const uint8_t *snd_buf, int len, } } else { pos = buffer + 1; - len = -1; + len -= 1; } memcpy(rcv_buf, pos, len); -- 2.44.0

2 2

[PATCH v2] esp: correctly terminate successful SCSI commands
by Mark Cave-Ayland 11 Sep '24

11 Sep '24

An upcoming series for QEMU's ESP emulation will check that ESP commands are only issued according to their valid states as listed in the datasheet, and otherwise generate an illegal command interrupt. Currently if a SCSI command is expected to return no data or transfers data successfully, the ASC is not returned to its disconnected state. This means that any subsequent ESP initiator commands should be rejected until the SCSI bus transaction is terminated. Update the ESP driver so that if a SCSI command is successful then the ICCS and MSGACC commands are issued by the host to complete the SCSI transaction. This ensures that the ASC is returned to the disconnected state which allows the ESP to accept subsequent SCSI commands without generating an illegal command interrupt. Signed-off-by: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk> --- drivers/esp.c | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) v2: - Fix typo in commit message spotted by Zoltan diff --git a/drivers/esp.c b/drivers/esp.c index 0880ab2..b1b10f4 100644 --- a/drivers/esp.c +++ b/drivers/esp.c @@ -113,7 +113,8 @@ do_command(esp_private_t *esp, sd_private_t *sd, int cmdlen, int replylen) return status; } if (replylen == 0) { - return 0; + /* No reply expected, ICCS and MSGACC to complete */ + goto done; } /* Target went to status phase instead of data phase? */ if ((status & ESP_STAT_PMASK) == ESP_STATP) { @@ -139,10 +140,18 @@ do_command(esp_private_t *esp, sd_private_t *sd, int cmdlen, int replylen) DPRINTF("do_command_reply: status 0x%x\n", status); - if ((status & ESP_STAT_TCNT) != ESP_STAT_TCNT) + if ((status & ESP_STAT_TCNT) != ESP_STAT_TCNT) { return status; - else - return 0; // OK + } + +done: + // ICCS and MSGACC sequence to complete + esp->ll->regs[ESP_CMD] = ESP_CMD_ICCSEQ; + (void)esp->ll->regs[ESP_FDATA]; // Ignore 1st byte for now + (void)esp->ll->regs[ESP_FDATA]; // Ignore 2nd byte for now + esp->ll->regs[ESP_CMD] = ESP_CMD_MOK; + + return 0; // OK } // offset is in sectors -- 2.39.2

1 1

[PATCH] esp: correctly terminate successful SCSI commands
by Mark Cave-Ayland 08 Sep '24

08 Sep '24

An upcoming series for QEMU's ESP emulation will check that ESP commands are only issued according to their valid states as listed in the datasheet, and otherwise generate an illegal command interrupt. Currently if a SCSI command is expected to return no data or transfers data successfully, the ASC is not returned to its disconnected state. This means that any subsequent ESP initiator commands should be rejected until the the SCSI bus transaction is terminated. Update the ESP driver so that if a SCSI command is successful then the ICCS and MSGACC commands are issued by the host to complete the SCSI transaction. This ensures that the ASC is returned to the disconnected state which allows the ESP to accept subsequent SCSI commands without generating an illegal command interrupt. Signed-off-by: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk> --- drivers/esp.c | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/drivers/esp.c b/drivers/esp.c index 0880ab2..b1b10f4 100644 --- a/drivers/esp.c +++ b/drivers/esp.c @@ -113,7 +113,8 @@ do_command(esp_private_t *esp, sd_private_t *sd, int cmdlen, int replylen) return status; } if (replylen == 0) { - return 0; + /* No reply expected, ICCS and MSGACC to complete */ + goto done; } /* Target went to status phase instead of data phase? */ if ((status & ESP_STAT_PMASK) == ESP_STATP) { @@ -139,10 +140,18 @@ do_command(esp_private_t *esp, sd_private_t *sd, int cmdlen, int replylen) DPRINTF("do_command_reply: status 0x%x\n", status); - if ((status & ESP_STAT_TCNT) != ESP_STAT_TCNT) + if ((status & ESP_STAT_TCNT) != ESP_STAT_TCNT) { return status; - else - return 0; // OK + } + +done: + // ICCS and MSGACC sequence to complete + esp->ll->regs[ESP_CMD] = ESP_CMD_ICCSEQ; + (void)esp->ll->regs[ESP_FDATA]; // Ignore 1st byte for now + (void)esp->ll->regs[ESP_FDATA]; // Ignore 2nd byte for now + esp->ll->regs[ESP_CMD] = ESP_CMD_MOK; + + return 0; // OK } // offset is in sectors -- 2.39.2

2 3

[PATCH] README: change reference from LinuxBIOS to Coreboot
by Mark Cave-Ayland 06 Sep '24

06 Sep '24

The linuxbios.org website does not exist anymore, so point the reader towards coreboot.org instead. Signed-off-by: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk> Resolves: https://github.com/openbios/openbios/issues/17 --- README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README b/README index 9f4b705..7e299b0 100644 --- a/README +++ b/README @@ -17,8 +17,8 @@ kernel and three interfaces for user interaction, device initialization and client (operating system) control. While far not all possible applications of OpenBIOS are implemented yet, -a lot of functionality is already there. OpenBIOS can be used to enhance -LinuxBIOS (http://www.linuxbios.org), or be booted from any multiboot +a lot of functionality is already there. OpenBIOS can be used as a payload +for Coreboot (http://www.coreboot.org), or be booted from any multiboot capable bootloader to bring Open Firmware to your machine. OpenBIOS can also be used when an operating system is already running. It provides the needed OpenFirmware functionality to MOL (MacOnLinux) to boot MacOS -- 2.39.2

3 3

Jump to page: