LineOf7s wrote: ↑Mon Oct 28, 2024 4:31 pm
I know what the P96 driver is, and I know of its use with RTG cards, and I know of using it and the Native driver instead of FBlit+FText... but I'm not sure I'm wrapping my head around what the P96 driver will do for an Indivision, exactly. Any ideas? I mean, it
sounds like it could be cool, but I can't work out
how. Some sort of pseudo/halfway-house RTG-like solution? Extra screen modes beyond ECS/OCS? Perhaps to do with the ECS-on-an-OCS-Denise functionality he mentions?
The Indivision v1 had a framebuffer and famously somebody on A1K wrote a P96 driver that could use it to produce 256 color RTG in 640x480, 800x600 and 1024x768. It was more of a toy than anything useful. It was the slowest RTG solution out there (though I was able to use workbench friendly programs like iBrowse and ImageFX with it well enough.) Actually, given that people used to use things like processor intensive S-HAM mode or pseudo framebuffers like Graffiti, HAM-E or DCTV to render high(er) color images on an Amiga, this was a much more elegant solution.
A bigger issue was stability - the driver was a hack and it was always a coin toss whether the device would be come confused about what mode it should be running in (framebuffer or Denise) and would cause issues. At any rate, the indivision v2 and v3 removed the frambeuffer so all fan-development of the driver was halted.
The v4 not only adds the framebuffer back but Jens says he has better logic for mode changes, which could address the major issue with using the v1 as a light-duty RTG board. Also, it is implied that a new driver will be written by the P96 developer directly, so we'd have a formal, supported driver.
According to Jens, the v4 framebuffer also adds some kind of 2D acceleration.