That cool for AROS to have up2date MESA + hardware 3D drivers. Hope aos4 will have that someday too.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

I hope that too!

_________________
Simone"Tuxedo"Monsignori, Perugia, ITALY.

@kas1e

The source codes are available in the AROS repository and I believe the majority of the work is done (AROS Mesa3D also works on PPC version (SAM port). What is needed is a person with AmigaOS4 driver development knowledge and of course some free time.

_________________
https://www.axrt.org

@deadwood
As i know, only Hans want to do that for AOS4, but for first he want to finish HD-Radeon drivers, then after he will works (maybe, and i hope that he will) on Galium/Mesa.

It's just better to do that for one person (low-level system drivers for gfx card + galium/mesa layers), because in this case (if all will do one person) possible to get maximum speedup (not like we have now with case with old p96drivers + buggy w3d drivers + minigl over it).

That opengl implementation (minigl) which we have on aos4 for now, more or less ok (thanks again to Hanz), but far from perfect because no shaders, no manu extensions, etc.

If someday mesa+galium will be avail on aos4, then (imho), will be pretty easy to create also a new minigl.library which will just resend everything to mesa.library -> that will allow all old games/demos which we have now works over new system, and not over current minigl-warp3d implementation.

Last edited by kas1e on 11-Apr-2010 at 04:33 PM.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

Thank you deadwood for your hard work on the Aros port.

PS.
I hope the other Amiga flavours will find someone to port this soon too. The more the merrier.

_________________
AmigaOS or MorphOS on x86 would sell orders of magnitude more than the current,
hardware-intensive solutions. And they'd go faster.-- D.Haynie

Good that Aros is able to help AmigaOS. This is an Amiga family and nice we can help each other.

Well done Deadwood and I love the Aros Mplayer update with fullscreen too.

_________________
Amiga 1000, 3000D Toaster, Checkmate A1500 Plus
http://www.checkmate1500plus.com/

Great work Aros devs :)

Great work!!

_________________
AmigaOS on Google+
AmigaOS on Facebook

@kas1e

Quote:

@deadwood As i know, only Hans want to do that for AOS4, but for first he want to finish HD-Radeon drivers, then after he will works (maybe, and i hope that he will) on Galium/Mesa.

That's correct. However, it would speed things up a lot if the latest version of MESA were ported over with the Gallium 3D software fallback driver by someone else other than me. The only part that can only be done by me is the Gallium 3D hardware driver for Radeon HD cards.

Hans

_________________
http://hdrlab.org.nz/ - Amiga OS 4 projects, programming articles and more. Home of the RadeonHD driver for Amiga OS 4.x project.
https://keasigmadelta.com/ - More of my work.

awesome news ..looking forward to the Samflex port hopefully soon

_________________
____________________________
c64-2sids, A1000, A1200T-060@50(finally working!),A4000-CSMKIII
! My Master Miggies- Amiga 1000 & AmigaOne X1000 !
mancave-ramblings
X1000 I BELIEVE

Quote:

he source codes are available in the AROS repository and I believe the majority of the work is done (AROS Mesa3D also works on PPC version (SAM port). What is needed is a person with AmigaOS4 driver development knowledge and of course some free time.

Yeah!

As in our previous conversation, we greatly appreciate your work and your collaboration, as well as the work done by Michal and Hans De Ruiter

Last edited by AmigaBlitter on 12-Apr-2010 at 08:57 AM.

_________________
retired

Good work!

@Hans

The software fallback Gallium3D driver should really be a simple(*) recompilation of what is available in AROS (however the performance would be still less then poor)

(*) The only non trivial thing would be how to make the GL rendering context which is global by design to act as per client context. On AROS it is stored in a CPU register - I don't know how this would be handled on AOS4 (TLS?)

_________________
https://www.axrt.org

Deadwood: we love you :D

thx

@deadwood
But imho Gallium itself (not drivers) works with aros hidds ? I mean galium3d drivers, in end, use OS routines + OS 2d drivers -> in case with aos4 we have p96 drivers, with case with AROS - hidd.

btw, on aros, galium itself it's a galium.library which loads with other libraryes, or how its done ?

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

Well, I would probably say that there is no such thing as 'Gallium itself' (a bit of abuse from my side). There are Gallium drivers and they interact with system. For example the software rasterization driver displays its results using WritePixelArray function, while nVidia driver does direct blits to frame buffer from render buffer.

Currently the setup is like this:
mesa.library
gallium.hidd
softpipe.hidd
nouvea.hidd

but there is still a build target that builds mesa.library containing the gallium stuff and softpipe renderer - that is how initially the gallium was released to users. Not it simply is splitted out into module following AROS design.

_________________
https://www.axrt.org

@deadwood
So, looks like Galium it's just the "inside" code which do opengl(mesa) calls translate to low-level os drivers (so, in general it kind of warp3d/directx, looks like, right ?)

@hans
How you think it must be looks like on aos4 ? like:

mesa.library - have mesa + galium + galium drives inside
redeonHD p96 driver.

right ?

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

My preferred structure would be:

mesa.library - gallium.library - R500/R600/R700 Gallium driver - RadeonHD driver backend.

Putting the Gallium3D driver inside the Picasso96 one would be rather inflexible.

@deadwood

I have some questions that I'd like to ask you, but I'll contact you via email, when I have time to think about this a bit more.

Hans

_________________
http://hdrlab.org.nz/ - Amiga OS 4 projects, programming articles and more. Home of the RadeonHD driver for Amiga OS 4.x project.
https://keasigmadelta.com/ - More of my work.

@Hans
Yep, by logic, and user-coder-future wise, better have everything logical, like mesa.library, gallium.library, then galium drivers (which will works with radeon drivers).

But from other side, 2 libs + 2 drivers (kind of), not will be a problem for speed ? Like need to open one library, then another, then another , etc ? (just curius about the best solution related to speed, and for future for other ppls who will in interest to make Galium drivers for other cards (for example i am in interes (in future) make a driver for radeon9250) ).

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@Hans

The current r300g Gallium3D driver supports R300-R500 only. R600 and up driver is not yet beeing developed (I think):

http://wiki.x.org/wiki/RadeonFeature

Also I think it can be rather tricki/time consuming to have the Gallium driver use existing RadeonHD backend - please contact me via mail for more details.

_________________
https://www.axrt.org