340
edits
Changes
Jump to navigation
Jump to search
m
Removed un-needed WD_SendBeacon info.
Line 117:
Line 117:
Ioctl 0x1009 input is a buffer/len pair.
Ioctl 0x1009 input is a buffer/len pair.
−WD_SendBeacon second input is the Nintendo tag code 0xDD data, starting after the timestamp. First input is a unknown pointer to a u16. Nintendo Channel increases this, then wraps around once the limit of 0xFFFF is reached. Might be the Nintendo tag timestamp? When state is 1, the tag data is copied to internal config.mpParent.beacon_nintagdata, fixed length of 0x80, when second input is not null. And the first input is written to config.mpParent.unk1_4. Unknown if the beacon is sent immediately, or via a IOS timer? It may be possible to send beacons larger than 0x70 payloadLength at offset 16 in tag data, but that's only possible if the beacon is sent immediately. If beacons are not sent immediately, beacon sending may be disabled by using WD_SetConfig(config, 0, BIT(4)), with config->mpParent.unk1_4 being 0?
+WD_SendBeacon second input is the Nintendo tag code 0xDD data, starting after the timestamp. First input might be a u16* for the Nintendo tag timestamp?
WD_SetLinkState might change which "mode"/"state" is used; 0 for Infrastructure, 1 for Ad-Hoc?
WD_SetLinkState might change which "mode"/"state" is used; 0 for Infrastructure, 1 for Ad-Hoc?
Line 189:
Line 189:
u8 maxNodes;//Must be less than 16.
u8 maxNodes;//Must be less than 16.
u8 authAlgorithm;//Must be less than 2. 0 = Open, 1 = Shared.
u8 authAlgorithm;//Must be less than 2. 0 = Open, 1 = Shared.
− u16 unk1_4;//unk field 4 of flags 1 fields.
+ u16 beacon_nintagtimestamp;//? bit 4 of flags 1 fields.
u8 channel;//Not verified if 0, but when non-zero, must be an available Nitro Allowed Channel. See _wd_info.ntr_allowed_channels.
u8 channel;//Not verified if 0, but when non-zero, must be an available Nitro Allowed Channel. See _wd_info.ntr_allowed_channels.
u8 unka4[3];
u8 unka4[3];