Storage information. More...
|Total available storage, in bytes. More...|
|Minimum programming size in bytes. More...|
|Optimal programming page-size in bytes. More...|
|A measure of endurance for reprogramming. More...|
|Contents of erased memory (usually 1 to indicate erased bytes with state 0xFF). More...|
|This storage device has a mapping onto the processor's memory address space. More...|
|A value to indicate storage programmability. More...|
This contains device-metadata. It is the return value from calling GetInfo() on the storage driver.
These fields serve a different purpose than the ones contained in ARM_STORAGE_CAPABILITIES, which is another structure containing device-level metadata. ARM_STORAGE_CAPABILITIES describes the API capabilities, whereas ARM_STORAGE_INFO describes the device. Furthermore ARM_STORAGE_CAPABILITIES fits within a single word, and is designed to be passed around by value; ARM_STORAGE_INFO, on the other hand, contains metadata which doesn't fit into a single word and requires the use of pointers to be moved around.
This storage device has a mapping onto the processor's memory address space.
Optimal programming page-size in bytes.
Some storage controllers have internal buffers into which to receive data. Writing in chunks of 'optimal_program_unit' would achieve maximum programming speed. Applicable only if the 'programmable' attribute is set for the underlying block(s).
Minimum programming size in bytes.
The offset of the start of the program-range should also be aligned with this value. Applicable only if the 'programmable' attribute is set for a block.