Would you support a new Unified Opensource RTG standart?

[unusedunused]

I have not look lots in AROS driver working, because i know, the Problem of writing drivers is the Hardware dependent Part.And there are lots drivers for classic here.writing this all as opensource again, is a years Job.

only thing thats not so hard and possible is use the P96 HW drivers due a wrapper.or best to get the P96 driver source.

the P96 driver api have some calls for blit,rectfill, openscreen, close screen, and hardware mousepointer show.there need a wrapper do that AROS code call this functions with correct Parameter.Because winuae driver is here, there can see what Parameters must send.

Or use gallium 3d on classic, but i dont know if that support ATI or Voodoo Gfx Cards

[unusedunused]

Isn't gallium a driver system? P96 and CGX is a two parter, one part is the driversystem, the other is replacing and patching OS screen and window routines?

>Isn't gallium a driver system? P96 and CGX is a two parter, one part is the driversystem, >the other is replacing and patching OS screen and window routines?

Yes its a driver system, the other part do then the AROS Code.
Even if it is a 3d system it can do 2d actions.For example to scroll a bitmap there need a rectangle polygon use and attach to the screen data as texture on the gfx card.now the rectangle is blit to another position, and the data is move.same can do with rectfill, that contain a solid color textur.

i think sooner or later the code from older Radeon driver is move to work in gallium too.But Gallium currently is very young and so the replacement of the older Linux driver API is not finished yet.

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

Gallium is also design to give best speed on virtual systems.

[unusedunused]

badly gallium exists only for more recent cards
so it is not a solution for older cards.....

Alain Thellier - Wazp3D author

I think it take so long that the Radeon drivers > 9200 for OS4/MOS  need so long time or other drivers(for mac) need so long times because its closed source.so they cant just copy and paste a driver and it must develop from 0 and the Users of course must pay this additional effort.

but as can see there are drivers for Linux here, so i dont see a big problem wy a copy and paste not work.

also for 68k there are good low level debuggers here(winuae debugger, hrtmon), so a function during interrupt or layerlock can single step and look how it work.

I think a 2d GFX driver source have always this functions as can see on the P96 driver API

open a display with a resolution and depth and return a bitmap address
close the display
alloc mem on gfx card
freemem on gfx card
set a Hardware pointer image on GFX Card
move the Hardware cursor
blit a rectangle
rectfill a rectangle.

Thats the most important things that need on hardware for 2D.

But because i miss lots of programs and features on all AOS, i better add this to 68k AOS, because its the easiest way to get features because of the good debuggers here that help to find every Problem, i dont have the time and fun to spend on low Level stuff.because with a new display driver i cant use more programs.
 
but i think a opensource Driver API is a big step to make driver that exist on Linux easy working on 68k too, so change a old Linux driver that it can work in Gallium is maybe not the biggest work, but there need somebody who want do that.

[unusedunused]

>to establish vesa as standard on amiga to prepare it to accomodate gallium? im losing the >grip on that. can someone outline an overall concept?

Vesa is only a function set to open/close  a screen on a specific resolution.I guess to use it you need a X86 CPU.
but to give usefull speed you need a bitblit command for the GFX Card, that can copy blocks on the GFX Card fast and also a rectfill command.

maybe to make live easy in a driver you can open the display in Vesa and then use the function from Linux that do blitblit and rectfill.

so this avoid handling with hardware registers to open screen

But i dont know if when a screen is open in Vesa mode the GFX Card work in linear mode and not work in 64 kb mode andif VESA work on non X86 CPU

when work in 64 k mode all is slow.

[unusedunused]

>A little dig around shows driver code for the following in x.org

If you want search, you need look for drivers for Big Endian Systems.maybe PPC or so.
i look on a link and it include X86 files.