Nice work Ratte. It is always hand to have a choice of drivers.

_________________
AmigaOne X1000, A4000(T), A3000, A2000, A1200(T), A1200, A500, CD32, Minimig+ARM, FPGA Arcade, Chameleon64, C-One, C128, C128D, C64C, C64, VIC-20, CBM 8032, CBM4032, Efika, Ultimate64

I don't want to split my gfx card mem as 128MB gfx mem + 128MB slow main mem.

Am I allowed to split it as 250MB gfx mem + 6MB shared PCI mem (for other cards that need it)?

I need way more than 128MB gfx mem, which is sort of the reason for buying a 256MB gfx mem card

_________________
Wanna try a wonderfull magical Amiga strategy game?
Total Chaos AGA

Quote:

I need way more than 128MB gfx mem, which is sort of the reason for buying a 256MB gfx mem card

Even on "NG" Amigas you dont need so much gfx mem.

_________________
Amiga Developer
Amiga 500, Efika, Mac Mini and PowerBook

Thanks

On my A4000 the radeon only works as a memory card with the elbox drivers, if i try to display anything i only get garbage on the (radeon)screen and then the machine locks up. I hope to have better luck with this driver.

Great! It seems I will give it a go with my prometheus

_________________
The only spanish amiga news web page/club: CUAZ

I hope he can find someone with the GREX so it can be supported as well

_________________
- Proud Member Of The Belgian Amigaclub Since 2003 -

The Belgian Amiga Club on FACEBOOK !

The Belgian Amiga Club Website

Quote:

Even on "NG" Amigas you dont need so much gfx mem.

Haha, Good joke!

That reminds me to :
"No one will need more than 637 kb of memory for a personal computer."

Turn Compositing on with 1600x1200 in 32bit and open 4-6 screens in that Resolution and voila

_________________
I´m back in 2023 on Classic Amiga with my A1200/Blizzard1230IB@50Mhz, 32MB RAM, AmigaOS3.2 and ROMs, Indivision AGA MK3, Author of Amiga-Flipclock (OS4)

On AOS4 + compositing in 16bit 1920x1080WB one can run out of 64M VRAM pretty easily. With 32bit WB, one application is enough, for example when using many tabs in web browser I run out of VRAM.
(not that severe as at the same time I'm usually also out of RAM on my SAM440). It would be nice to be able to multitask like in the old days.

+it seems that when less than half of VRAM is free, I do not get HW acceleration any more.

My next new everyday Amigan system must have 1GB+1GB at least.
(In the meanwhile I will see how efficient MOS is with RAM & VRAM on old Macs...)

Last edited by KimmoK on 03-Dec-2012 at 12:54 PM.

_________________
- KimmoK
// For freedom, for honor, for AMIGA
//
// Thing that I should find more time for: CC64 - 64bit Community Computer?

Quote:

Turn Compositing on with 1600x1200 in 32bit and open 4-6 screens in that Resolution and voila

Thank you but I prefer using 1920x1200 in 32-bit

_________________
Amiga Developer
Amiga 500, Efika, Mac Mini and PowerBook

Fantastic news. I've been looking forward to this since it was 1st mentioned at the start of the year.

What cards are supported by the way please? My Amithlon box is a core2duo, ergo new enough to only have pci express + pci as gfx card options, so it'd be great to be able to use a pci express card (so as to free up one of the 3 pci slots).

Also, is it possible to use dual display output, either through the one card, or 2 cards? I seem to recall there being a video some time back showing this feature?

Also, I have 1gig in my amithlon box, could this potentially, cause issues? (some hardware has issues beyond 1gig of ram with Amithlon).

I'll post some results from something a bit beefier (core2duo@3.86ghz/1gig dual channel ddr2-1066) than the duron you posted results from once I find out (and acquire) a radeon gfx card if youre interested to see how raw grunt influences this openpci driver vs. using powerfb ?

Thanks for your efforts, Im quite excited at the prospect of being able to finally use more than 8meg gfx memory with my amithlon machine :)

This new driver actually kind of works for me, atleast better then the elbox one, i did a quick install and just copied over the radeon monitor file and radeon.card and changed screenmode to a radeon one and with this driver my machine doesn't lock up like it does with the elbox driver. Icons isn't displayed, the background is not showing and the mouse pointer is just garbage and it doesn't allocate gfx mem as system memory but this gives me hope that i someday will be able to use my radeon :)

Will test this better and install all the mediator configfiles etc later, any hints of how to get it working is welcome.

this is how it looks like now when i use radeon for my workbench screen.



Config:
A4000
CSPPC 060
Mediator DI
Voodoo3
RV280 Radeon 9200 Pro (with 256mb ram i think)
realtek 100Mbit nic
Spider

All jumpers except for winsize is closed as my machine will crash when loading workbench if it's closed.

Last edited by smf on 06-Dec-2012 at 10:22 PM.

@smf

Does your voodoo seem to work?

_________________
Wanna try a wonderfull magical Amiga strategy game?
Total Chaos AGA

