summaryrefslogtreecommitdiffstats
path: root/qemu/roms/u-boot/api/README
diff options
context:
space:
mode:
authorRajithaY <rajithax.yerrumsetty@intel.com>2017-04-25 03:31:15 -0700
committerRajitha Yerrumchetty <rajithax.yerrumsetty@intel.com>2017-05-22 06:48:08 +0000
commitbb756eebdac6fd24e8919e2c43f7d2c8c4091f59 (patch)
treeca11e03542edf2d8f631efeca5e1626d211107e3 /qemu/roms/u-boot/api/README
parenta14b48d18a9ed03ec191cf16b162206998a895ce (diff)
Adding qemu as a submodule of KVMFORNFV
This Patch includes the changes to add qemu as a submodule to kvmfornfv repo and make use of the updated latest qemu for the execution of all testcase Change-Id: I1280af507a857675c7f81d30c95255635667bdd7 Signed-off-by:RajithaY<rajithax.yerrumsetty@intel.com>
Diffstat (limited to 'qemu/roms/u-boot/api/README')
-rw-r--r--qemu/roms/u-boot/api/README55
1 files changed, 0 insertions, 55 deletions
diff --git a/qemu/roms/u-boot/api/README b/qemu/roms/u-boot/api/README
deleted file mode 100644
index 6df225f58..000000000
--- a/qemu/roms/u-boot/api/README
+++ /dev/null
@@ -1,55 +0,0 @@
-U-Boot machine/arch independent API for external apps
-=====================================================
-
-1. Main assumptions
-
- - there is a single entry point (syscall) to the API
-
- - per current design the syscall is a C-callable function in the U-Boot
- text, which might evolve into a real syscall using machine exception trap
- once this initial version proves functional
-
- - the consumer app is responsible for producing appropriate context (call
- number and arguments)
-
- - upon entry, the syscall dispatches the call to other (existing) U-Boot
- functional areas like networking or storage operations
-
- - consumer application will recognize the API is available by searching
- a specified (assumed by convention) range of address space for the
- signature
-
- - the U-Boot integral part of the API is meant to be thin and non-intrusive,
- leaving as much processing as possible on the consumer application side,
- for example it doesn't keep states, but relies on hints from the app and
- so on
-
- - optional (CONFIG_API)
-
-
-2. Calls
-
- - console related (getc, putc, tstc etc.)
- - system (reset, platform info)
- - time (delay, current)
- - env vars (enumerate all, get, set)
- - devices (enumerate all, open, close, read, write); currently two classes
- of devices are recognized and supported: network and storage (ide, scsi,
- usb etc.)
-
-
-3. Structure overview
-
- - core API, integral part of U-Boot, mandatory
- - implements the single entry point (mimics UNIX syscall)
-
- - glue
- - entry point at the consumer side, allows to make syscall, mandatory
- part
-
- - helper conveniency wrappers so that consumer app does not have to use
- the syscall directly, but in a more friendly manner (a la libc calls),
- optional part
-
- - consumer application
- - calls directly, or leverages the provided glue mid-layer