@kas1e
Very nice progress!

It's great that you're able to fix old bugs and missing things and improve our hardware.
And may I ask what the advantage is of having a GeForce 2 driver?
Wouldn't it be more beneficial to have a Radeon R300 driver in AmigaOS?

@Ami603

Yup its marked as Beta, so its still a work in progress.

@PetrolQuote:

Antialiasing I made a conscious decision to use graphics.library rather than anything more sophisticated, so probably not.

Gradients and transparency - possibly, I'm unsure if libsvgtiny supports them.

@derfs

Just compiled your driver and tested it on qemu under debian 13,
the mouse pointer appears briefly with a bluish tint, then dissapears as soon as i click or move it, never to be seen again.
Tried both Virtio-gpu and virtio-gpu-gl,with same result.
I am using pegasos 2 version.CPU is AMD Ryzen 3 7320C with Radeon Graphics.

@smarkusg
Yes, USB boot was the first thing i add once make UHCI working better than original : you can use USB CD-ROM too btw, and not only on UHCI but also on EHCI and even OHCI :) It wasn't hard after CFE/x1000 patches once i realised that to make thing be visibly in amigaboot, all it's need it to be "block" device doesn't matter if it USB or CD or HDD/SSD/etc.

Currently USB boot is the heaven for me on pegasos2 for real tests: if not that, i had to boot always from CD which kind of unpossible for fast work.

Right now i need to deal with this "RTAS" issues so to make Radeon cards works over bridge on public kernel if possible, and then can make wide release of first version (also of course fixing what you find too)

To add some tease i also add basic support for NVidia cards into the firmware, and have output on AGP version of Geforce2, but, to make any use of it i also want ot make 2D driver for OS4 (that why i started this another topic). Without 3D of course, just some basic 2D stuff so to have WB on it, etc, as it's not main thing for now per se, but to just fill the gap so having output in firmware make sense in end of all :)

@smarkusg
The way how Falke did is pure vibe coding, the way how Derfs do is more looks like real programming even with help of AI : i check the logs of repo , and he did quite lot of work for 2 months : he does same as if me does it : disassembly RadeonRX, disasembly PCIGraphics.card, disassembly graphics.library, then used all the opensources variants of all possible related drivers (even no directly os4 ones), and he fully reconstruct private BoardInfo structure which is "closed sourced".

Also, he go the way how RadeonRX driver do : create 2 residents in one binary, one which patch PCIGraphics.card via setmethod so to add "gate" to add more cards to the PCIgraphics.card together with usage of full stuff from PCIgraphics.card, and another resident is actual code.

@kas1e
I don’t know if this will be useful, but I’ve just remembered something…
Falke tried to do something along these lines using AI.
He couldn’t get a new graphics card to initialise via PCIGraphics.card
He created a separate virtovga.card. The graphics card did initialise and was visible in the system, but it couldn’t be started.

@jorg wrote about an entry in p96config in the bootloader and loading a new driver from there. I don’t think that worked.
screen - > https://ibb.co/bRybTDvc

@kas1e
I’ve been testing pegasos2_kas1e.rom a bit more under QEMU
From what I’ve noticed, it’s possible to boot the AOS4 system from USB
It’s also possible to boot Linux from USB... if anyone’s interested, I’ll post a description of my test.
Here is the description:
The QEMU command

testpegU2.hdf = RAW image. On actual hardware, you can connect the system drive via an IDE-to-USB adapter to a USB port – the result will be the same.

show-devs


assigns itself data under the alias ‘usb’

boots the system via the command line

The system boots from USB and works fine

full kernel debug


przesyłanie zdjęć bez kompresji

But those private boardinfo restructurisation are fine already? Just want to use it for my tests

@kas1e

currently no, as its full of debug and not optimized. Its at the 'get anything working' stage.

@derfs
Cool!

If description generated by AI on your link is correct then you do it exactly same way as radeonrx : patching pcigraphics by setmethod. I also see you alreade restructure private boardinfo structures, that nice :)

Btw, is your virtuogpu fast in 2d in compare with any other emulated card ?

@kas1e

Thats how im doing it - see https://github.com/derfsss/VirtIOGPU

The other way is to fake it and add your driver as a known entry.

@All (but mostly Balaton and Joerg):

Want to play with graphics drivers a bit to understand how it all works on low level, and so far found that PCIgraphics.card contain hardcoded list of supported graphics cards (by name of *.chip files or by vendor/ids value?) and adding any new card which not in, can be done or by creating new xxxx.card, or by patching PCIGraphics.card. That correct ?

I just grep on strings inside of PCIgraphics.card, and found those:



So, like anything else is out and if i want to add any new vendor/id/driver-name i need to create own *.card file or patch PCIgraphics.card , right ?


What is interesting, is that PCIGraphics.card does not have RadeonRX.chip string, so that mean RadeonHd there only for supporting "lite" version of the driver which come with the OS4 installation.

I disassembly RadeonRX driver, and found that it do have 2 resident tags : RadeonRX.chip main code, and RXCardPatch cold-start resident. RXCardPatch runs early, and have high priority, so it scan/build RadeonRX card info, and then opens PCIGraphics.card , get its main interface and via SetMethod() replace FindCard() and InitCard(). Then, when time come and PCIGraphics.card runs, it's already patched and do what need to do.

So, the way to add any new card which is not in PCIGraphics.card is probably that one, right ?

@Joerg
Quote:

But at least if it run's before on amigaos4 (i remember it too, it surely were working half way), it can be fixed. At least on aminet i surely see scout_os4 from 2006 and scout_src.

@Chris

Thanks.

Will it be possible to add more features, like gradients, transparency, antialiasing, ... ?

@Petrol

Quote:

Way ahead of you (also no AI used).

https://aminet.net/package/util/dtype/drawing_dt

@Maijestro

What do you mean by VAAPI support? Which SDL APIs are you referring?

There recently has been some discussion on EAB on a potential Amiga port (the author of the game was also in the discussion).

I made a survey on it:

https://docs.google.com/forms/d/e/1FAI ... 4MHuXURq0aQSKkcA/viewform

Note on the 3 options: There are two versions of Apidya Source Code, one is hardware hacking AGA Code which only runs on Classic Amigas with AGA (or Emulation). It could theoretically be expanded to run the new game.

The other is the source of the PC version, highend code in C++ (actually not sure if this would work on a 060 so the option 2 is unsure technically).

Basically the question is "AGA or new systems". The author seems very much to be an AGA hardware hacking guy, but as he put the question up himselves, I made this survey to get a broader public than just EAB readers.

a SVG datatype

I think it would be excellent to include a note indicating that the software was developed with the assistance of AI.