Home
last modified time | relevance | path

Searched hist:f2f9bb5e712d3ec1d7dda5a5b52c8f8701a93d99 (Results 1 – 1 of 1) sorted by relevance

/rk3399_ARM-atf/
H A DMakefilef2f9bb5e712d3ec1d7dda5a5b52c8f8701a93d99 Mon Feb 10 16:18:59 UTC 2014 James Morrissey <james.morrissey@arm.com> Add IO abstraction framework

This is intended primarily for use as a storage abstraction.
It allows operations such as image-loading to be implemented
in a platform-independent fashion. Each platform registers
a set of IO drivers during initialisation. The platform must
also provide a function that will return a device and a specifier
that can be used to access specified content.

Clients of the API will primarily use device and entity handles.
The term "entity" is deliberately vague, to allow for different
representations of content accessed using different types of
specifier, but will often be interpreted as a "file" where the
specifier will normally be its path.

This commit builds, but is intended to be paired with a sample
implementation of "load_image" using a semi-hosting driver on FVP.

Change-Id: Id3b52f1c0eb9ce76b44b99fc6b6460803668cc86