|
From: Dom M. <do...@ja...> - 2007-07-21 19:15:52
|
On Sat, 21 Jul 2007, alvin albrecht wrote: > I think we need to do the interposer thing and write our own (brief) > interrupt routine that should be part of the crt0 maybe that ensures the > BC' and F' registers are all ok. On startup the crt0 records the > firmware's BC' and F' and then the interrupt stub restores that > environment and jumps into the regular firmware interrupt routine and > records new values of BC' and F' on exit. We should also make this stub > visible so that it can be used as part of a custom im2 routine if > desired. Without doing all this the cpc port is a little bit crippled. > > Do you want to do this dom? Or maybe set up the interposer thing since > I think you may be more familiar with where the firmware calls might be > in stdio and cpcfs (are there any more? graphics lib for plotting > points??) and I can set up the interrupt junk? I'm happy doing the interposer, there's quite a few places where it's used: fcntl/cpc, cpcmath, graphics/cpc, stdio/cpc, stdio/ansi/cpc so it may take a while to fix them all. It looks like ix is unused by the firmware routines so I'll use that to hold the machine address. Could you do the interrupt routine so that it can be used with the im2 library. d. |