mirror of
https://github.com/reactos/reactos.git
synced 2024-09-19 01:00:51 +00:00
e1ef078741
The idea then would be to have the following behaviour (when specifying the following options in the kernel command line): /DEBUGPORT=COMi --> load KDCOM.DLL and use COMi port (i == 1,2,3,4) if possible. /DEBUGPORT=FOO --> load KDFOO.DLL (useful for KDUSB.DLL, KD1394.DLL, KDBAZIS.DLL for VirtualKD, etc...) /DEBUGPORT=ROSDBG:[COMi|SCREEN|FILE|GDB|...] --> load KDROSDBG.DLL which contains the ROS kernel debugger, and use COMi or SCREEN or... as output port. svn path=/branches/kd++/; revision=58883
18 lines
220 B
ArmAsm
18 lines
220 B
ArmAsm
|
|
//
|
|
// @name GENERATE_INT_HANDLER
|
|
//
|
|
// This macro creates an unexpected interrupt handler.
|
|
//
|
|
// @param None.
|
|
//
|
|
// @remark None.
|
|
//
|
|
.macro GENERATE_ARM_STUB Name
|
|
.global &Name
|
|
.func &Name
|
|
&Name:
|
|
b .
|
|
.endfunc
|
|
.endm
|