Lines Matching refs:run
80 run-time
83 - The image description is automatically available at run-time in U-Boot,
197 or use buildman to build U-Boot. There is no need to run binman independently
202 (the 'inputs' rule), then binman is run to produce the final images (the 'all'
359 provided by Intel which must be run for the platform to work. Typically
380 You can run binman directly if you put it on your PATH. But if you want to
455 Access to binman entry offsets at run time (symbols)
459 This information may be useful to U-Boot at run time. For example, in SPL it
518 Access to binman entry offsets at run time (fdt)
526 the devicetree. These can be used by U-Boot at run-time to find the location
928 operation, but his property can be read at run time.
1001 `fred.bin` from a previous run.
1592 Python functions to run the tool for each purpose (e.g. creating a new
1664 - **test** - run tests
1758 `Access to binman entry offsets at run time (fdt)`_.
1911 Test names to run (omit for all)
1923 run tests and check for 100% coverage
1927 output directory if a single test is run (pass test name at the end of the
2004 run first, this method should return False, in which case it will be called
2054 See 'Access to binman entry offsets at run time' below for a description of
2204 Binman tries to run tests concurrently. This means that the tests make use of
2205 all available CPUs to run.
2231 Binman's tests have been written under the assumption that they'll be run on a
2233 However, it's possible to run the tests by cross-compiling to x86.
2239 Then, you can run the tests under cross-compilation::