Home
last modified time | relevance | path

Searched refs:BIOS (Results 1 – 25 of 237) sorted by relevance

12345678910

/external/vboot_reference/tests/futility/
Dtest_load_fmap.sh14 BIOS=${TMP}.bios.bin
16 cp ${IN} ${BIOS}
21 ${FUTILITY} dump_fmap -x ${BIOS} ${AREAS}
33 ${FUTILITY} load_fmap ${BIOS} ${CMDS}
36 ${FUTILITY} dump_fmap -x ${BIOS} ${AREAS}
/external/autotest/test_suites/
Dcontrol.faft_lv216 This test suite runs FAFT (Fully Automated Firmware Test) for BIOS that should
17 all pass and that verifies the BIOS fit Chrome OS verified-boot requirements.
19 All BIOS tests are categorized into 5 test levels:
20 Level-1: Basic BIOS tests which verify basic vboot functions.
21 Level-2: Recovery BIOS tests which need external USB disk.
22 Level-3: Corruption BIOS tests which modify firmware/kernel image.
24 Level-4: Advanced BIOS tests which verify not-so-critical features.
Dcontrol.faft_lv516 This test suite runs FAFT (Fully Automated Firmware Test) for BIOS that should
17 all pass and that verifies the BIOS fit Chrome OS verified-boot requirements.
19 All BIOS tests are categorized into 5 test levels:
20 Level-1: Basic BIOS tests which verify basic vboot functions.
21 Level-2: Recovery BIOS tests which need external USB disk.
22 Level-3: Corruption BIOS tests which modify firmware/kernel image.
24 Level-4: Advanced BIOS tests which verify not-so-critical features.
Dcontrol.faft_lv116 This test suite runs FAFT (Fully Automated Firmware Test) for BIOS that should
17 all pass and that verifies the BIOS fit Chrome OS verified-boot requirements.
19 All BIOS tests are categorized into 5 test levels:
20 Level-1: Basic BIOS tests which verify basic vboot functions.
21 Level-2: Recovery BIOS tests which need external USB disk.
22 Level-3: Corruption BIOS tests which modify firmware/kernel image.
24 Level-4: Advanced BIOS tests which verify not-so-critical features.
Dcontrol.faft_lv316 This test suite runs FAFT (Fully Automated Firmware Test) for BIOS that should
17 all pass and that verifies the BIOS fit Chrome OS verified-boot requirements.
19 All BIOS tests are categorized into 5 test levels:
20 Level-1: Basic BIOS tests which verify basic vboot functions.
21 Level-2: Recovery BIOS tests which need external USB disk.
22 Level-3: Corruption BIOS tests which modify firmware/kernel image.
24 Level-4: Advanced BIOS tests which verify not-so-critical features.
Dcontrol.faft_lv416 This test suite runs FAFT (Fully Automated Firmware Test) for BIOS that should
17 all pass and that verifies the BIOS fit Chrome OS verified-boot requirements.
19 All BIOS tests are categorized into 5 test levels:
20 Level-1: Basic BIOS tests which verify basic vboot functions.
21 Level-2: Recovery BIOS tests which need external USB disk.
22 Level-3: Corruption BIOS tests which modify firmware/kernel image.
24 Level-4: Advanced BIOS tests which verify not-so-critical features.
/external/autotest/server/site_tests/firmware_ChipFwUpdate/
Dfirmware_ChipFwUpdate.py67 BIOS = 'bios.bin' variable in firmware_ChipFwUpdate
128 chip.chip_name, self.BIOS)
132 chip.chip_name, self.BIOS)
139 chip.chip_name, self.BIOS)
150 self.BIOS, chip.chip_name, bundled_fw_ver)
165 logging.info('replacing %s firmware in %s', chip_name, self.BIOS)
/external/autotest/server/site_tests/firmware_CompareChipFwToShellBall/
Dfirmware_CompareChipFwToShellBall.py34 BIOS = 'bios.bin' variable in firmware_CompareChipFwToShellBall
162 chip.chip_name, self.BIOS)
169 chip.chip_name, self.BIOS)
181 self.BIOS, chip.chip_name, bundled_fw_ver)
/external/autotest/server/site_tests/firmware_FMap/
Dcontrol.dev9 PURPOSE = "Check the existence of BIOS and EC FMap and the required FMap areas"
19 This test checks the active BIOS and EC firmware contains the required
21 the active BIOS and EC firmware and dump_fmap to decode them.
Dcontrol9 PURPOSE = "Check the existence of BIOS and EC FMap and the required FMap areas"
19 This test checks the active BIOS and EC firmware contains the required
21 the active BIOS and EC firmware and dump_fmap to decode them.
/external/u-boot/arch/x86/include/asm/arch-quark/acpi/
Dsouthcluster.asl85 /* BIOS Extension (0xe0000-0xe3fff) */
91 /* BIOS Extension (0xe4000-0xe7fff) */
97 /* BIOS Extension (0xe8000-0xebfff) */
103 /* BIOS Extension (0xec000-0xeffff) */
109 /* System BIOS (0xf0000-0xfffff) */
/external/u-boot/arch/x86/include/asm/arch-baytrail/acpi/
Dsouthcluster.asl88 /* BIOS Extension (0xe0000-0xe3fff) */
94 /* BIOS Extension (0xe4000-0xe7fff) */
100 /* BIOS Extension (0xe8000-0xebfff) */
106 /* BIOS Extension (0xec000-0xeffff) */
112 /* System BIOS (0xf0000-0xfffff) */
/external/autotest/client/site_tests/firmware_LockedME/
Dcontrol8 CRITERIA = "Fail if any part of the BIOS ME region is mutable from userspace"
15 Intel x86 CPUs (Sandybridge and later) reserve a portion of the BIOS
17 requires that section of the BIOS flash to be mutable. The ME firmware
/external/syzkaller/pkg/report/testdata/linux/report/
D1356 [ 177.902067] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
22 [ 179.076171] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
D11510 [ 76.661710] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
31 [ 76.940499] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
D2289 [ 177.014155] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
58 [ 177.214312] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
102 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
D1209 [ 80.262197] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
28 [ 80.272175] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
D12728 [ 0.000000] e820: BIOS-provided physical RAM map:
29 [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
D2298 [ 212.571646] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
69 [ 212.872149] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
147 [ 213.238994] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
D1428 [ 95.884050] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
17 [ 95.884317] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
D1968 [ 67.633801] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
26 [ 27.260654] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01…
/external/autotest/server/site_tests/firmware_Bmpblk/
Dcontrol17 This test checks whether the BIOS was built with a correctly configured bmpblk
20 optimal quality. Relies on flashrom and cbfstool to inspect the BIOS image.
/external/u-boot/arch/x86/
DKconfig534 bool "Add a VGA BIOS image"
536 Select this option if you have a VGA BIOS image that you would
540 string "VGA BIOS image filename"
544 The filename of the VGA BIOS image in the board directory.
547 hex "VGA BIOS image location"
551 The location of VGA BIOS image in the SPI flash. For example, base
556 bool "Add a Video BIOS Table (VBT) image"
559 Select this option if you have a Video BIOS Table (VBT) image that
564 Video BIOS Table, or VBT, provides platform and board specific
573 string "Video BIOS Table (VBT) image filename"
[all …]
/external/u-boot/arch/x86/cpu/queensbay/
DKconfig34 access when powered up before system BIOS is executed.
65 card's VGA BIOS and use that card for the graphics console.
/external/u-boot/doc/
DREADME.hwconfig10 interface for Award BIOS-like interface, and frame-buffer
11 interface for AMI GUI[1] BIOS-like interface with mouse

12345678910