MCUNWM:SetWirelessDisabledFlag - Revision history

Dazzozo at 04:15, 2 May 2016

2016-05-02T02:15:45Z

← Older revision		Revision as of 06:15, 2 May 2016
Line 32:		Line 32:
	The value is loaded at FIRM boot to correctly initialize the previous wireless state that the user expects.		The value is loaded at FIRM boot to correctly initialize the previous wireless state that the user expects.

	This is stored in (volatile) MCU memory and is reset (to enabled state) at battery pull. This mostly exists here because ~~LGY FIRM~~ cannot ~~modify Config savegame blocks~~.		This is stored in (volatile) MCU memory and is reset (to enabled state) at battery pull. This mostly exists here because LgyBg cannot save any settings anywhere else (i.e. NAND).

Dazzozo: /* Description */

2016-05-02T02:10:28Z

Description

← Older revision		Revision as of 06:10, 2 May 2016
Line 32:		Line 32:
	The value is loaded at FIRM boot to correctly initialize the previous wireless state that the user expects.		The value is loaded at FIRM boot to correctly initialize the previous wireless state that the user expects.

	This is stored in (volatile) MCU memory and is reset (to enabled state) at battery pull.		This is stored in (volatile) MCU memory and is reset (to enabled state) at battery pull. This mostly exists here because LGY FIRM cannot modify Config savegame blocks.

Dazzozo: crap

2016-05-02T02:05:14Z

crap

← Older revision		Revision as of 06:05, 2 May 2016
Line 9:		Line 9:
	\|-		\|-
	\| 1		\| 1
	\| ?		\| bool, true = disabled, false = enabled
	\|}		\|}

Line 28:		Line 28:
	This writes to the MCU system-state buffer and updates the WirelessDisabled bit.		This writes to the MCU system-state buffer and updates the WirelessDisabled bit.

	This does nothing by itself, it merely records the user-specified enable/disable state for future FIRMs. When this is updated, the running FIRM would then actually enable/disable the hardware separately to this. The value is loaded at FIRM boot to correctly initialize the previous wireless state that the user expects.		This does nothing by itself, it merely records the user-specified enable/disable state for future FIRMs. When this is updated, the running FIRM would then actually enable/disable the hardware separately to this.

			The value is loaded at FIRM boot to correctly initialize the previous wireless state that the user expects.

	This is stored in (volatile) MCU memory and is reset (to enabled state) at battery pull.		This is stored in (volatile) MCU memory and is reset (to enabled state) at battery pull.

Dazzozo: Created page with "=Request= {| class="wikitable" border="1" |- ! Index Word ! Description |- | 0 | Header code [0x00070040] |- | 1 | ? |} =Response= {| class="wikitable" border="1" |- ! Ind..."

2016-05-02T02:04:17Z

Created page with "=Request= {| class="wikitable" border="1" |- ! Index Word ! Description |- | 0 | Header code [0x00070040] |- | 1 | ? |} =Response= {| class="wikitable" border="1" |- ! Ind..."

New page

=Request=
{| class="wikitable" border="1"
|-
! Index Word
! Description
|-
| 0
| Header code [0x00070040]
|-
| 1
| ?
|}

=Response=
{| class="wikitable" border="1"
|-
! Index Word
! Description
|-
| 0
| Header code
|-
| 1
| Result code
|}

=Description=
This writes to the MCU system-state buffer and updates the WirelessDisabled bit.

This does nothing by itself, it merely records the user-specified enable/disable state for future FIRMs. When this is updated, the running FIRM would then *actually* enable/disable the hardware separately to this. The value is loaded at FIRM boot to correctly initialize the previous wireless state that the user expects.

This is stored in (volatile) MCU memory and is reset (to enabled state) at battery pull.