OpenBIOS

Download

openbios@openbios.org

June 2025

4 participants
2 discussions

June 10, 2025

I’m trying to fix ms and get-msecs so they return other than zero, but I can’t seem to build because The Forth word milliseconds is not registered or available at dictionary build time—it is only registered at runtime by the C code. diff --git a/arch/ppc/qemu/init.c b/arch/ppc/qemu/init.c index 253394c..d00a940 100644 --- a/arch/ppc/qemu/init.c +++ b/arch/ppc/qemu/init.c @@ -39,6 +39,9 @@ #define UUID_FMT "%02x%02x%02x%02x-%02x%02x-%02x%02x-%02x%02x-%02x%02x%02x%02x%02x%02x" +extern void ob_milliseconds(void); + + struct cpudef { unsigned int iu_version; const char *name; @@ -914,6 +917,7 @@ arch_of_init(void) openbios_init(); modules_init(); setup_timers(); + bind_func("milliseconds", ob_milliseconds); bind_func("ppc-dma-alloc", dma_alloc); feval("['] ppc-dma-alloc to (dma-alloc)"); diff --git a/drivers/timer.c b/drivers/timer.c index de999e1..da2d7eb 100644 --- a/drivers/timer.c +++ b/drivers/timer.c @@ -14,6 +14,10 @@ #include "timer.h" #include "asm/io.h" +void ob_tb_fetch(void); +void ob_tb_frequency(void); +void ob_milliseconds(void); + #if defined(CONFIG_X86) || defined(CONFIG_AMD64) void setup_timers(void) @@ -26,7 +30,7 @@ static void load_timer2(unsigned int ticks) /* Set up the timer gate, turn off the speaker */ outb((inb(PPC_PORTB) & ~PPCB_SPKR) | PPCB_T2GATE, PPC_PORTB); outb(TIMER2_SEL | WORD_ACCESS | MODE0 | BINARY_COUNT, - TIMER_MODE_PORT); + TIMER_MODE_PORT); outb(ticks & 0xFF, TIMER2_PORT); outb(ticks >> 8, TIMER2_PORT); } @@ -51,7 +55,7 @@ unsigned long currticks(void) ticks = inb(TIMER2_PORT); ticks |= inb(TIMER2_PORT) << 8; outb(TIMER2_SEL | WORD_ACCESS | MODE0 | BINARY_COUNT, - TIMER_MODE_PORT); + TIMER_MODE_PORT); outb(0, TIMER2_PORT); outb(0, TIMER2_PORT); @@ -71,6 +75,46 @@ unsigned long currticks(void) #ifdef CONFIG_PPC +#include "libopenbios/bindings.h" +typedef unsigned long long uint64_t; + +void ob_tb_fetch(void) +{ + unsigned long tbu0, tbu1, tbl; + do { + __asm__ volatile ("mftbu %0" : "=r"(tbu0)); + __asm__ volatile ("mftb %0" : "=r"(tbl)); + __asm__ volatile ("mftbu %0" : "=r"(tbu1)); + } while (tbu0 != tbu1); + + PUSH((cell)tbu0); + PUSH((cell)tbl); +} + +void ob_tb_frequency(void) +{ + PUSH(25000000); // 25 MHz typical for mac99 +} + +/* + * Real 64-bit ms, scaled for QEMU's low-resolution timebase (~20 ticks/second) + * Change divisor if your tb@ ticks/second changes! + */ +void ob_milliseconds(void) +{ + unsigned long tbu0, tbu1, tbl; + uint64_t tb; + uint64_t ms; + do { + __asm__ volatile ("mftbu %0" : "=r"(tbu0)); + __asm__ volatile ("mftb %0" : "=r"(tbl)); + __asm__ volatile ("mftbu %0" : "=r"(tbu1)); + } while (tbu0 != tbu1); + tb = (((uint64_t)tbu0) << 32) | tbl; + ms = (tb * 1000ULL) / 20ULL; // 20 is your tb@ ticks per real second + PUSH((cell)ms); +} + void setup_timers(void) { /* nothing to do */

4 16

PCI BAR qemu Mac99
by Jd Lyons June 4, 2025

June 4, 2025

Balaton when you realigned the memory hole on Qemu from Size: 0x70000000 (1792 MB, 0x80000000–0xF0000000). To 256MB was there a specific issue that you can recall? The reason I ask is I’m trying to use PCI Passthrough of a PCI-E Radeon X1950XT with 265MB of VRAM and I assume, tho I’ve not checked yet, it uses 64bit BARs. Qemu skips BARs marked as 64Bit. if ((*p_omask & 0x0000000f) == 0x4) { /* 64 bits memory mapping */ PCI_DPRINTF("Skipping 64 bit BARs for %s\n", config->path); return; } So when the FCode ROM tries to setup the BAR 0x10 and 0x18 we are failing there: 400369f : (compile) 2 [ 0xa7 ] 40036a0 : (compile) or [ 0x24 ] 40036a2 : (compile) [ 0x9e6 ] 40036a4 : (compile) [ 0xb40 ] 40036a5 : (compile) b(;) [ 0xc2 ] 40036a6 : b(lit) [ 0x10 ] 40036ac : my-space [ 0x103 ] 40036ad : + [ 0x1e ] 40036ae : b(") [ 0x12 ] (const) config-l@ 40036ba : $call-parent [ 0x209 ] byte-load: exception caught! ok I was just going to bypass the 64bit BAR check in Openbios as 265MB is still within the 4GB address space of 32bit but I’m going to need more space in the hole for the other BARs, no?

4 22