Home
last modified time | relevance | path

Searched refs:bootloader (Results 1 – 25 of 196) sorted by relevance

12345678

/external/vboot_reference/tests/futility/
Dtest_sign_kernel.sh16 dd if=/dev/urandom bs=512 count=1 of=${TMP}.bootloader.bin
35 --bootloader ${TMP}.bootloader.bin \
52 --bootloader ${TMP}.bootloader.bin \
78 --bootloader ${TMP}.bootloader2.bin
92 --bootloader ${TMP}.bootloader2.bin \
114 --bootloader ${TMP}.bootloader2.bin \
136 --bootloader ${TMP}.bootloader.bin \
152 --bootloader ${TMP}.bootloader.bin \
176 --bootloader ${TMP}.bootloader2.bin
197 --bootloader ${TMP}.bootloader2.bin \
[all …]
Dtest_show_kernel.sh19 dd if=/dev/urandom bs=16384 count=1 of=${TMP}.bootloader.bin
41 --bootloader ${TMP}.bootloader.bin \
/external/libese/apps/boot/
DREADME.md8 a mechanism for a device's bootloader, using [AVB](https://android.googlesource.com/platform/extern…
9 to store sensitive information. For a bootloader, sensitive information
41 non-zero value is valid and may be used by the bootloader if any additional
137 The device lock is one of the setting used by the bootloader to
149 The boot lock is used by the bootloader to control whether it should
151 is cleared (0x0), the bootloader will boot anything. When the lock
153 stored in the bootloader except if `LOCK_OWNER` is set. Discussion of
156 `LOCK_BOOT` can only be toggled when in the bootloader/fastboot and if
164 The owner lock is used by the bootloader to support an alternative
169 bootloader. `LOCK_OWNER` may be toggled in the bootloader or the
[all …]
/external/autotest/server/site_tests/enterprise_CFM_HuddlyUpdater/samples/
Dhuddly-updater-info.log6 bootloader: 0.2.1
11 bootloader: 0.2.1
/external/autotest/server/site_tests/firmware_Fingerprint/
Dcontrol.rdp129 levels through the bootloader (only accessible when HW write protect is
32 When the test script starts, a read through the bootloader is done without
36 Next a read through the bootloader is done, while also disabling flash
/external/autotest/client/bin/
Dlocal_host.py28 def _initialize(self, hostname=None, bootloader=None, *args, **dargs): argument
36 self.bootloader = bootloader
/external/chromium-trace/catapult/devil/devil/android/
Dfastboot_utils.py209 bootloader=False, argument
221 if bootloader:
297 self.Reboot(bootloader=True)
Dfastboot_utils_test.py244 self.fastboot.Reboot(bootloader=True)
261 (self.call.fastboot.Reboot(bootloader=True)),
263 (self.call.fastboot.Reboot(bootloader=True)),
278 (self.call.fastboot.Reboot(bootloader=True)),
280 (self.call.fastboot.Reboot(bootloader=True)),
303 (self.call.fastboot.Reboot(bootloader=True)),
305 (self.call.fastboot.Reboot(bootloader=True)),
/external/mesa3d/docs/ci/
Dbare-metal.rst13 and bootloader support are more primitive.
25 can see bootloader progress.
39 as fastboot, so we assume your bootloader can do TFTP, and that your
61 # filename didn't seem to get picked up by the bootloader, so we use
/external/toolchain-utils/binary_search_tool/android/
Dtest_setup.sh62 adb reboot bootloader
/external/autotest/server/hosts/
Dbase_classes.py51 bootloader = None variable in Host
/external/vboot_reference/tests/
Dload_kernel_tests.sh48 --bootloader "dummy_bootloader.bin" \
Dgen_preamble_testdata.sh79 --bootloader "${DATADIR}/dummy_bootloader.bin" \
Dgen_fuzz_test_cases.sh60 --bootloader ${TEST_BOOTLOADER_FILE} \
Drun_vbutil_kernel_arg_tests.sh109 --bootloader "${BIG}" \
/external/autotest/test_suites/
Dcontrol.brillo-presubmit16 physical devices. WiFi, fastboot and other hardware or bootloader related tests
/external/pigweed/pw_boot_armv7m/
Dbasic_armv7m.ld21 * This linker script is likely not suitable for a project with a bootloader.
90 * so it's used on reset, or by explicitly setting the VTOR in a bootloader
/external/dtc/Documentation/
Ddtc-paper.tex126 come either from the embedded bootloader, or from a specialised
132 kernel that parses it and the bootloader that generates it. In
136 \item \emph{relocatable}: the bootloader or kernel should be able to
140 \item \emph{insert and delete}: sometimes the bootloader might want to
380 and include it in the bootloader image. For minor revisions of the
381 board, the bootloader can contain code to make the necessary tweaks to
422 bootloader or firmware image.
481 the size of memory. The bootloader for such a board can have a device
569 machine. After writing a bootloader, BootX, for it in 1998, he
/external/bcc/
DFAQ.txt28 modules and headers, update your bootloader and reboot into the new
/external/arm-trusted-firmware/docs/plat/
Dintel-agilex.rst58 quartus_cpf --bootloader bl2.hex <quartus_generated_sof> <output_sof_with_bl2>
Dintel-stratix10.rst58 quartus_cpf --bootloader bl2.hex <quartus_generated_sof> <output_sof_with_bl2>
/external/e2fsprogs/doc/RelNotes/
Dv1.06.txt15 Add support for Linux/FT's bootloader, which actually uses
/external/cpuinfo/test/build.prop/
Dgalaxy-tab-3-7.0.log29 ro.bootloader=T210LKLUANB4
/external/nos/host/generic/nugget/proto/nugget/app/avb/
Davb.proto59 bool bootloader = 2; field
/external/libese/
DREADME.md81 like a bootloader or non-Linux OS, this library may need to be replaced.

12345678