mirror of
https://github.com/reactos/reactos.git
synced 2024-11-07 15:10:53 +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
17 lines
314 B
C
17 lines
314 B
C
#ifndef s6_addr
|
|
|
|
typedef struct in6_addr {
|
|
union {
|
|
UCHAR Byte[16];
|
|
USHORT Word[8];
|
|
} u;
|
|
} IN6_ADDR, *PIN6_ADDR, FAR *LPIN6_ADDR;
|
|
|
|
#define in_addr6 in6_addr
|
|
#define _S6_un u
|
|
#define _S6_u8 Byte
|
|
#define s6_addr _S6_un._S6_u8
|
|
#define s6_bytes u.Byte
|
|
#define s6_words u.Word
|
|
|
|
#endif
|