mirror of
https://github.com/reactos/reactos.git
synced 2024-09-14 14:51:27 +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
22 lines
633 B
Python
22 lines
633 B
Python
; Old KD
|
|
@ stdcall KdPortGetByte(ptr)
|
|
@ stdcall KdPortGetByteEx(ptr ptr)
|
|
@ stdcall KdPortInitialize(ptr long long)
|
|
@ stdcall KdPortInitializeEx(ptr long long)
|
|
@ stdcall KdPortPollByte(ptr)
|
|
@ stdcall KdPortPollByteEx(ptr ptr)
|
|
@ stdcall KdPortPutByte(long)
|
|
@ stdcall KdPortPutByteEx(ptr long)
|
|
@ stdcall KdPortRestore()
|
|
@ stdcall KdPortSave()
|
|
@ stdcall KdPortDisableInterrupts()
|
|
@ stdcall KdPortEnableInterrupts()
|
|
|
|
; New KD
|
|
@ stdcall KdDebuggerInitialize0(ptr)
|
|
@ stdcall KdDebuggerInitialize1(ptr)
|
|
@ stdcall KdSave(long)
|
|
@ stdcall KdRestore(long)
|
|
@ stdcall KdReceivePacket(long ptr ptr ptr ptr)
|
|
@ stdcall KdSendPacket(long ptr ptr ptr)
|