@smf: for a perfect testrun
- remove ALL pci-cards, except radeon
- close ALL jumpers on der mediator-bridge
winsize needs to be 512MB with a 256MB Radeon,
I/O-mem must be mapped beside 256MB GFX-mem.
so you need 256MB + some more bytes
CONFIGSWITCH is good for "expanded" systems.
bridge-resources are configured behind the pci-mem-area.

example (my config): possible Z3-Configspace = $4000.0000 - $7FFF.FFFF
$4000.0000 - $5FFF.FFFF 512MB PCI-MEM
$6000.0000 - $60FF.FFFF 16MB PCI-BRIDGE
$6100.0000 - $61FF.FFFF 16MB DENEB
$7000.0000 - $7FFF.FFFF 256MB ZORRAM
+ some stuff in Z2-Configspace

copy ALL files from the openpci-radeon archive 1:1 to your system (backup your settings!)

Quote:

I don't want to split my gfx card mem as 128MB gfx mem + 128MB slow main mem. Am I allowed to split it as 250MB gfx mem + 6MB shared PCI mem (for other cards that need it)? I need way more than 128MB gfx mem, which is sort of the reason for buying a 256MB gfx mem card

This is V0.99 only ...

technical reason: the register for the mousepointer is only able to point inside the first 128MB (27 Bits) ... even on 256MB cards with ONE memblock.
at the moment the mousepointer is at the end of gfxmem ... i will place it to the beginning of gfxmem in later releases.

Quote:

This is V0.99 only ... technical reason: the register for the mousepointer is only able to point inside the first 128MB (27 Bits) ... even on 256MB cards with ONE memblock. at the moment the mousepointer is at the end of gfxmem ... i will place it to the beginning of gfxmem in later releases.

Thank you!!!!!!

I really really really do need more than 128MB of gfx mem! We are cooking up 1280x1024x32bit game with a ton of animation and we need the mem!

ur my hero. Please fix the 256MB problem before Elbox does. Thanxx0rz

Maybe you have to make a rule that I have to allocate 2 different gfx mem allocs or maybe you have to make a new function for me to call? Do whatever it takes.

_________________
Wanna try a wonderfull magical Amiga strategy game?
Total Chaos AGA

well done ratte!!.

hows the performance? , on a classic Amiga with P96 for instance..

_________________
See my blog and collection website! . https://www.blog.amigaguru.com

DRAW()-function .. up to 8 - 20 times faster.
P96Speed-module included ... just follow the link

Hello,

Two weeks ago I read on a1k.org that two people - MastaTabs and Ratte -- made available OpenPCI driver for the Radeon gfx cards.

I was a bit surprised that they made a driver for exactly the same ATI chipsets, which are just supported by Elbox Radeon driver. There are so many other gfx cards around...

I looked into the openpci driver code to check the name of its author but found that there isn't any copyright info inside. Nobody signed this driver. It seemed to me a little suspicious because developers who spend many weeks or months on such a project usually sign their code.

I sent the archive with this driver to Pawel Stypula - author of the Elbox driver for the Radeon gfx cards. He is a very busy man but promised to make a look into it as soon as has a moment of a spare time.

I just received his response. He is totally shocked. More than 90% of our Radeon related code was directly copied from our Radeon.card driver (ver. 2.12 from 09 Sep 2010) to the openpci Radeon.card driver. Almost all functions were taken from our driver and inserted by simple "copy and past" to this "new" driver. Many of the procedures were taken without changing even single line of the code. The only actual change that has been made in the code of functions taken from our driver was removing these parts of code, which are related to Mediators for A1200.

The blocks of the code taken from our driver without altering even one byte in them are so big as several hundreds of processor opcodes! There are over a dozen of such big directly copied blocks of code. The biggest one has 637 assembler lines (1898 bytes of the driver code)!

I'm really surprised that someone decided to make an almost 1:1 copy of our code, inserted it as an essential part of his driver and announced it as his work.

The development of our Radeon driver took months of work in 2007 and 2008. This was a first support for any ATI Radeon gfx cards in Classic Amigas. There were many undocumented Radeon issues which had to be solved in the code of this driver. Solving them required many time and hard work.

Nobody wants their work being stolen, we too. If somebody wants to use our code he should contact us for the license. Using our copyrighted code without our permission is illegal.

The driver released by MastaTabs and Ratte is clearly illegal as containing the stolen code.

Best regards,
Darek Smietana
ELBOX COMPUTER

Postscriptum:
It is just the removal of checks on which Mediator (A1200 or ZIII Amiga) and in what mode (MMU / NOMMU) driver is working what results in the slight increase in speed tests measured by P96speed.

Last edited by DJS on 19-Dec-2012 at 10:09 PM.

@Djs

I understand your point of view and the situation.

But : users want faster Amiga Classic, so a faster driver is good for the community and for keeping Classic alive...

Remember that your are the only supplier of your hardware, and Ratte's driver cannot work without it...

The solution against 3nd party drivers is to update your own drivers with the users's desires :
- faster drivers (here Radeon)
- romable drivers (FastATA...)

Last edited by CosmosUnivers on 23-Dec-2012 at 08:46 AM.

statement:
http://www.a1k.org/forum/showthread.php?p=585102

Last edited by Ratte on 24-Dec-2012 at 12:11 PM.