mirror of
https://github.com/reactos/reactos.git
synced 2024-10-06 09:24:11 +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
44 lines
1.6 KiB
C
44 lines
1.6 KiB
C
#include "wdm.h"
|
|
|
|
#ifdef EXPORT
|
|
#undef EXPORT
|
|
#endif
|
|
#define EXPORT __cdecl
|
|
|
|
|
|
typedef VOID (EXPORT *PACPI_OP_REGION_CALLBACK)();
|
|
|
|
typedef
|
|
NTSTATUS
|
|
(EXPORT *PACPI_OP_REGION_HANDLER) (ULONG AccessType,
|
|
PVOID OperationRegionObject,
|
|
ULONG Address,
|
|
ULONG Size,
|
|
PULONG Data,
|
|
ULONG_PTR Context,
|
|
PACPI_OP_REGION_CALLBACK CompletionHandler,
|
|
PVOID CompletionContext);
|
|
|
|
NTSTATUS
|
|
RegisterOpRegionHandler (IN PDEVICE_OBJECT DeviceObject,
|
|
IN ULONG AccessType,
|
|
IN ULONG RegionSpace,
|
|
IN PACPI_OP_REGION_HANDLER Handler,
|
|
IN PVOID Context, IN ULONG Flags,
|
|
IN OUT PVOID *OperationRegionObject);
|
|
|
|
NTSTATUS
|
|
DeRegisterOpRegionHandler (IN PDEVICE_OBJECT DeviceObject,
|
|
IN PVOID OperationRegionObject);
|
|
|
|
#define ACPI_OPREGION_ACCESS_AS_RAW 0x1
|
|
#define ACPI_OPREGION_ACCESS_AS_COOKED 0x2
|
|
#define ACPI_OPREGION_REGION_SPACE_MEMORY 0x0
|
|
#define ACPI_OPREGION_REGION_SPACE_IO 0x1
|
|
#define ACPI_OPREGION_REGION_SPACE_PCI_CONFIG 0x2
|
|
#define ACPI_OPREGION_REGION_SPACE_EC 0x3
|
|
#define ACPI_OPREGION_REGION_SPACE_SMB 0x4
|
|
#define ACPI_OPREGION_READ 0x0
|
|
#define ACPI_OPREGION_WRITE 0x1
|
|
#define ACPI_OPREGION_ACCESS_AT_HIGH_LEVEL 0x1
|