![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to README.PROGRAMMERS CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [UNIX Amiga Emulator] / uae / docs|
Return to README.PROGRAMMERS CVS log | Up to [UNIX Amiga Emulator] / uae / docs |
1.1 root 1: You can help to make this program better. If you fix bugs or implement new
2: features, I'd be grateful if you send me patches. For a list of interesting
3: projects, and for a brief summary on how UAE works, see below.
4:
5: A few guidelines for anyone who wants to help:
6: - Please contact me first before you implement major new features. Someone
7: else might be doing the same thing already. This has already happened :-(
8: Even if no one else is working on this feature, there might be alternative
9: and better/easier/more elegant ways to do it.
10: - If you have more than one Kickstart, try your code with each one.
11: - Patches are welcome in any form, but diff -u or diff -c output is preferred.
12: If I get whole source files, the first thing I do is to run diff on it. You
13: can save me some work here (and make my mailbox smaller).
14:
15: Some possible projects, in order of estimated difficulty:
1.1.1.2 root 16: - Add gamma correction
1.1.1.3 root 17: - If the serial port still isn't working (I've got no idea, I don't use it),
18: fix it.
1.1 root 19: - Someone with a 68020 data sheet might check whether all opcodes are
20: decoded correctly and whether all instructions really do what they are
21: supposed to do (I'm pretty sure it's OK by now, but you never know...).
1.1.1.3 root 22: - Add more 2.0 packets to filesys.c
1.1.1.2 root 23: - Multi-thread support is there now, it just needs someone to test it on a SMP
24: machine and to fix it so it improves speed instead of slowing the thing
25: down.
1.1 root 26: - Improve the Kickstart replacement to boot more demos.
27: - Snapshots as in CPE. Will need to collect all the variables containing
28: important information. Fairly easy, but boring. (Use core dumps instead :-)
1.1.1.2 root 29: _If_ someone attempts this, please be more clever than the various CPC
30: emulators and dump state only at one fixed point in the frame, preferrably
1.1.1.3 root 31: the vsync point. Also talk with Petter about this.
1.1 root 32: - Find out why uae.device has to be mounted manually with Kick 1.3.
33: The problem seems to be that we don't have a handler for it. I _think_ what
34: we need is the seglist of the standard filesystem handler. Problem is,
35: DOS hasn't been started when the devices are initialized and so we can't get
36: to the DosBase->RootNode->FileHandlerSeg pointer, and then there is the
37: confusing matter of BCPL GlobVecs and other weird stuff...
1.1.1.2 root 38: - Some incompatibilities might be fixed with user-modifiable fudge variables
39: the same way it's done in various C64 emulators.
40: - With the new display code, it would probably be easier than before to
41: implement ECS resolutions - however, a lot of places rely on the OCS timing
42: parameters and display sizes.
1.1 root 43: - Figure out a diskfile format that supports every possible non-standard
44: format.
45: - Implement 68551 MMU. I have docs now. Not among the most necessary things.
1.1.1.3 root 46: Should be done like exception 3 handling: add code to genamode in gencpu.c.
1.1 root 47: - Implement AGA support. Some bits and pieces exist.
48: - Reimplement Amiga OS. (Well-behaved) Amiga programs could then be made
49: to use the X Window System as a "public screen". Of course, not all the
1.1.1.3 root 50: OS would have to be re-done, only Intuition/GFX/Layers (which is enough).
51: [Started, look at gfxlib.c - not usable yet.]
1.1.1.2 root 52: - Find some extremely clever ways to optimize the smart update methods. Some
53: ideas:
54: a) Always use memcmpy() to check for bitplane differences. If no differences
55: are found, see if BPLxDELAY got modified, if so, scroll.
1.1.1.3 root 56: Problems:
1.1.1.2 root 57: * You'd still have to draw a few pixels around the DIW borders. Not very
58: hard.
59: * Scrolling with memcpy in video memory can be terribly slow (no, I
60: shouldn't have bought the cheaper video card with DRAMs)
61: * At least every 15 pixels a full update has to be done since the
62: bitplane pointers get updated after that. And that's with the slowest
63: scrolling - if the playfield scrolls faster, the benefit converges
64: against zero.
65: You could also do vertical scrolling tests, but similar problems arise -
66: where should one check? One line above/below? What about faster
67: scrolling? You could use the bitplane pointers as hints, but with
68: double/triple buffering this gets problematic, too.
69: On the whole, I don't think it would be worth the effort, even if it
70: works very well for a few games.
71: b) Well, there is no b). If I thought of something I forgot it while
72: writing a).
1.1 root 73: - Port it to Java and Emacs Lisp
74: - A formal proof of correctness would be nice.
75:
76:
1.1.1.3 root 77: Source file layout
78:
79: src/ contains (mostly) machine-independent C code.
80: include/ contains header files included by C code.
81: md-*/ CPU and compiler dependent files, linked to machdep by configure
82: od-*/ operating system dependent files, linked to osdep by configure
83: td-*/ thread library dependent files, linked to threaddep by configure
84: sd-*/ Sound code. sd-* is only for sound systems which are not OS specific
85: or for which no "od-*" directory exists. Linked to sounddep
86: targets/ Contains header files which contain some information about which
87: options a specific port of UAE understands.
88:
89:
90: Coding style
91:
92: As long as your code is hidden in a file buried in md-*/ or od-*/ where I
93: never have a look at it, you can probably get away with not following these
94: guidelines.
95:
96: * Do not include CR characters.
97: * Do not use GNU C extensions if you can't hide them in a macro or in a
98: system-specific file so that an alternative implementation is available
99: when GNU C is not used.
100: This applies to _all_ OS/CPU/compiler specific details. Basically, nothing
101: of that sort should appear in src/*.c (we're a bit away from that goal at
102: the moment, but it's getting better).
103: * Make sure your code does not make assumption about type sizes other than
104: the minimum widths allowed by C. If you need specific type sizes, use the
105: uae_u32 type and its friends.
106: * Set up your editor so that tab characters round up to the next position
107: where ((cursorx-1) % 8) == 0, i.e. 8 space tabs. Do not use 4 space tabs,
108: that makes the code awful to read on other machines and worse to edit.
1.1.1.5 ! root 109: (I'm talking about the tab character here, not indentation!)
1.1.1.3 root 110: * Lines can be up to 132 characters wide. Use SVGATextMode for the Linux
111: console, or use a windowing system in a high resolution.
112: * C++ comments are a no-no in C code.
113: * Indentation - look at some code in custom.c and try to follow it. Don't
114: use GNU 2-space-in-weird-places indentation, I find it awful. But _do_
115: follow the GNU rules for adding whitespace in expressions, and those for
116: breaking up multiple-line if statements.
117: Fixed indentation rules almost never make sense - break the rules if that
118: makes your code more readable.
119: Hint: Get jed from space.mit.edu, /pub/davis. It can indent your code
120: automatically. Put the following into your .jedrc, and it will come out
121: right:
122: C_INDENT = 4;
123: C_BRACE = 0;
124: C_BRA_NEWLINE = 0;
125: C_Colon_Offset = 1;
126: C_CONTINUED_OFFSET = 4;
127:
128:
1.1 root 129: How it works
130:
131: Let's start with the memory emulation. All addressable memory is split into
132: banks of 64K each. Each bank can define custom routines accessing bytes,
133: words, and longwords. All banks that really represent physical memory just
134: define these routines to write/read the specified amount of data to a chunk
1.1.1.3 root 135: of memory. This memory area is organized as an array of uae_u8, which means
1.1 root 136: that those parts of the emulator that want to access memory in a linear
1.1.1.3 root 137: fashion can get a (uae_u8 *) pointer and use it to circumvent the overhead of
1.1.1.2 root 138: the put_*() and get_*() calls. That is done, for example, in the
1.1 root 139: pfield_doline() function which handles screen refreshes.
140: Memory banks that represent hardware registers (such as the custom chip bank
141: at 0xDF0000) can trap reads/writes and take any necessary actions.
142:
143: To provide a good emulation of graphical effects, only one thing is vital:
144: Copper and playfield emulation have to be kept absolutely synchronous. If the
145: copper writes to (say) a color register in a specific cycle, the playfield
1.1.1.2 root 146: hardware needs to use the new information in the next word of data it
1.1 root 147: processes.
148: UAE 0.1 used to call routines like do_pfield() and do_copper() each time the
149: CPU emulator had finished an instruction. That was one of the reasons why it
150: was so slow. Recent versions try to draw complete scanlines in one piece. This
151: is possible if the copper does not write to any registers affecting the
152: display during that scanline. Therefore, drawing the line is deferred until
1.1.1.2 root 153: the last cycle of the line. However, sometimes a register which affects how
154: the screen will look is modified before the end of the line (think of copper
155: plasmas). That's what "struct decision thisline_decision" is for. It is
156: initialized at the start of each line. During the line, whenever a vital
157: register is changed, one of the decide_*() functions is called and may modify
158: thisline_decision. There are several independent decisions:
159: - which DIW should be used
160: - where does data fetch start/stop (or is the line in the border altogether)
161: - where should sprites be drawn (note: the same sprite can appear more than
162: once on one scanline, see Turrican I world 3 levels 1 and 3 for the best
163: example)
164: - what are the playfield pointers at the start of DDF. Related, what data do
165: they point to.
166: - what are the playfield modulos at the end of DDF
167: - coppermagic with the colors is remembered for later use
168: - so is copper magic with the bitplane delay values. I used to think there
169: was no useful application for modifying BPLCON1 while data is being
170: displayed, but Sanity demos can make Amiga emulator programmers look real
171: old.
172:
173: All of this is remembered while the raster line is processed by the hardware.
174: After the line (at hsync), all the decisions are made if they weren't made
175: before. At that point the line can be drawn by playfield_draw_line.
176: Additionally, all the decisions from the previous displayed frame are saved
177: and compared with the new ones, since often lines are not modified between
178: frames. This saves a lot of redrawing work.
1.1 root 179:
180: The CPU emulator no longer has to call all sorts of functions after each
181: instruction. Instead, it keeps a list of events that are scheduled (timer
182: interrupts, hsync and vsync events) and their "arrival time". Only the time
183: for the next event is checked after each CPU instruction. If it's higher than
184: the current cycle counter, the CPU can continue to execute.
185:
1.1.1.2 root 186: Things that can't be supported with the current "decision" model:
187: - Changes in lores/hires mode during one line. Dunno whether that was ever
188: used in reality.
189: - Changes to the bitplane DMA bit during one line. Hardly useful and not
1.1.1.3 root 190: likely to be used. [but there are at least two programs which do ugly
1.1.1.2 root 191: things like that, and there are some hacks in UAE that make those programs
192: work (Magic 12 Ray of Hope 2 is one of these demos)]
193: - Changes in bitplane data during one line. If programs do this kind of
194: thing, it's most likely accidental and the program is broken. Can happen
195: with programs that use the blitter incorrectly, like all the Andromeda
196: demos.
197: - others? (fill in if you can think of anything)
198:
199: All in all, it's unlikely that this causes compatibility problems. If it does,
200: fudge values could be introduced (although that sort of thing gets messy
201: quickly).
1.1 root 202:
203:
1.1.1.3 root 204: * Native code vs. 68k code
1.1.1.2 root 205:
1.1.1.3 root 206: It is possible to call native code from 68k code; autoconf.c has some routines
207: which make setting up a call trap very easy. However, it is not as easy to
208: call 68k code from native C code, at least not while Amiga Exec multitasking
209: is running. You ask why?
210:
211: Amiga process1 calls native function foo
212: Native function foo calls some 68k function and goes into 68k mode
213: Amiga context switch happens, process1 is put to sleep and process2 gets run.
214: Amiga process2 calls native function foo
215: Native function foo calls some 68k function and goes into 68k mode
216: Amiga context switch happens, process2 is put to sleep and process1 gets run.
217: Process 1 completes the 68k function called by foo and returns from 68k mode.
218:
219: There. Now we are in function foo again. When it called the 68k code, process2
220: was active. Now process1 is active, and the function we called in process2
221: hasn't completed yet. What a mess.
222:
223: To get around this, you need to do some stack magic. Code to do this exists,
224: but it must be adapted for each port, since setting up a different stack is
225: completely non-portable.
226:
227:
228: * How multithreading in filesys.c works
229:
230: AmigaOS is nice enough to start one processes for each mounted filesystem. All
231: of these run in the 68k emulation code, i.e. in the main UAE thread. This is
232: the reason why multithreading is desirable: if the main UAE thread blocks
233: waiting for I/O, the CPU emulation can't continue to run. Since the Amiga OS
234: is capable of multi-tasking, it is possible that other code could run until
235: the I/O operation is complete. The most important bit of code that can run is
236: the code that moves the mouse pointer - it's unpleasant if the pointer does
237: not follow mouse movement during disk/CD accesses.
238:
239: When a packet is received by the filesys.asm code, filesys_handler is called.
240: This function always runs in the main UAE thread.
241: - In the single-threaded case, this function performs the action that was
242: requested, then returns 0 to indicate "action completed, reply packet".
243: Nothing else is performed.
244: - In the multi-threaded case, filesys_handler figures out which unit the
245: packet was for and sends the packet to the UAE thread responsible for
246: handling this unit. filesys_handler returns 0 to indicate: queue the
247: packet. Also, one (at that point unused) field in the packet is set to
248: 0 to indicate that the action was not completed.
249:
250: The latter case is the interesting one. The thread that got the packet does
251: the following:
252: - perform the action as usual
253: - set the "command complete" field in the packet to -1.
254: - send a message to the AmigaOS (!) filesystem process. However, it can't do
255: that without some effort. We can't call 68k code from the emulator easily.
256: So we have to use an Amiga interrupt. The filesystem init code sets up an
257: Exec IntServer for the EXTER interrupt, and hsync_handler() checks
258: periodically whether the filesystem needs an interrupt and raises one if
259: necessary.
260: Only one dummy message is used per filesystem unit, which is allocated at
261: startup. This means that there must be some locking to prevent the unit
262: thread from sending the same message twice to the same port. To determine
263: whether the message is free, three counts are kept. "cmds_sent" is
264: incremented by the UAE thread whenever it has completed a command.
265: "cmds_acked" is set to the same value of cmds_sent at the point that the
266: interrupt handler got invoked and decided it must send a message. Finally,
267: cmds_complete is set to this value at the time the AmigaOS process receives
268: the dummy message. Whenever cmds_acked == cmds_complete, the dummy message
269: is free to be sent again.
270:
271: The EXTER interrupt basically walks through the units, looks at the cmds_*
272: fields and sends the dummy message to the Amiga filesystem process when
273: possible and necessary.
274:
275: When the Amiga filesystem process receives such a dummy message, it does the
276: following:
277: - increment cmds_complete as described above.
278: - walk through the queue of unprocessed commands and see which ones now have
279: a status of -1, indicating that they are finished. These are removed from
280: the queue and replied to.
281:
282:
283: * Calltraps at fixed locations
284:
285: F0FF00: return from 68k mode.
286: F0FF10: must have gotten lost somewhere ;)
287: F0FF20: used by filesys.c to store away some information from the startup
288: packet.
289: F0FF30: filesys_handler().
290: F0FF40: startup_handler(), handles only the startup packet for each
291: filesystem.
292: F0FF50: used by the EXTER interrupt which we set up for the filesystem.
293: F0FF60: used by the uaectrl/uae-control programs (see uaelib.c)
294: F0FF70: used by the task that gets set up for the mouse emulation.
1.1.1.2 root 295:
1.1.1.5 ! root 296:
1.1.1.3 root 297: * How the compiler works
1.1.1.2 root 298:
299: .. yet to be written. To be decided, in fact.
1.1.1.3 root 300:
301:
302: Portability
303:
304: This section was out of date. I'll rewrite it.
305: Some day.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.