Ian Collier wrote:
For the moment, assume that the screen is turned off or it happens to
be displaying the border. At this time, all accesses to main RAM are
restricted by the ASIC to occur only on every fourth cycle. (This does
not apply to external RAM or to ROM).
Ah, didn't suspect RAM
On Tue, Apr 13, 1999 at 08:39:11AM +0100, Si Owen wrote:
Can you recommend a reference for this sort of instruction detail?
Not really - it's mostly guesswork, although I did measure a lot of
instructions experimentally. I think Pedro Gimeno did something similar
for the Spectrum and the
Ian Collier wrote:
Not really - it's mostly guesswork, although I did measure a lot of
instructions experimentally. I think Pedro Gimeno did something similar
for the Spectrum and the results are in the cssfaq
I found Pedro's work at lunch-time and it looks like a good starting point.
At the
On Sat, Apr 10, 1999 at 01:53:01AM +0100, Andrew Collier wrote:
Well maybe this is slightly different? But these symptoms came up on
the very latest linux version (or at least, that's what Ian _said_ he'd got
installed) :)
I said nothing of the sort. I have version 0.72 which is rather
From: Andrew Collier [EMAIL PROTECTED]
It seems my code was reading the status register, and jumping for LINEint
correctly, but performing the wrong test for FRAMEints and jumping to the
FRAMEint handler iff the corresponding status register bit was high.
My guess is that on a real Sam, this
On Fri, Apr 09, 1999 at 11:20:01AM +0100, Andrew Collier wrote:
Û¤¸2Ĥ2 Ĥ2UÄÊ
ÌsÄC
Correct me if I'm wrong but this doesn't look anything like the code you
were supposed to be attaching, and it just says not understood when
executed. And your mailer transmitted it as text in
From: Andrew Collier [EMAIL PROTECTED]
It seems my code was reading the status register, and jumping for LINEint
correctly, but performing the wrong test for FRAMEints and jumping to the
FRAMEint handler iff the corresponding status register bit was high.
My guess is that on a real Sam, this
