mirror of
https://github.com/reactos/reactos.git
synced 2024-09-17 16:20:20 +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
9 lines
316 B
C
9 lines
316 B
C
#pragma once
|
|
|
|
|
|
NTSTATUS _MmCopyFromCaller( PVOID Target, PVOID Source, UINT Bytes );
|
|
NTSTATUS _MmCopyToCaller( PVOID Target, PVOID Source, UINT Bytes );
|
|
|
|
#define MmCopyFromCaller(x,y,z) _MmCopyFromCaller((PCHAR)(x),(PCHAR)(y),(UINT)(z))
|
|
#define MmCopyToCaller(x,y,z) _MmCopyToCaller((PCHAR)(x),(PCHAR)(y),(UINT)(z))
|