68k & 060 friendly code...

[korruptor]

Hiya,

I've just got an 060 into my 1200, so I've hit the point where my dodgy old 500 code doesn't display properly. I'm pretty sure this is because of my interrupt setup being wrong for the higher processor.

Am I right in thinking that I need to get the VBR if I'm on a higher processor?

If so, how do I detect the CPU in asm to make the decision?

I'd like to dev on the 1200 (so run it and test it) but actually target the A500 for the stuff I'm making.

Thanks!

[pmc]

Hey korruptor

Yeah, you need to get the VBR.

This code will do it, just bsr to it in your startup before you need to set up your interrupt:

execbase	equ	$4
supervisor	equ	-30
attnflags	equ	296


.get_vbr:	move.l	execbase.w,a6
	btst	#0,attnflags+1(a6)
	bne.s	.need_vbr
	lea	sys_vbr_addr(pc),a0
	move.l	#0,(a0)
	rts

.need_vbr	lea	.get_vbr_code(pc),a5
	jsr	supervisor(a6)
	lea	sys_vbr_addr(pc),a0
	move.l	d0,(a0)
	rts

.get_vbr_code:	movec	vbr,d0
	rte

sys_vbr_addr:	dc.l	0

Don't thank me for the above, thank StingRay.

[korruptor]

Oh, cracking, I'd just come back to post that I'd discovered the AttnFlags after much googling!

Thanks PMC (and Stingray!)

[korruptor]

My next question; can anyone remember the key you hold down to turn the Blizzard expansion cards off during boot?

I know there's one for the 030 and I vaguely remember it being a function key but I can't make that trick work with the 060...

So far my code is spectacularly crashing, which is better than the grey screen I had before.

Edit: Fixed the crash. Yay!

[adolescent]

Originally Posted by korruptor

My next question; can anyone remember the key you hold down to turn the Blizzard expansion cards off during boot?

Hold down the "2" button (not the one of the number pad) during boot.

[korruptor]

Ah. Brilliant, thank you!