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