Welcome, Guest. Please login or register.

Author Topic: Why is AGA so hard to implement?  (Read 5467 times)

Description:

0 Members and 2 Guests are viewing this topic.

Offline kolla

Re: Why is AGA so hard to implement?
« on: March 24, 2018, 11:15:32 PM »
Quote from: Chucky;837781

but I do not understand those who wants to ADD stuff to AGA.. why.  there is simply no reason whatsoever to do that.


It's possible to add things to AGA without breaking how software access and see AGA - faster chip RAM access, de-interlacing, new modes (like HighGfx is already doing), better HAM implementations etc. Ideally I want an improved AGA for doing animations using old tools like DPaint, Briallance etc. Old AGA _can_ do 1280x720 HAM8 animations, but it is borderline within chip ram limits and annoyingly sluggish. More and faster ChipRAM can help with this (as demonstrated using UAE and for that matter, FPGA Arcade).
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS