Warp3d Voodoo vs. Radeon ClassicOS

[Karlos]

Porting the OS4 drivers for R100/R200 to classic is a bit more involved than potentially writing from scratch, in part because they share an OS4 only resource with the compositing engine. Occasionally there are other obstacles too, for the unwary. For example, the Picasso 96 driver for Permedia had to be changed to get a functuonal Warp3D driver for OS4 since the initial 2D subsystem only cared about minimal alignment of bitmaps and not the specific encoded sizes required for hardware rasterizarion to work. This meant most bitmaps allocated by the graphics system were not suitable for 3D.

[Karlos]

In hindsight, I'm also of the opinion that a less modular warp3d implementation for classic makes sense. For example, having a whole array of precompiled warp3d libraries and you install the one specific to your rtg/3d chip.

This may sound like heresy and a huge retrograde step but it has a lot of advantages for older systems. For example, in warp3d the rtg library component handles allocation of memory and the 3d component has no say, but on an 8MB card the allocation strategy that works best will nor be the same as some 128MB one. Also, it would remove many layers of indirection and partial features like multiple card support that add a lot of complexity. Finally, just support v4 and v5 vertex arrays and emulate the v3 calls using them. A single drop in library that will either work or fail to open if it isn't correct for your system.

[Karlos]

As I see it the problems are:
* Finding the people that have the time, skills and inclination. Writing hardware drivers is time consuming and a pain in the rear to debug.
* Getting access to the legacy W3D source. It has moved on since OS4.
* Identifying all the other problems. As I said before, even the 2D drivers for OS4 use the 3D engine for compositing so you know the hardware is initialised correctly. Its likely that a legacy R200 driver will need more set up as it can't depend on anything being done for it.
* Your new 68K R200 driver may suffer memory management problems without work to the rtg driver component. that in turn many need changes to Picasso driver.
* You may have even more problems if your card is in a Mediator1200, at least from the software side.
* Maybe GRexx owners want someblove too.
* And finally, doing all this without elbox wanting to kick you where it hurts, because apparently they don't like other people writing drivers for their stuff.

If you think a bounty can address these then great.

[Karlos]

Drivers for later cards under OS4 have to use 3D gpu functions since there aren't any 2D functions.

My point is that the OS4 Warp3D driver for R100/200 relies on functionality nor available to OS3.x, so a back port becomes a bit more involved.

[Karlos]

Wow, it takes a lot of coders to be second best. :hammer:

Taking part is what matters.

[Karlos]

I think I stand by my earlier point. A single warp3d library replacement, pre compiled for a specific GPU/PCI/rtg combo is the only way to get past all the issues, technical and political. The source can and should be as modular as you like, but you need a fresh start implementation wise. A driver for warp3d on the classic just isn't likely to happen. As it stands, reimplementing the API in a totally separate project doesn't violate anything and already happened with wazp3d. Use OpenPCI to get around elbox's self destructive desire to crush any third party drivers and open source the whole thing.

[Karlos]

My point was that Karlos is one of the AmigaOS developers Jim. Specifically GPU driver development and Warp3D.

Was, more like. I got married and had kids since then...

[Karlos]

Toss in the fact that my A1 decided to join its departed siblings a few years ago now, then the HD on which all my development work died suddenly before I could back it up properly (and still remains to be recovered). Lots to repair and do, but the fact is I have far bigger and more important responsibilities these days.

One day, when the munchkins are a bit older I may get some time for my old hobby. Assuming any of my Amiga gear even works by then.

[Karlos]

This is why developers should use services like github etc.

I was preparing to migrate my personal svn repo and also back up everything else both locally and where appropriate to cloud storage. There was zero warning of the HD failure, I nothing in smart, etc. In an epic example of irony, the day I'd set aside to do this was the exact same day I saw the Disk Boot Failure message.

I believe the drive controller board or firmware failed and as such it's recoverable. It's also expensive.

[Karlos]

Everything I did on OS4 was at least in their version control repository. It was all my own stuff that I lost.