![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to todo.txt CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [HATARI the Atari ST Emulator] / hatari / doc|
Return to todo.txt CVS log | Up to [HATARI the Atari ST Emulator] / hatari / doc |
1.1 root 1:
1.1.1.4 root 2: Hatari TO-DO list
3: =================
1.1 root 4:
1.1.1.4 root 5: If you think that you can help with one of the TO-DO list items, please get
6: in touch with us.
1.1 root 7:
1.1.1.6 root 8:
1.1.1.4 root 9: Emulation improvements
10: ----------------------
1.1 root 11:
1.1.1.11 root 12: - Investigate what TOS version/functionality doesn't work for programs
13: started from the DESKTOP/NEWDESK.INF and why, e.g:
14: - Printing doesn't work with TOS versions v1.02 - v2.06
1.1.1.12 root 15: - Colors in 2-plane VDI resolution are not set correctly
1.1.1.11 root 16: - Tony Benett: Virtual City demo bombs
17: - NoCrew: Aggressive Party 2 4k demo doesn't work
18: - Running 1997 shareware version doesn't work
19: Document that in manual (page) for the Hatari "autorun" feature.
20:
21: - Keyboard detection sometimes fails when --fast-forward is enabled
22: while TOS boots / game is loaded (e.g. Falcon Snake game packed
23: with Sentry).
24:
1.1.1.3 root 25: - Improve disk image formats support:
1.1.1.6 root 26: - Add support for .STT images
27: (created with the STEEM disk image program)
28: - Support .DIM images created with the "Get sectors: used" option
1.1 root 29:
1.1.1.8 root 30: - Real HD 6301 (keyboard processor of the ST) emulation.
1.1.1.4 root 31: (Current special casing is enough for all known demos using 6301)
1.1 root 32:
1.1.1.8 root 33: - Finish upgrading the CPU core of Hatari to the latest WinUAE
34: which has better cycle accuracy needed by some programs:
1.1.1.12 root 35: - Finish MMU emulation support
1.1.1.8 root 36: - Add Exception debugging support
37: - Instead of calling Reset_Cold()/m68k_reset()/uae_reset()
38: directly from newcpu.c, show user a notice (dialog)
39: about what happened and let user do the reboot
1.1.1.11 root 40: (see "Emulation reset, old-UAE vs. WinUAE core" mail-thread)
1.1.1.12 root 41: - Make WinUAE core ST/STE emulation as good as with old UAE core
1.1.1.8 root 42: - Update WinUAE core to its latest (a year newer) version
1.1.1.12 root 43: - Document cmdline options for selecting prefetch etc
44: once they're stable
1.1 root 45:
46: - Get the games/demos working that are marked as non-working in the manual.
47:
1.1.1.11 root 48: - Improve TT and/or Falcon emulation, especially VIDEL, e.g:
49: - Palette switching during screen drawing
50: - ST screen modes centering when Videl borders are enabled
1.1.1.12 root 51: - Videl video register access (e.g. VIDEL_ScreenCounter_ReadByte()
52: never changes the register value unless it had first specifically
53: been written into):
54: http://listengine.tuxfamily.org/lists.tuxfamily.org/hatari-devel/2013/02/msg00155.html
1.1.1.4 root 55:
1.1.1.8 root 56: - TT/FastRAM support as some demos need >14MB
57:
1.1.1.5 root 58: - Add SCSI hard disk emulation for Falcon/TT mode.
1.1.1.4 root 59:
1.1.1.12 root 60: - ACSI emulation doesn't work with TOS v3 (but works for TT/EmuTOS).
1.1.1.6 root 61:
1.1.1.4 root 62: - Add SCC serial port emulation for Falcon/TT mode.
63:
1.1.1.10 root 64: - Disable VDI mode for TOS v4 as it doesn't support it (and VDI mode
65: is redundant as Falcon's Videl allows similar resolutions)
1.1.1.6 root 66:
1.1.1.11 root 67: - Fix falcon sound quality (sound is sometimes noisy).
1.1.1.8 root 68: Sound is also toggling between nice to noise with some demos.
1.1.1.6 root 69:
1.1.1.8 root 70: - DSP emulation / Falcon sound matrix:
1.1.1.7 root 71: - Dsp SSI internal clock (is it used on falcon ?)
1.1.1.8 root 72: - Verify DSP instructions cycle count, especially with external RAM
1.1.1.6 root 73:
1.1.1.12 root 74: - FPU 80-bit precision mode (selected with FPUCW instruction, and
75: extra instructions on 040), if there are programs depending on it.
76: UAE core implements only support for 64-bit precision. See "m68k
77: FPU precision issue" thread on debian-68k mailing list for details.
78:
1.1.1.9 root 79: - The "memvalid" system variables currently have to be patched in most cases.
80: For improved compatibility (e.g. the game "Yolanda") it would be better to
81: skip this step, but we then run into multiple other problems, see:
82: http://listengine.tuxfamily.org/lists.tuxfamily.org/hatari-devel/2011/12/msg00123.html
83:
84:
1.1.1.10 root 85: Programs known as not fully functional (not an exhaustive list)
86: ---------------------------------------------------------------
1.1.1.9 root 87:
88: Demos :
89: - video : Omega - Full Overscan Screen, Phalanx Demo - Dragon,
90: Dragonnels - Happy Island, Phaleon Demo - Future Minds,
91: Decade Demo - Reset, TNT - Death Of The Left Border,
92: Anomaly Demo - Menu, Delirious Demo IV - STE Detection,
93: Ventura - Ultimate Dist, Syntax Terror - TCB, ICE - Kryos,
94: ICE - Intruding, ICE - Jamcols, Extreme Rage, Paradox - XMas 2004,
95: ICE - Space Tale, ICE - The Wave Of The Future, Snork - DNT Screen 1
96:
97: Games :
1.1.1.12 root 98: - ikbd : Superior 109 - Special Forces
1.1.1.9 root 99:
1.1.1.6 root 100:
101: Other potential Hatari functionality improvements
102: -------------------------------------------------
103:
1.1.1.7 root 104: - Improved boot drive & partition handling code:
105: - count partitions the same way in ACSI, IDE & GEMDOS
106: - move BootDrive stuff from floppy.c e.g. to tos.c where NumDrives is
107:
108: - Support harddisk write protection also for IDE & ACSI drives?
109:
1.1.1.12 root 110: - Fix GST symbol table detection in debugger & gst2ascii. Currently
111: it will just process whatever it thinks the symbol table to
112: contain (which output can mess the console). MiNT binaries can
113: contain GST symbol tables, so checking that isn't enough.
114:
1.1.1.8 root 115: - Preliminary debugger work for the other features + cleanup:
116: - Eval_Number() could take DSP/CPU flag like Eval_Range()
117: does so that all commands taking numeric args can accept
118: also symbol, variable & register names
119: - Skip & tell user to rename any of the loaded symbols that
120: have same name as internal Hatari variables
1.1.1.9 root 121: - Change "" for expressions to {} so that quotes can
1.1.1.8 root 122: be used for e.g. search strings?
123:
1.1.1.11 root 124: - While Hatari debugger has many features that Steem one doesn't have,
125: that also has debugging features missing from the Hatari debugger.
126:
127: These ones should be straightforward to implement:
1.1.1.9 root 128: - Breakpoints on interrupts
1.1.1.8 root 129: - Breaking on exceptions 2-8 vs. bombs vs. don't break.
130: Hatari has only an option to break on address & bus errors
131: & uninitialized exception handler.
1.1.1.12 root 132: - Showing values both in different lengths and numeric bases.
1.1.1.8 root 133: (In Hatari one gets latter with "evaluate" command, e.g. "e a0",
1.1.1.12 root 134: and showing the value as long/word/byte requires ANDing it)
1.1.1.8 root 135: - All register values being shown with above info
136: (= Steem Register monitor)
137: - info commands for PSG, MFP, FDC and IKBD register values
138: (= Steem monitors for these)
1.1.1.11 root 139: - Info command for "timings" i.e. cycles since HBL/VBL,
1.1.1.8 root 140: timer values, video address & scanline
141: (= Steem Timings view)
142: - memory dump in text format
143: (= Steem Text monitor)
144: - Stack content display: m "a7-$40"-"a7"
145: (= Steem Stack display)
146: - Text string and binary values (hex) search
147: (= widgets in Steem monitor windows)
148: - Run for N cycles
1.1.1.11 root 149: (Hatari 'continue' command accepts only instructions, not cycles)
150:
1.1.1.8 root 151: These are more complicated ones:
152: - Monitoring reads & writes to specific address. Hatari supports
1.1.1.11 root 153: only tracing changes to values, not having breakpoints of
1.1.1.8 root 154: reading values or writing the same value. Slow
155: - Showing breakpoints in instruction dumps. Hatari breakpoints
156: are more advanced than the trivial address breakpoints, so
157: this would require adding efficient support for plain PC
158: based breakpoints
159: - Adding new symbol names for arbitrary addresses one at the time.
160: Hatari debugger currently requires new symbols to be added to
161: a file containing all the symbols + reloading that file
162: - Memory dump that shows also disassembly and values
163: in different bases
164: (= Steem Memory monitor)
1.1.1.11 root 165:
1.1.1.8 root 166: Basic GUI debugger features:
167: - Ability to open as many dump/info windows as wanted
1.1.1.11 root 168: (hex/asm/mfp/video/sound/...) and have their content
1.1.1.8 root 169: refreshed each time emulation is stopped.
170: - A stop/run button and a debugger "step" button
171: - Possibility to click to an address on dump window to define
172: a simple PC breakpoint (or monitor memory on B/W/L accesses)
173: - A way to search for hex/text in Hatari's RAM.
174:
175: (See "Steem debugger features not in Hatari debugger"
1.1.1.11 root 176: on BerliOS hatari-devel mail thread for more info.)
1.1.1.8 root 177:
178: - MonST debugger features missing from Hatari debugger
179: (ones not mentioned in Steem features):
180: - Address breakpoints can have conditions that are evaluated
181: only on that address
182: - Marking breakpoint types in disassembly (<count> for counted
183: ones, ? for conditional ones, * for others)
1.1.1.7 root 184: - Shortcut command for telling to run until given
185: (temporary) conditional breakpoint is hit
186: - Running until code returns from ROM (exiting from super mode?)
187: - Single stepping that skips Traps, Line-A, Line-F. And one that
1.1.1.8 root 188: skips also BSRs and JSRs. Run until RTS/RTE command
189: - Saving full machine status (like registers) to history buffer
190: each time debugger is entered (exception or breakpoint is hit)
191: and viewing of that history
1.1.1.7 root 192: - SP & SSP as CPU register names (active & supervisor stack)
193: - Fill and copy memory command
1.1.1.8 root 194: - Search for an address which disassembly output matches
195: given instruction substring
196: - User variables which values can be set & used in expressions
1.1.1.6 root 197:
198: - Improved screen handling:
199: - Direct 16-bit & 32-bit support for monochrome and VDI modes
200: (currently they're converted through 8-bit surface)
201: - Line based screen change detection/checks:
202: - blit only changed lines
203: - simpler / faster (LED) overlay handling
204: - x3 and x4 zooming routines for ST-Low resolution
205: - Include some fancy zooming routines like 2xSaI or Super-Eagle
206: - Add support for hardware accelerated zooming with
207: SDL YUV overlays or OpenGL
208:
1.1.1.7 root 209: - Check/clean RS232 code:
210: - polls at 2/20ms intervals and reads data byte at the time.
211: SDL_Delay()s & fgetc() could be replaced (at least on unix)
212: with select() and fread(). Or just remove the rs232 thread
213: and use an interrupt for it...
214: - The commented out rs232 stuff could be removed from gemdos.c
215: (RS emulation is done at HW, not Gemdos level).
216:
217: - Improve directory handling:
218: - Currently screenshots & anim go always to current dir,
219: whereas memsave, sound recording, printer & midi & serial &
220: output and log output go to file specified in config file.
221: There should be support for setting also anim/screenshot
222: directory / file name from config file (needs change also
223: in screenSnapShot.c).
224: - By default the directory config values should be empty in
225: which case the code will at run-time decide to use current
226: directory, but not modify the path config setting.
1.1.1.9 root 227:
228:
229: Bug reports
230: -----------
231:
1.1.1.13! root 232: - Hextracker freezes at start with Falcon emulation because Videl
! 233: screen address counter doesn't advance (its read & write are no-ops).
! 234:
1.1.1.11 root 235: - Atari programs can crash Hatari in Falcon mode because sound DMA code isn't robust
236: against bad register values:
237: http://listengine.tuxfamily.org/lists.tuxfamily.org/hatari-devel/2012/02/msg00082.html
238:
1.1.1.9 root 239: - When playing Tautology 2 I noticed the mod player sound goes in and out of
240: sync. fading into crackle and back. (Using Hatari 1.4 with TOS 4.04 on Mac
241: OS X 10.6.5)
242: http://developer.berlios.de/bugs/?func=detailbug&bug_id=17781&group_id=10436
243:
244: - Problem: On real Falcon there is a minor feature in videl. You can simply
245: fade whole screen to black, if you just clear the Horizontal Border End
246: ($ffff8286) and start fading colors from 0 to 255 to $ffff9800 or vice versa.
247: test <put picture to screen>
248: move.w #255-1,d7
249: moveq #0,d6
250: .loop <vsync, stop#$2300>
251: clr.w $ffff8286.w
252: move.l d6,$ffff9800.w
253: addq.l #1,d6
254: dbf d7,.loop
255: Now it does this exactly opposite direction, it fades bgcolor from 0 to 255.
256: http://developer.berlios.de/bugs/?func=detailbug&bug_id=18002&group_id=10436
257:
258: - To compare my real Falcon with Hatari on my Windows 7 PC, I make some short
259: benchmarks with Kronos. The disk benchmark in Kronos runs in 1-2 minutes on
1.1.1.10 root 260: my real Falcon. The same disk benchmark in Kronos under Hatari 1.5 runs
261: longer than 20 minutes with GEMDOS emulation. Only when I use the AltGr + X
262: option, before the benchmark runs, then the disk benchmark in kronos is
263: comparable fast as my 16MHz Falcon.
1.1.1.9 root 264: http://developer.berlios.de/bugs/?func=detailbug&bug_id=18298&group_id=10436
1.1.1.10 root 265:
266: -> Hatari GEMDOS emulation needs to do a lot of extra kernel file & directory
267: accesses which with current code seem unavoidable. They're a problem only
268: with test programs like Kronos, for those one should consider using
269: harddisk image files instead.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.