Difference between revisions of "SHIP:Port:DRIVE:BULK"

From Serious Documentation
Jump to: navigation, search
 
Line 3: Line 3:
 
'''DRIVE.BULKx''' ports can be referenced in various file related actions as the device on which a file is opened/closed/read/written for example. Also theseports have various attributes to determine/control their state:
 
'''DRIVE.BULKx''' ports can be referenced in various file related actions as the device on which a file is opened/closed/read/written for example. Also theseports have various attributes to determine/control their state:
 
{{PortvarTableStart|}}
 
{{PortvarTableStart|}}
|{{:SHIP:Port:DRIVE.all:autoUpdate}}
+
|{{:SHIP:Port:DRIVE:all:autoUpdate}}
 
|}</onlyinclude>
 
|}</onlyinclude>
  
 
{{†}}see [[SHIP:GRMs|GRM]]
 
{{†}}see [[SHIP:GRMs|GRM]]

Latest revision as of 06:07, 14 November 2018

DRIVE.BULKx ports refer to file systems on bulk storage devices, such as e.MMC, NAND, or NOR Flash devices, built into the specific module and are referred to in the format "platform.DRIVE.BULK0", "platform.DRIVE.BULK1", etc. Think of DRIVE.DRIVE.BULK0 as your traditional "C drive" on a PC -- the built-in main storage device.

DRIVE.BULKx ports can be referenced in various file related actions as the device on which a file is opened/closed/read/written for example. Also theseports have various attributes to determine/control their state:

Portvar Data Type Permissions Description
autoUpdate Boolean Read/Write A reboot-persistent setting, this enables/disables (if true/false) the auto-update process if firmware update files are present on the drive.

see GRM