Recent content by Melkhior

Checl also /HALT, it will also prevent the CPU from doing anything if stuck low.

Emphasis on the 'might'. Beware that: (a) applications that use FP instructions directly just won't run on the LC version (b) applications that don't use FP at all, or use it via built-in emulation, will not benefit from the FPU in the non-LC (c) applications that uses SANE, or applications...

@Jockelill was willing to give it a go, so with an appropriate bitstream (to use the proper clock signal and pseudo-slot number, IIsi and SE/30 are $9 while the IIfx and LC3 are $E) he gave it a shot - and it works! Though the position of the HDMI connector will prevent the case from closing...

Makes sense. Thanks for the confirmation. If that board was released as late as '98, or even in '97 or '96, spending money on acceleration for systems already obsolete twice (CPU first 68k->PPC '94, I/O second NuBus -> PCI '95) and unlikely to cause any additional sales doesn't sound like a...

'sVidAuxParams' isn't awfully well documented... google only finds it in your thread about the Thunder II @ 1600x1200 (which I had forgotten and where you already mentioned this... not getting any younger it seems). It has an entry 123 in the appropriate header (the one you quoted), and that's...

There's audio because it was fun to try and get audio to work :-) In fact as detailed in the QuadraFPGA thread, audio comes with its own HDMI PHY, which only does windowboxed resolution - the 'standard' Litex PHY has hardware resolution, but no audio, it's just DVI signaling in a HDMI connector...

At most 5 if using a pseudo-slot design and the 20 MHz half-speed clock, as there's only 6 slot area in the memory map ($9 to $E inclusive). Using 'slow space' ($6 area) you can use the 20 MHz clock without interfering with the NuBus area. It makes the software abit more complex, but the...

The NuBusFPGA should definitely work in there. Well, now that your IIsiFPGA is working in a IIsi and a SE/30, it might be time to try a bitstream for the IIfx as well :-) I was worried the weird PDS implementation might cause issue, but it is working for the SEthernet/30, so worth a shot...

It was introduced in late '98 if MacTech is to be believed. But clearly for PowerMacs, I wonder if they would work on a 68k Mac... I'm surprised anyone still created NuBus device as late as that (says the guy that did one in 2022...). I'll be content with the first Highly Desirable Macintosh...

Well, I'll be a pedant and claim the QuadraFPGA is the third time, following the NuBusFPGA and IIsiFPGA at first and second :) Although they are similar enough that they can probably all be counted as one and just want all three medals 'cause I'm greedy :) More seriously, I don't remember any...

Any pointers to the relevant documentation? There DeclROM isn't particularly well documented post-DCDMF3 and I can't find an explicit documentation of the Display Manager, let alone the ROM part of it. (... some more googling...) Apparently, from Develop 25 (March '96), you need the "Display...

I'll try and post something later this week (if @Jockelill doesn't beat me to it ;-) ), but it's somewhat frustrating: MacOS (8.1 at least) seems to auto-generate the names in the list, so if you have the same resolution twice (once windowboxed, once 'hardware') then you get the same name twice...

No, the reset system needed between resolution / depth change isn't reliable and I haven't figured out why yet... so it still a matter of re-changing resolution/depth to force a reset :-(

Just forgot to update the public thread with the new status, nothing new vs. the ones you tested some weeks ago :-) They are in the repo as (a) 'LitexPHY' and (b) 'AltPHY'.

Update on that: this particular limitation has been (somewhat) lifted. The QuadraFPGA (and NuBusFPGA, IIsiFPGA) now has the choice of two different Highly Desirable Macintosh Interface PHY (the part that generate the appropriate signals to the connector): (a) the Litex-style one (written in...