mirror of
https://github.com/reactos/reactos.git
synced 2024-09-09 04:10:19 +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
15 lines
446 B
C
15 lines
446 B
C
#pragma once
|
|
|
|
void initme(void);
|
|
void mmusetramsize(paddr_t size);
|
|
int mmuaddpage(ppc_map_info_t *info, int count);
|
|
void mmudelpage(ppc_map_info_t *info, int count);
|
|
void mmugetpage(ppc_map_info_t *info, int count);
|
|
void mmusetvsid(int start, int end, int vsid);
|
|
void *allocvsid(int);
|
|
void mmuallocvsid(int vsid, int mask);
|
|
void freevsid(int);
|
|
void mmufreevsid(int vsid, int mask);
|
|
int mmunitest(void);
|
|
void callkernel(void *fun_ptr, void *arg);
|