Lines Matching refs:sandbox

11 The 'sandbox' architecture is designed to allow U-Boot to run under Linux on
16 of the sandbox U-Boot. The purpose of running U-Boot under Linux is to test
22 The board name is 'sandbox' but the vendor name is unset, so there is a
23 single board in board/sandbox.
28 There are two versions of the sandbox: One using 32-bit-wide integers, and one
31 default, the sandbox it built for a 32-bit host. The sandbox using 64-bit-wide
40 To run sandbox U-Boot use something like::
47 build sandbox without SDL (i.e. no display/keyboard support) by removing
48 the CONFIG_SANDBOX_SDL line in include/configs/sandbox.h or using::
53 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
133 With sandbox you can write drivers which emulate the operation of drivers on
155 Since there is no machine architecture, sandbox U-Boot cannot actually boot
160 When 'bootm' runs a kernel, sandbox will exit, as U-Boot does on a real
176 U-Boot sandbox supports these emulations:
195 Also sandbox supports driver model (CONFIG_DM) and associated commands.
203 sandbox:
213   builds sandbox with SPL support, so you can run spl/u-boot-spl
217 Of these sandbox_spl can probably be removed since it is a superset of sandbox.
227 functionality to be tested in sandbox against real network traffic.
243 The default device tree for sandbox includes an entry for eth0 on the sandbox
290 The default device tree for sandbox includes an entry for lo on the sandbox
339 Drivers are connected to a particular bus/cs using sandbox's state
383 Generally you should put your driver in a file containing the word 'sandbox'
392 See arch/sandbox/include/asm/state.h for documentation. In short you provide
424    Starting program: /tmp/b/sandbox/u-boot
441 This approach can be used on normal boards as well as sandbox.
458 If you are running sandbox SPL or TPL, then valgrind will not by default
468 U-Boot sandbox can be used to run various tests, mostly in the test/
479    ./test/py/test.py --bd sandbox --build -k ut_dm -v
499 To run a single test in an existing sandbox build, you can use -T to use the
502   /tmp/b/sandbox/u-boot -T -c "ut dm pci_busdev"