Talk:Z80 Routines:Graphic:Fastcopy - Revision history

Galandros: Talk:Routines:Graphic:Fastcopy moved to Talk:Z80 Routines:Graphic:Fastcopy: unite z80 routines

2009-10-25T19:49:46Z

Talk:Routines:Graphic:Fastcopy moved to Talk:Z80 Routines:Graphic:Fastcopy: unite z80 routines

FloppusMaximus: /* Potential Nspire issues */ new section

2009-06-01T01:44:50Z

‎Potential Nspire issues: new section

Darkstone knight at 16:28, 6 November 2008

2008-11-06T16:28:53Z

Jim e at 23:55, 29 April 2005

2005-04-29T23:55:53Z

Aquanight at 20:29, 29 April 2005

2005-04-29T20:29:59Z

Jim e at 00:42, 29 April 2005

2005-04-29T00:42:56Z

JasonM at 23:30, 27 April 2005

2005-04-27T23:30:04Z

Jim e at 21:05, 27 April 2005

2005-04-27T21:05:17Z

Woozle at 20:40, 27 April 2005

2005-04-27T20:40:14Z

Jim e at 14:17, 27 April 2005

2005-04-27T14:17:40Z

← Older revision		Revision as of 01:44, 1 June 2009
Line 36:		Line 36:
	2x INC HL (what ionfastcopy uses) 12 clocks <br>		2x INC HL (what ionfastcopy uses) 12 clocks <br>
	[[User:Darkstone knight\|Darkstone knight]] 08:28, 6 November 2008 (PST)		[[User:Darkstone knight\|Darkstone knight]] 08:28, 6 November 2008 (PST)
		+
		+	== Potential Nspire issues ==
		+
		+	The "safe" routines described on this page have their own problem: since they use undocumented instructions, they may not work on the Nspire. (Can anyone confirm this?)
		+
		+	I would guess that, since the Nspire is emulating the T6A04 anyway, the delay isn't really needed at all. (Can anyone confirm ''this''?) If so, it should be sufficient to replace
		+	in f, (c)
		+	jp m, $-2
		+	with
		+	cp a
		+	in f, (c)
		+	jp m, $-2
		+	since the Nspire will presumably skip over the undocumented instruction; "cp a" clears the sign flag regardless of the value of a. At some points, of course, the "cp a" can be avoided, if you're sure that the sign flag is already reset.
		+
		+	At some points in the routines, it might also be possible to use a normal, documented instruction such as "in b,(c)" instead. Which leads us to the question of whether the Nspire emulates port 10 for input at all...
		+
		+	[[User:FloppusMaximus\|FloppusMaximus]] 01:44, 1 June 2009 (UTC)

← Older revision		Revision as of 16:28, 6 November 2008
Line 26:		Line 26:

	I foregot about the ld a,I thing. that could work. But still one problem, If the coder is depending the interrupt timing, then DI will mess that up. But again it's getting more complicated than it should.--[[User:Jim e\|Jim e]] 16:55, 29 Apr 2005 (PDT)		I foregot about the ld a,I thing. that could work. But still one problem, If the coder is depending the interrupt timing, then DI will mess that up. But again it's getting more complicated than it should.--[[User:Jim e\|Jim e]] 16:55, 29 Apr 2005 (PDT)
		+
		+	== faster ==
		+	ld (hl),0 takes 10 cycles, so we can do with one less inc hl (6 cycles) and thus
		+	load 11 into de instead of 10.
		+
		+	actualy, it is faster to load 12 into de instand of 10, and use NOP <br>
		+	NOP + Ld (HL),0 = 14 clocks <br>
		+	INC HL + LD (HL),0 = 16 clocks <br>
		+	2x INC HL (what ionfastcopy uses) 12 clocks <br>
		+	[[User:Darkstone knight\|Darkstone knight]] 08:28, 6 November 2008 (PST)

← Older revision		Revision as of 23:55, 29 April 2005
Line 24:		Line 24:

	Why not just disable interrupts during fastcopy and turn them back on when returning to the program? (Or go even more tricky using ld a, i or similar.) --[[User:Aquanight\|Aquanight]] 13:29, 29 Apr 2005 (PDT)		Why not just disable interrupts during fastcopy and turn them back on when returning to the program? (Or go even more tricky using ld a, i or similar.) --[[User:Aquanight\|Aquanight]] 13:29, 29 Apr 2005 (PDT)
		+
		+	I foregot about the ld a,I thing. that could work. But still one problem, If the coder is depending the interrupt timing, then DI will mess that up. But again it's getting more complicated than it should.--[[User:Jim e\|Jim e]] 16:55, 29 Apr 2005 (PDT)

