Difference between revisions of "MCUNWM:SetWirelessDisabledFlag"
Jump to navigation
Jump to search
(Created page with "=Request= {| class="wikitable" border="1" |- ! Index Word ! Description |- | 0 | Header code [0x00070040] |- | 1 | ? |} =Response= {| class="wikitable" border="1" |- ! Ind...") |
|||
| (2 intermediate revisions by the same user not shown) | |||
| 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 | + | 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. |
| − | This is stored in (volatile) MCU memory and is reset (to enabled state) at battery pull. | + | 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 LgyBg cannot save any settings anywhere else (i.e. NAND). | ||
Latest revision as of 05:15, 2 May 2016
Request[edit]
| Index Word | Description |
|---|---|
| 0 | Header code [0x00070040] |
| 1 | bool, true = disabled, false = enabled |
Response[edit]
| Index Word | Description |
|---|---|
| 0 | Header code |
| 1 | Result code |
Description[edit]
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. This mostly exists *here* because LgyBg cannot save any settings anywhere else (i.e. NAND).