Lines Matching full:sandbox

10 The 'sandbox' architecture is designed to allow U-Boot to run under Linux on
15 of the sandbox U-Boot. The purpose of running U-Boot under Linux is to test
21 The board name is 'sandbox' but the vendor name is unset, so there is a
22 single board in board/sandbox.
33 To run sandbox U-Boot use something like:
41    build sandbox without SDL (i.e. no display/keyboard support) by removing
42    the CONFIG_SANDBOX_SDL line in include/configs/sandbox.h or using:
49    include/configs/sandbox.h and change CONFIG_SANDBOX_BITS_PER_LONG to 32.
51 U-Boot will start on your computer, showing a sandbox emulation of the serial
66 not supported you can add it to include/configs/sandbox.h.
75 sandbox with LCD and keyboard emulation, using something like:
82 tree file - see arch/sandbox/dts/sandbox.dts.
102 (it is stored at arch/sandbox/dts/sandbox.dts) you must rebuild U-Boot to
130 With sandbox you can write drivers which emulate the operation of drivers on
145 whatever properties it likes in there. See 'Writing Sandbox Drivers' below
152 Since there is no machine architecture, sandbox U-Boot cannot actually boot
157 When 'bootm' runs a kernel, sandbox will exit, as U-Boot does on a real
173 U-Boot sandbox supports these emulations:
192 Also sandbox supports driver model (CONFIG_DM) and associated commands.
200 functionality to be tested in sandbox against real network traffic.
216 The default device tree for sandbox includes an entry for eth0 on the sandbox
258 The default device tree for sandbox includes an entry for lo on the sandbox
272 Sandbox supports SPI and SPI flash emulation.
305 Drivers are connected to a particular bus/cs using sandbox's state
347 Writing Sandbox Drivers
350 Generally you should put your driver in a file containing the word 'sandbox'
359 See arch/sandbox/include/asm/state.h for documentation. In short you provide
369 U-Boot sandbox can be used to run various tests, mostly in the test/
379 	  ./test/py/test.py --bd sandbox --build -k ut_dm -v