DSP:RegisterInterruptEvents - Revision history

Merry at 21:44, 7 March 2016

2016-03-07T20:44:31Z

← Older revision		Revision as of 23:44, 7 March 2016
Line 39:		Line 39:
	DSP can hold up to 6 concurrent registrations. More than that will cause registration to fail.		DSP can hold up to 6 concurrent registrations. More than that will cause registration to fail.

	Interrupts with interupt=2 are related to [[DSP:WriteProcessPipe\|pipes]]. The channel argument is the same as the pipe channel argument. The interrupt is signalled when data is available on a pipe or when a related event occurs.		Interrupts with interupt=2 are related to [[DSP:WriteProcessPipe\|pipes]]. The channel argument is the same as the pipe channel argument. The interrupt is signalled when data is available on the related pipe or when a related event occurs.

2016-03-07T20:44:15Z

← Older revision		Revision as of 23:44, 7 March 2016
Line 38:		Line 38:

	DSP can hold up to 6 concurrent registrations. More than that will cause registration to fail.		DSP can hold up to 6 concurrent registrations. More than that will cause registration to fail.

			Interrupts with interupt=2 are related to [[DSP:WriteProcessPipe\|pipes]]. The channel argument is the same as the pipe channel argument. The interrupt is signalled when data is available on a pipe or when a related event occurs.

2016-02-15T11:29:42Z

← Older revision		Revision as of 14:29, 15 February 2016
Line 36:		Line 36:
	=Description=		=Description=
	Application should unregister the event by setting handle to zero. If the session was closed before the event was unregistered, it will cause a handle leak in DSP process.		Application should unregister the event by setting handle to zero. If the session was closed before the event was unregistered, it will cause a handle leak in DSP process.

			DSP can hold up to 6 concurrent registrations. More than that will cause registration to fail.

2015-10-09T03:49:40Z

Clean up.

← Older revision		Revision as of 07:49, 9 October 2015
Line 9:		Line 9:
	\|-		\|-
	\| 1		\| 1
	\| ~~param0~~		\| Interrupt
	\|-		\|-
	\| 2		\| 2
	\| ~~param1~~		\| Channel
	\|-		\|-
	\| 3		\| 3
	\| 0		\| 0x0
	\|-		\|-
	\| 4		\| 4
	\| Event handle, 0 ~~for~~ unregister the event that was previous registered		\| Event handle (0 = unregister the event that was previous registered)
	\|}		\|}

Line 34:		Line 34:
	\|}		\|}

	Application should unregister the event by setting handle to zero~~, if~~ the session was closed before the event ~~is unregisterd~~, it will cause a handle leak in ~~dsp~~ process.		=Description=
			Application should unregister the event by setting handle to zero. If the session was closed before the event was unregistered, it will cause a handle leak in DSP process.

2015-06-21T21:00:54Z

← Older revision		Revision as of 01:00, 22 June 2015
Line 28:		Line 28:
	\|-		\|-
	\| 0		\| 0
	\| Header code [0x00150040] ~~(not fully verified)~~		\| Header code [0x00150040]
	\|-		\|-
	\| 1		\| 1

2015-06-19T20:27:30Z

← Older revision		Revision as of 00:27, 20 June 2015
Line 28:		Line 28:
	\|-		\|-
	\| 0		\| 0
	\| Header code [0x00150040]		\| Header code [0x00150040] (not fully verified)
	\|-		\|-
	\| 1		\| 1

2015-06-19T06:27:21Z

2015-03-25T13:26:10Z

← Older revision		Revision as of 16:26, 25 March 2015
Line 18:		Line 18:
	\|-		\|-
	\| 4		\| 4
	\| Event handle		\| Event handle, 0 for unregister the event that was previous registered
	\|}		\|}

Line 33:		Line 33:
	\| Result code		\| Result code
	\|}		\|}

			Application should unregister the event by setting handle to zero, if the session was closed before the event is unregisterd, it will cause a handle leak in dsp process.

2014-11-10T14:12:17Z

Request

2014-11-10T06:22:25Z

Small fixes