Would you support a new Unified Opensource RTG standart?

[Golem!dk]

@golem: once again, what ahi drivers you immediately require that are missing?

The ones I mentioned obviously.

and i think we seriously have to stop thinking of amiga software on profit basis. it is a hobby, so it is either open source or nothing. the consumer base is too small to generate income. not so hardware wise since it cant be done in the kitchen. i dont know exactly if this is sad , but it is the truth.

Good thing we have AROS.

[arnljot]

Included drivers
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
concierto.audio   4.28 (1.11.98)    © 1997-1998 Village Tronic Computer
delfina.audio     4.07 (11.10.98)   © 1997 Petsoff Limited Partnership
maestropro.audio  2.3 (28.10.97)    © 1997 Richard Koerber
melody.audio      4.10 (31.07.98)   © 1998 Thorsten Hansen
melody1200.audio  4.10 (06.09.98)   © 1998 Kato Development (Thorsten Hansen)
paula.audio       4.30 (29.04.03    Public Domain
paula.audio (MOS) 4.30 (30.03.03)   © 2002-2003 Sigbjørn "CISC" Skjæret and
                                    Harry "Piru" Sintonen
prelude.audio     2.30 (06.02.99)   © 1996 A.C.T.
toccata.audio     4.7 (19.06.2005)  Public Domain
wavetools.audio   2.11 (15.02.97)   Public Domain

Those are the drivers from the main m68k ahi archive.

http://bvernoux.free.fr/DevPCI.php The open PCI site doesn't quote who wrote the AHI drivers for OpenPCI library audio cards.

The GREX drivers are " ©2000-2001 by DCE Computer Service GmbH ".

And then there are the Elbox AHI drivers, and number of AHI drivers around for MOS, AROS, AOS4 and number of drivers on aminet. All made possible because Martin Bloom recognized that for his Audio system to be a success, it had to be open.

Your comment on AROS, I completely agree on. And I like it so much, because it's open!

But, to get back on track.

It seems that we need to make a new system from scratch.

The question is then, what is the best starting point. Is it to look what code that can be taken from the AROS repository?

[Gulliver]

I believe the next step should be to outline goals (in persue of a bounty).

I am thinking on a bounty. I already emailed power2people (AROS bounty system), and they said they are willing to help with their website and bounty management system on AmigaOS bounties.

What do you think?

[Tension]

If by "support" you mean "use if it is better" then Yes.

edit: 1000th post - woohoo!!

[trekiej]

How does AROS and RTG relate?
Enquiring minds want to now.

[Golem!dk]

Those are the drivers from the main m68k ahi archive.

Yes, I see most of those predate AHI being released under the (L)GPL, which was kinda the point I was trying to make

[bloodline]

How does AROS and RTG relate?
Enquiring minds want to now.

Search for Bernd AFA

[wawrzon]

@bloodline: ok, ill notify him of the thread.;P
but he will not do the job.

who would probably be the right person is alain, but his projects, wazp and mesa, are keeping him busy enough already. i also have had a talk on subject like that with both already some time ago, and they regarded i too big a task to handle. (i believe i was thinking of w3d driver for radeons)

[kolla]

Yes, I see most of those predate AHI being released under the (L)GPL, which was kinda the point I was trying to make

What does (L)GPL have to do with any of this?
Besides, no - it was not the point you were trying to make, I know you too well - your point was that some of those drivers would have been written anyways, because those who wrote them would happily have used a pirated SDK  

[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

[wawrzon]

but gallium is not a replacement for an rtg system? i expect perhaps it could be used to replace or improve warp3d but not the rtg itself. besides from what i remember gallium doesnt support r200 only >r300 so radeon9xxx series is out of the question and that are exactly the pci graphic cards is that have decent driver support on all amiga(oid) brands. i recall there were lately some 5 v tolerant radeon pci cards. perhaps effort should concentrate on writing openpci driver for such a card to get gallium based mesa or warp3d based support later. although im not sure if this isnt pile of bs what i write.

[arnljot]

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?

As I've understood it gallium will be injected between AROS CGX and the hardware. Then there is talk about putting Cairo on top of that, and make a cgx library on top of that for backwards compatability.

This is how I've understood it.

[Karlos]

Which existing graphics cards for the Amiga have chipsets that support the VESA standards (and which version thereof)?

[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.

[wawrzon]

Which existing graphics cards for the Amiga have chipsets that support the VESA standards (and which version thereof)?

obviously at least those pci:
voodoo3 - vesa 2/3 (would impy also voodoo 4/5)
radeon9xxx

http://www.geos-infobase.de/HWARE03.HTM#

@bernd: ok, then i misunderstood something about gallium, it then does rely only on a (gallium) hardware driver. in this case i suppose 2d graphics could be wrapped to be implemented by 3d means as you suggest.. maybe not all that heavy.

[wawrzon]

@karlos:
but if we are going for vesa pci cards anyway, do we really need one already supported by amigaos drivers if gallium interfaces directly to the hw via vesa if i understood you right?

edit: would amithlon vesa2 drivers be of any help? i dont know how it is done on amithlon, nor on linux for that matter, does the kernel contains them or what?