← Older revision		Revision as of 20:29, 29 April 2005
Line 22:		Line 22:

	:We really shouldn't over complicate this. We know that there are certain instances where the DI isn't needed. That's when the interrupt won't use the lcd for anything but a status read. The most common case where an interrupt will affect the lcd driver is with the busy indicator.--[[User:Jim e\|Jim e]] 17:42, 28 Apr 2005 (PDT)		:We really shouldn't over complicate this. We know that there are certain instances where the DI isn't needed. That's when the interrupt won't use the lcd for anything but a status read. The most common case where an interrupt will affect the lcd driver is with the busy indicator.--[[User:Jim e\|Jim e]] 17:42, 28 Apr 2005 (PDT)
		+
		+	Why not just disable interrupts during fastcopy and turn them back on when returning to the program? (Or go even more tricky using ld a, i or similar.) --[[User:Aquanight\|Aquanight]] 13:29, 29 Apr 2005 (PDT)

← Older revision		Revision as of 00:42, 29 April 2005
Line 20:		Line 20:

	The main question regarding the interrupts is this: does the TI-OS touch the LCD driver if you have disabled the run indicator any anything like flashing cursors? --[[User:JasonM\|JasonM]] 16:30, 27 Apr 2005 (PDT)		The main question regarding the interrupts is this: does the TI-OS touch the LCD driver if you have disabled the run indicator any anything like flashing cursors? --[[User:JasonM\|JasonM]] 16:30, 27 Apr 2005 (PDT)
		+
		+	:We really shouldn't over complicate this. We know that there are certain instances where the DI isn't needed. That's when the interrupt won't use the lcd for anything but a status read. The most common case where an interrupt will affect the lcd driver is with the busy indicator.--[[User:Jim e\|Jim e]] 17:42, 28 Apr 2005 (PDT)

← Older revision	Revision as of 19:49, 25 October 2009
(No difference)

← Older revision		Revision as of 23:30, 27 April 2005
Line 18:		Line 18:

	:::::Well now that's just pushing towards a different topic. "When do you need to use fastcopy." I guess something should be said about when you would need to fastcopy and when ti-os handles it for you.--[[User:Jim e\|Jim e]] 14:05, 27 Apr 2005 (PDT)		:::::Well now that's just pushing towards a different topic. "When do you need to use fastcopy." I guess something should be said about when you would need to fastcopy and when ti-os handles it for you.--[[User:Jim e\|Jim e]] 14:05, 27 Apr 2005 (PDT)
		+
		+	The main question regarding the interrupts is this: does the TI-OS touch the LCD driver if you have disabled the run indicator any anything like flashing cursors? --[[User:JasonM\|JasonM]] 16:30, 27 Apr 2005 (PDT)

← Older revision		Revision as of 21:05, 27 April 2005
Line 16:		Line 16:

	::::What about grapher cursors? They dont need edit buffers.--[[User:Woozle\|Woozle]]		::::What about grapher cursors? They dont need edit buffers.--[[User:Woozle\|Woozle]]
		+
		+	:::::Well now that's just pushing towards a different topic. "When do you need to use fastcopy." I guess something should be said about when you would need to fastcopy and when ti-os handles it for you.--[[User:Jim e\|Jim e]] 14:05, 27 Apr 2005 (PDT)

← Older revision		Revision as of 20:40, 27 April 2005
Line 14:		Line 14:
	::And when the cursor flash has been disabled.--[[User:Kalimero\|Kalimero]] 03:22, 27 Apr 2005 (PDT)		::And when the cursor flash has been disabled.--[[User:Kalimero\|Kalimero]] 03:22, 27 Apr 2005 (PDT)
	:::Well the cursor should only flash if the edit buffer is open, and shouldn't be.--[[User:Jim e\|Jim e]] 07:16, 27 Apr 2005 (PDT)		:::Well the cursor should only flash if the edit buffer is open, and shouldn't be.--[[User:Jim e\|Jim e]] 07:16, 27 Apr 2005 (PDT)
		+
		+	::::What about grapher cursors? They dont need edit buffers.--[[User:Woozle\|Woozle]]

@@ Line 13: / Line 13: @@
 :True, but this isn't necessarily pertaining to MirageOS, or any shell for that matter.  A nostub program would need to disable interrupts or disable the busy indicator. A note should be made about why DI could dispensible, if a person disables the busy indicator.--[[User:Jim e|Jim e]] 20:16, 26 Apr 2005 (PDT)
 ::And when the cursor flash has been disabled.--[[User:Kalimero|Kalimero]] 03:22, 27 Apr 2005 (PDT)
-:::Well the cursor should only flash if the edit buffer is open, ad shouldn't be.--[[User:Jim e|Jim e]] 07:16, 27 Apr 2005 (PDT)
+:::Well the cursor should only flash if the edit buffer is open, and shouldn't be.--[[User:Jim e|Jim e]] 07:16, 27 Apr 2005 (PDT)