Lines Matching refs:sandbox

9 The 'sandbox' architecture is designed to allow U-Boot to run under Linux on
14 of the sandbox U-Boot. The purpose of running U-Boot under Linux is to test
20 The board name is 'sandbox' but the vendor name is unset, so there is a
21 single board in board/sandbox.
26 There are two versions of the sandbox: One using 32-bit-wide integers, and one
29 default, the sandbox it built for a 32-bit host. The sandbox using 64-bit-wide
38 To run sandbox U-Boot use something like:
46    build sandbox without SDL (i.e. no display/keyboard support) by removing
47    the CONFIG_SANDBOX_SDL line in include/configs/sandbox.h or using:
52 U-Boot will start on your computer, showing a sandbox emulation of the serial
67 not supported you can add it to include/configs/sandbox.h.
76 sandbox with LCD and keyboard emulation, using something like:
83 tree file - see arch/sandbox/dts/sandbox.dts.
103 (it is stored at arch/sandbox/dts/sandbox.dts) you must rebuild U-Boot to
131 With sandbox you can write drivers which emulate the operation of drivers on
153 Since there is no machine architecture, sandbox U-Boot cannot actually boot
158 When 'bootm' runs a kernel, sandbox will exit, as U-Boot does on a real
174 U-Boot sandbox supports these emulations:
193 Also sandbox supports driver model (CONFIG_DM) and associated commands.
201 functionality to be tested in sandbox against real network traffic.
217 The default device tree for sandbox includes an entry for eth0 on the sandbox
259 The default device tree for sandbox includes an entry for lo on the sandbox
306 Drivers are connected to a particular bus/cs using sandbox's state
351 Generally you should put your driver in a file containing the word 'sandbox'
360 See arch/sandbox/include/asm/state.h for documentation. In short you provide
370 U-Boot sandbox can be used to run various tests, mostly in the test/
380 	  ./test/py/test.py --bd sandbox --build -k ut_dm -v