Home
last modified time | relevance | path

Searched refs:boot (Results 1 – 200 of 1011) sorted by relevance

123456

/linux-4.4.14/drivers/isdn/hysdn/
Dhysdn_boot.c57 StartDecryption(struct boot_data *boot) in StartDecryption() argument
59 boot->Cryptor = CRYPT_STARTTERM; in StartDecryption()
70 DecryptBuf(struct boot_data *boot, int cnt) in DecryptBuf() argument
72 unsigned char *bufp = boot->buf.BootBuf; in DecryptBuf()
75 boot->Cryptor = (boot->Cryptor >> 1) ^ ((boot->Cryptor & 1U) ? CRYPT_FEEDTERM : 0); in DecryptBuf()
76 *bufp++ ^= (unsigned char)boot->Cryptor; in DecryptBuf()
87 struct boot_data *boot = card->boot; /* pointer to boot specific data */ in pof_handle_data() local
93 switch (boot->pof_recid) { in pof_handle_data()
97 hysdn_addlog(card, "POF created %s", boot->buf.PofTime.DateTimeText); in pof_handle_data()
101 DecryptBuf(boot, datlen); /* we need to encrypt the buffer */ in pof_handle_data()
[all …]
/linux-4.4.14/arch/xtensa/boot/
DMakefile12 KBUILD_CFLAGS += -fno-builtin -Iarch/$(ARCH)/boot/include
13 HOSTFLAGS += -Iarch/$(ARCH)/boot/include
24 bootdir-$(CONFIG_XTENSA_PLATFORM_ISS) += boot-elf
25 bootdir-$(CONFIG_XTENSA_PLATFORM_XT2000) += boot-redboot boot-elf boot-uboot
26 bootdir-$(CONFIG_XTENSA_PLATFORM_XTFPGA) += boot-redboot boot-elf boot-uboot
42 boot-elf: vmlinux.bin
43 boot-redboot: vmlinux.bin.gz
44 boot-uboot: vmlinux.bin.gz
/linux-4.4.14/arch/unicore32/
D.gitignore10 # Generated images in boot
12 boot/Image
13 boot/zImage
14 boot/uImage
16 # Generated files in boot/compressed
18 boot/compressed/piggy.S
19 boot/compressed/piggy.gzip
20 boot/compressed/vmlinux
21 boot/compressed/vmlinux.lds
DMakefile42 boot := arch/unicore32/boot macro
51 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
54 $(Q)$(MAKE) $(clean)=$(boot)
/linux-4.4.14/arch/arm/boot/dts/
Dmmp2-brownstone.dts45 regulator-boot-on;
51 regulator-boot-on;
57 regulator-boot-on;
63 regulator-boot-on;
69 regulator-boot-on;
75 regulator-boot-on;
81 regulator-boot-on;
87 regulator-boot-on;
93 regulator-boot-on;
99 regulator-boot-on;
[all …]
Dimx53-qsrb.dts45 regulator-boot-on;
53 regulator-boot-on;
61 regulator-boot-on;
69 regulator-boot-on;
76 regulator-boot-on;
84 regulator-boot-on;
92 regulator-boot-on;
98 regulator-boot-on;
106 regulator-boot-on;
111 regulator-boot-on;
[all …]
Daxm5516-cpus.dtsi2 * arch/arm/boot/dts/axm5516-cpus.dtsi
81 cpu-release-addr = <0>; // Fixed by the boot loader
89 cpu-release-addr = <0>; // Fixed by the boot loader
97 cpu-release-addr = <0>; // Fixed by the boot loader
105 cpu-release-addr = <0>; // Fixed by the boot loader
113 cpu-release-addr = <0>; // Fixed by the boot loader
121 cpu-release-addr = <0>; // Fixed by the boot loader
129 cpu-release-addr = <0>; // Fixed by the boot loader
137 cpu-release-addr = <0>; // Fixed by the boot loader
145 cpu-release-addr = <0>; // Fixed by the boot loader
[all …]
Dpxa910-dkb.dts48 regulator-boot-on;
54 regulator-boot-on;
60 regulator-boot-on;
66 regulator-boot-on;
72 regulator-boot-on;
78 regulator-boot-on;
89 regulator-boot-on;
95 regulator-boot-on;
101 regulator-boot-on;
107 regulator-boot-on;
[all …]
Dtegra114-tn7.dts90 regulator-boot-on;
98 regulator-boot-on;
106 regulator-boot-on;
114 regulator-boot-on;
122 regulator-boot-on;
130 regulator-boot-on;
138 regulator-boot-on;
146 regulator-boot-on;
154 regulator-boot-on;
162 regulator-boot-on;
[all …]
Dexynos5250-arndale.dts210 regulator-boot-on;
219 regulator-boot-on;
228 regulator-boot-on;
245 regulator-boot-on;
254 regulator-boot-on;
263 regulator-boot-on;
272 regulator-boot-on;
288 regulator-boot-on;
297 regulator-boot-on;
306 regulator-boot-on;
[all …]
Drk3288-evb-rk808.dts90 regulator-boot-on;
101 regulator-boot-on;
113 regulator-boot-on;
122 regulator-boot-on;
134 regulator-boot-on;
146 regulator-boot-on;
157 regulator-boot-on;
169 regulator-boot-on;
181 regulator-boot-on;
193 regulator-boot-on;
[all …]
Dimx6sx-sdb-reva.dts29 regulator-boot-on;
37 regulator-boot-on;
45 regulator-boot-on;
52 regulator-boot-on;
59 regulator-boot-on;
76 regulator-boot-on;
81 regulator-boot-on;
Dimx6sx-sdb.dts44 regulator-boot-on;
52 regulator-boot-on;
59 regulator-boot-on;
66 regulator-boot-on;
78 regulator-boot-on;
83 regulator-boot-on;
Dexynos4412-odroid-common.dtsi253 regulator-boot-on;
261 regulator-boot-on;
302 regulator-boot-on;
310 regulator-boot-on;
318 regulator-boot-on;
326 regulator-boot-on;
334 regulator-boot-on;
341 regulator-boot-on;
349 regulator-boot-on;
357 regulator-boot-on;
[all …]
Dam335x-lxm.dts33 regulator-boot-on;
42 regulator-boot-on;
198 regulator-boot-on;
206 regulator-boot-on;
214 regulator-boot-on;
226 regulator-boot-on;
236 regulator-boot-on;
244 regulator-boot-on;
252 regulator-boot-on;
260 regulator-boot-on;
[all …]
Dsh73a0-kzm9g.dts57 regulator-boot-on;
66 regulator-boot-on;
231 regulator-boot-on;
238 regulator-boot-on;
245 regulator-boot-on;
252 regulator-boot-on;
259 regulator-boot-on;
266 regulator-boot-on;
273 regulator-boot-on;
280 regulator-boot-on;
[all …]
Dimx27-phytec-phycore-som.dtsi106 regulator-boot-on;
114 regulator-boot-on;
121 regulator-boot-on;
126 regulator-boot-on;
133 regulator-boot-on;
138 regulator-boot-on;
145 regulator-boot-on;
157 regulator-boot-on;
164 regulator-boot-on;
Dpicoxcell-pc7302-pc3x2.dts54 boot@100000 {
59 redundant-boot@200000 {
64 boot-env@300000 {
69 redundant-boot-env@320000 {
Ddra7-evm.dts65 regulator-boot-on;
424 regulator-boot-on;
433 regulator-boot-on;
442 regulator-boot-on;
451 regulator-boot-on;
460 regulator-boot-on;
469 regulator-boot-on;
478 regulator-boot-on;
488 regulator-boot-on;
497 regulator-boot-on;
[all …]
Drk3288-popmetal.dts131 regulator-boot-on;
245 regulator-boot-on;
256 regulator-boot-on;
268 regulator-boot-on;
277 regulator-boot-on;
289 regulator-boot-on;
301 regulator-boot-on;
312 regulator-boot-on;
324 regulator-boot-on;
343 regulator-boot-on;
[all …]
Dpicoxcell-pc7302-pc3x3.dts60 boot@100000 {
65 redundant-boot@200000 {
70 boot-env@300000 {
75 redundant-boot-env@320000 {
Darmada-xp-synology-ds414.dts49 * were delivered with an older version of u-boot that left internal
51 * not be able to directly boot a kernel based on this Device Tree. In
54 * installing it from u-boot prompt) or adjust the Devive Tree
126 * Synology u-boot uses its compiled-in environment
127 * and it seems Synology did not care to change u-boot
130 * if you do a 'saveenv' under u-boot, your modified
137 partition@00000000 { /* u-boot */
182 * Warning: the device may not boot with a 3.3V
254 regulator-boot-on;
267 regulator-boot-on;
[all …]
Dexynos5422-odroidxu3-common.dtsi237 regulator-boot-on;
245 regulator-boot-on;
253 regulator-boot-on;
261 regulator-boot-on;
269 regulator-boot-on;
277 regulator-boot-on;
285 regulator-boot-on;
293 regulator-boot-on;
301 regulator-boot-on;
309 regulator-boot-on;
Dexynos5420-smdk5420.dts268 regulator-boot-on;
276 regulator-boot-on;
284 regulator-boot-on;
292 regulator-boot-on;
300 regulator-boot-on;
308 regulator-boot-on;
316 regulator-boot-on;
324 regulator-boot-on;
332 regulator-boot-on;
340 regulator-boot-on;
Domap5-board-common.dtsi409 regulator-boot-on;
418 regulator-boot-on;
427 regulator-boot-on;
436 regulator-boot-on;
445 regulator-boot-on;
462 regulator-boot-on;
493 regulator-boot-on;
511 regulator-boot-on;
520 regulator-boot-on;
537 regulator-boot-on;
[all …]
Domap5-cm-t54.dts448 regulator-boot-on;
457 regulator-boot-on;
466 regulator-boot-on;
475 regulator-boot-on;
484 regulator-boot-on;
494 regulator-boot-on;
503 regulator-boot-on;
534 regulator-boot-on;
550 regulator-boot-on;
559 regulator-boot-on;
[all …]
Dimx6q-dmo-edmqmx6.dts57 regulator-boot-on;
153 regulator-boot-on;
160 regulator-boot-on;
167 regulator-boot-on;
174 regulator-boot-on;
181 regulator-boot-on;
200 regulator-boot-on;
205 regulator-boot-on;
222 regulator-boot-on;
Dtegra30-cardhu-a04.dts30 regulator-boot-on;
42 regulator-boot-on;
88 regulator-boot-on;
100 regulator-boot-on;
Dam437x-idk-evm.dts27 regulator-boot-on;
36 regulator-boot-on;
46 regulator-boot-on;
56 regulator-boot-on;
66 regulator-boot-on;
76 regulator-boot-on;
86 regulator-boot-on;
96 regulator-boot-on;
279 regulator-boot-on;
351 * valid file to boot(XIP).
Ddra72-evm.dts330 regulator-boot-on;
338 regulator-boot-on;
347 regulator-boot-on;
357 regulator-boot-on;
365 regulator-boot-on;
375 regulator-boot-on;
390 regulator-boot-on;
400 regulator-boot-on;
408 regulator-boot-on;
545 label = "NAND.u-boot-spl-os";
[all …]
Dtegra124-nyan.dtsi169 regulator-boot-on;
180 regulator-boot-on;
189 regulator-boot-on;
197 regulator-boot-on;
219 regulator-boot-on;
227 regulator-boot-on;
242 regulator-boot-on;
250 regulator-boot-on;
536 regulator-boot-on;
546 regulator-boot-on;
[all …]
Dda850-evm.dts144 regulator-boot-on;
188 regulator-boot-on;
196 regulator-boot-on;
205 regulator-boot-on;
214 regulator-boot-on;
222 regulator-boot-on;
Dam335x-nano.dts177 linux,rs485-enabled-at-boot-time;
187 linux,rs485-enabled-at-boot-time;
311 label = "boot";
386 regulator-boot-on;
395 regulator-boot-on;
404 regulator-boot-on;
412 regulator-boot-on;
420 regulator-boot-on;
428 regulator-boot-on;
436 regulator-boot-on;
Dlogicpd-torpedo-som.dtsi63 …/* u-boot uses mtdparts=omap2-nand.0:512k(x-loader),1920k(u-boot),128k(u-boot-env),4m(kernel),-(fs…
71 label = "u-boot";
76 label = "u-boot-env";
Dkirkwood-t5325.dts98 label = "u-boot";
108 label = "u-boot env";
113 label = "permanent u-boot env";
118 label = "permanent u-boot env";
164 regulator-boot-on;
Dkirkwood-b3.dts11 * Note: This requires a new'ish version of u-boot, which disables the
12 * L2 cache. If your B3 silently fails to boot, u-boot is probably too
84 label = "u-boot";
89 label = "u-boot env";
Dam335x-chilisom.dtsi145 regulator-boot-on;
154 regulator-boot-on;
160 regulator-boot-on;
166 regulator-boot-on;
172 regulator-boot-on;
178 regulator-boot-on;
Dam57xx-beagle-x15.dts54 regulator-boot-on;
425 regulator-boot-on;
434 regulator-boot-on;
443 regulator-boot-on;
452 regulator-boot-on;
463 regulator-boot-on;
473 regulator-boot-on;
483 regulator-boot-on;
492 regulator-boot-on;
501 regulator-boot-on;
[all …]
Dkirkwood-laplug.dts106 regulator-boot-on;
118 regulator-boot-on;
130 regulator-boot-on;
141 label = "u-boot";
Dkirkwood-net5big.dts42 regulator-boot-on;
54 regulator-boot-on;
66 regulator-boot-on;
78 regulator-boot-on;
Daks-cdu.dts33 linux,rs485-enabled-at-boot-time;
39 linux,rs485-enabled-at-boot-time;
45 linux,rs485-enabled-at-boot-time;
Dtegra114-roth.dts799 regulator-boot-on;
827 regulator-boot-on;
834 regulator-boot-on;
842 regulator-boot-on;
850 regulator-boot-on;
865 regulator-boot-on;
873 regulator-boot-on;
881 regulator-boot-on;
889 regulator-boot-on;
915 regulator-boot-on;
[all …]
Dkirkwood-synology.dtsi625 regulator-boot-on;
638 regulator-boot-on;
660 regulator-boot-on;
682 regulator-boot-on;
695 regulator-boot-on;
718 regulator-boot-on;
731 regulator-boot-on;
744 regulator-boot-on;
757 regulator-boot-on;
779 regulator-boot-on;
[all …]
Drk3288-veyron.dtsi119 regulator-boot-on;
128 regulator-boot-on;
137 regulator-boot-on;
200 regulator-boot-on;
212 regulator-boot-on;
225 regulator-boot-on;
241 regulator-boot-on;
260 regulator-boot-on;
272 regulator-boot-on;
284 regulator-boot-on;
[all …]
Dtegra30-cardhu-a02.dts30 regulator-boot-on;
42 regulator-boot-on;
88 regulator-boot-on;
Dimx6sl-evk.dts75 regulator-boot-on;
84 regulator-boot-on;
157 regulator-boot-on;
165 regulator-boot-on;
173 regulator-boot-on;
180 regulator-boot-on;
187 regulator-boot-on;
204 regulator-boot-on;
209 regulator-boot-on;
Darmada-370-synology-ds213j.dts49 * were delivered with an older version of u-boot that left internal
51 * not be able to directly boot a kernel based on this Device Tree. In
54 * installing it from u-boot prompt) or adjust the Devive Tree
103 * Synology u-boot uses its compiled-in environment
104 * and it seems Synology did not care to change u-boot
107 * if you do a 'saveenv' under u-boot, your modified
114 partition@00000000 { /* u-boot */
260 regulator-boot-on;
273 regulator-boot-on;
Dge863-pro3.dtsi41 boot@0 {
42 label = "boot";
Dimx6q-gw5400-a.dts224 regulator-boot-on;
232 regulator-boot-on;
240 regulator-boot-on;
247 regulator-boot-on;
254 regulator-boot-on;
271 regulator-boot-on;
276 regulator-boot-on;
Dexynos4412-origen.dts140 regulator-boot-on;
365 regulator-boot-on;
374 regulator-boot-on;
383 regulator-boot-on;
392 regulator-boot-on;
401 regulator-boot-on;
410 regulator-boot-on;
419 regulator-boot-on;
Dtegra114-dalmore.dts806 regulator-boot-on;
838 regulator-boot-on;
844 regulator-boot-on;
850 regulator-boot-on;
872 regulator-boot-on;
882 regulator-boot-on;
888 regulator-boot-on;
935 regulator-boot-on;
943 regulator-boot-on;
951 regulator-boot-on;
[all …]
Dtegra20-iris-512.dts86 regulator-boot-on;
97 regulator-boot-on;
Dtegra124-venice2.dts55 pinctrl-names = "boot";
701 regulator-boot-on;
712 regulator-boot-on;
721 regulator-boot-on;
729 regulator-boot-on;
742 regulator-boot-on;
752 regulator-boot-on;
760 regulator-boot-on;
775 regulator-boot-on;
783 regulator-boot-on;
[all …]
Dimx6qdl-gw54xx.dtsi221 regulator-boot-on;
229 regulator-boot-on;
237 regulator-boot-on;
244 regulator-boot-on;
251 regulator-boot-on;
268 regulator-boot-on;
273 regulator-boot-on;
Dimx6qdl-sabresd.dtsi223 regulator-boot-on;
231 regulator-boot-on;
239 regulator-boot-on;
246 regulator-boot-on;
253 regulator-boot-on;
270 regulator-boot-on;
275 regulator-boot-on;
Darmada-370-seagate-personal-cloud.dtsi85 label = "u-boot";
109 regulator-boot-on;
120 regulator-boot-on;
Dorion5x-lacie-d2-network.dts78 regulator-boot-on;
90 regulator-boot-on;
108 * least three partitions: 'u-boot code', 'u-boot environment'
Dimx6qdl-sabreauto.dtsi185 regulator-boot-on;
193 regulator-boot-on;
201 regulator-boot-on;
208 regulator-boot-on;
215 regulator-boot-on;
232 regulator-boot-on;
237 regulator-boot-on;
Dimx51-babbage.dts201 regulator-boot-on;
208 regulator-boot-on;
215 regulator-boot-on;
222 regulator-boot-on;
229 regulator-boot-on;
236 regulator-boot-on;
247 regulator-boot-on;
Dkirkwood-topkick.dts167 regulator-boot-on;
177 label = "u-boot";
182 label = "u-boot env";
Dimx27-pdk.dts57 regulator-boot-on;
67 regulator-boot-on;
72 regulator-boot-on;
Dam43x-epos-evm.dts40 regulator-boot-on;
428 regulator-boot-on;
437 regulator-boot-on;
446 regulator-boot-on;
455 regulator-boot-on;
477 regulator-boot-on;
615 label = "NAND.u-boot-spl-os";
619 label = "NAND.u-boot";
623 label = "NAND.u-boot-env";
627 label = "NAND.u-boot-env.backup1";
[all …]
Dkirkwood-sheevaplug-common.dtsi67 regulator-boot-on;
77 label = "u-boot";
Dkirkwood-dockstar.dts69 regulator-boot-on;
79 label = "u-boot";
Dexynos5250-spring.dts274 regulator-boot-on;
283 regulator-boot-on;
292 regulator-boot-on;
300 regulator-boot-on;
309 regulator-boot-on;
318 regulator-boot-on;
327 regulator-boot-on;
Dexynos5250-smdk5250.dts244 regulator-boot-on;
252 regulator-boot-on;
260 regulator-boot-on;
268 regulator-boot-on;
276 regulator-boot-on;
Dkirkwood-dreamplug.dts52 label = "u-boot";
57 label = "u-boot env";
Domap3-igep0030-rev-g.dts54 boot {
55 label = "omap3:green:boot";
Dam335x-igep0033.dtsi45 regulator-boot-on;
170 label = "U-boot";
270 regulator-boot-on;
279 regulator-boot-on;
/linux-4.4.14/arch/avr32/
DMakefile31 head-$(CONFIG_LOADER_U_BOOT) += arch/avr32/boot/u-boot/head.o
40 core-$(CONFIG_LOADER_U_BOOT) += arch/avr32/boot/u-boot/
50 boot := arch/$(ARCH)/boot/images macro
52 KBUILD_IMAGE := $(boot)/uImage
53 vmlinux.elf: KBUILD_IMAGE := $(boot)/vmlinux.elf
54 vmlinux.cso: KBUILD_IMAGE := $(boot)/vmlinux.cso
55 uImage.srec: KBUILD_IMAGE := $(boot)/uImage.srec
56 uImage: KBUILD_IMAGE := $(boot)/uImage
64 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
67 $(Q)$(MAKE) $(build)=$(boot) BOOTIMAGE=$(KBUILD_IMAGE) $@
[all …]
/linux-4.4.14/arch/arm64/
DMakefile82 boot := arch/arm64/boot macro
85 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
88 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
91 $(Q)$(MAKE) $(build)=$(boot) $@
94 $(Q)$(MAKE) $(build)=$(boot)/dts $(boot)/dts/$@
99 $(Q)$(MAKE) $(build)=$(boot)/dts
102 $(Q)$(MAKE) $(dtbinst)=$(boot)/dts
110 $(Q)$(MAKE) $(clean)=$(boot)
111 $(Q)$(MAKE) $(clean)=$(boot)/dts
/linux-4.4.14/arch/alpha/
DMakefile50 boot := arch/alpha/boot macro
53 all boot: $(boot)/vmlinux.gz target
55 $(boot)/vmlinux.gz: vmlinux
56 $(Q)$(MAKE) $(build)=$(boot) $@
59 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
62 $(Q)$(MAKE) $(clean)=$(boot)
/linux-4.4.14/arch/cris/
DMakefile44 core-$(CONFIG_OF) += arch/cris/boot/dts/
77 boot := arch/cris/boot macro
83 $(Q)$(MAKE) $(build)=$(boot) MACHINE=$(MACHINE) $(boot)/$@
88 $(Q)if [ -e arch/cris/boot ]; then \
89 $(MAKE) $(clean)=arch/cris/boot; \
93 $(boot)/zImage \
94 $(boot)/compressed/decompress.bin \
95 $(boot)/compressed/piggy.gz \
96 $(boot)/rescue/rescue.bin
/linux-4.4.14/arch/c6x/
DMakefile37 boot := arch/$(ARCH)/boot macro
44 core-y += $(boot)/dts/
50 $(Q)$(MAKE) $(build)=$(boot) $(patsubst %,$(boot)/%,$@)
53 $(Q)$(MAKE) $(build)=$(boot) $(patsubst %,$(boot)/%,$@)
56 $(Q)$(MAKE) $(clean)=$(boot)
/linux-4.4.14/arch/metag/
DMakefile45 core-y += arch/metag/boot/dts/
54 boot := arch/metag/boot macro
69 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
72 $(Q)$(MAKE) $(build)=$(boot)/dts $(boot)/dts/$@
75 $(Q)$(MAKE) $(build)=$(boot)/dts
78 $(Q)$(MAKE) $(clean)=$(boot)
/linux-4.4.14/Documentation/arm/
DBooting9 In order to boot ARM Linux, you require a boot loader, which is a small
10 program that runs before the main kernel. The boot loader is expected
14 Essentially, the boot loader should provide (as a minimum) the
28 Existing boot loaders: MANDATORY
29 New boot loaders: MANDATORY
31 The boot loader is expected to find and initialise all RAM that the
35 the RAM in the machine, or any other method the boot loader designer
42 Existing boot loaders: OPTIONAL, RECOMMENDED
43 New boot loaders: OPTIONAL, RECOMMENDED
45 The boot loader should initialise and enable one serial port on the
[all …]
/linux-4.4.14/Documentation/arm/Samsung/
DBootloader-interface.txt1 Interface between kernel and boot loaders on Exynos boards
8 and boot loaders on Samsung Exynos based boards. This is not a definition
12 In the document "boot loader" means any of following: U-boot, proprietary
24 0x1c exynos4_secondary_startup Secondary CPU boot
25 0x1c + 4*cpu exynos4_secondary_startup (Exynos4412) Secondary CPU boot
36 0x00 exynos4_secondary_startup Secondary CPU boot
37 0x04 exynos4_secondary_startup (Exynos542x) Secondary CPU boot
38 4*cpu exynos4_secondary_startup (Exynos4412) Secondary CPU boot
49 0x0814 exynos4_secondary_startup (Exynos4210 r1.1) Secondary CPU boot
59 0x0908 Non-zero Secondary CPU boot up indicator
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Dpfuze100.txt32 regulator-boot-on;
40 regulator-boot-on;
47 regulator-boot-on;
54 regulator-boot-on;
61 regulator-boot-on;
78 regulator-boot-on;
83 regulator-boot-on;
133 regulator-boot-on;
141 regulator-boot-on;
148 regulator-boot-on;
[all …]
Dtps65090.txt54 regulator-boot-on;
62 regulator-boot-on;
68 regulator-boot-on;
74 regulator-boot-on;
80 regulator-boot-on;
86 regulator-boot-on;
92 regulator-boot-on;
98 regulator-boot-on;
104 regulator-boot-on;
110 regulator-boot-on;
[all …]
Dtps65217.txt32 regulator-boot-on;
39 regulator-boot-on;
46 regulator-boot-on;
53 regulator-boot-on;
60 regulator-boot-on;
67 regulator-boot-on;
74 regulator-boot-on;
Dltc3589.txt41 regulator-boot-on;
50 regulator-boot-on;
59 regulator-boot-on;
67 regulator-boot-on;
75 regulator-boot-on;
84 regulator-boot-on;
91 regulator-boot-on;
Dlp872x.txt73 regulator-boot-on;
79 regulator-boot-on;
122 regulator-boot-on;
128 regulator-boot-on;
149 regulator-boot-on;
158 regulator-boot-on;
D88pm860x.txt20 regulator-boot-on;
26 regulator-boot-on;
Dtps6586x.txt59 regulator-boot-on;
66 regulator-boot-on;
73 regulator-boot-on;
80 regulator-boot-on;
D88pm800.txt27 regulator-boot-on;
33 regulator-boot-on;
/linux-4.4.14/Documentation/
Defi-stub.txt8 jumps to are collectively known as the "EFI boot stub", and live in
9 arch/x86/boot/header.S and arch/x86/boot/compressed/eboot.c,
11 arch/arm/boot/compressed/efi-header.S and
12 arch/arm/boot/compressed/efi-stub.c. EFI stub code that is shared
20 By using the EFI boot stub it's possible to boot a Linux kernel
21 without the use of a conventional EFI boot loader, such as grub or
22 elilo. Since the EFI boot stub performs the jobs of a boot loader, in
23 a certain sense it *IS* the boot loader.
25 The EFI boot stub is enabled with the CONFIG_EFI_STUB kernel option.
30 The bzImage located in arch/x86/boot/bzImage must be copied to the EFI
[all …]
Dbasic_profiling.txt10 /sbin/installkernel to copy vmlinux to /boot, in addition to vmlinuz,
26 dump output readprofile -m /boot/System.map > captured_profile
45 opcontrol --setup --vmlinux=/boot/vmlinux
53 To only report on the kernel, run opreport -l /boot/vmlinux > output_file
Dinitrd.txt8 initrd provides the capability to load a RAM disk by the boot loader.
19 discussion of the boot process can be found in [1].
27 1) the boot loader loads the kernel and the initial RAM disk
42 the usual boot sequence
76 initrd is mounted as root, and the normal boot procedure is followed,
88 find . | cpio --quiet -H newc -o | gzip -9 -n > /boot/imagefile.img
94 gzip -cd /boot/imagefile.img | cpio -imd --quiet
107 If the root file system is created during the boot procedure (i.e. if
165 Finally, you have to boot the kernel and load initrd. Almost all Linux
166 boot loaders support initrd. Since the boot process is still compatible
[all …]
Ddynamic-debug-howto.txt233 the boot process, even before userspace and debugfs exists, use
241 messages in all code run after this arch_initcall via this boot
249 this boot parameter for debugging purposes.
252 boot time, without effect, but will be reprocessed when module is
254 boot.
269 2. # foo.dyndbg as given in boot args, "foo." is stripped and passed
276 This allows boot args to override or modify those from /etc/modprobe.d
277 (sensible, since 1 is system wide, 2 is kernel or boot specific), and
291 For CONFIG_DYNAMIC_DEBUG kernels, any settings given at boot-time (or
333 // boot-args example, with newlines and comments for readability
/linux-4.4.14/arch/mn10300/
DMakefile68 boot := arch/mn10300/boot macro
72 KBUILD_IMAGE := $(boot)/zImage
73 CLEAN_FILES += $(boot)/zImage
74 CLEAN_FILES += $(boot)/compressed/vmlinux
75 CLEAN_FILES += $(boot)/compressed/vmlinux.bin
76 CLEAN_FILES += $(boot)/compressed/vmlinux.bin.gz
79 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dst-fsm.txt11 - st,syscfg : Phandle to boot-device system configuration registers
12 - st,boot-device-reg : Address of the aforementioned boot-device register(s)
13 - st,boot-device-spi : Expected boot-device value if booted via this device
22 st,boot-device-reg = <0x958>;
23 st,boot-device-spi = <0x1a>;
/linux-4.4.14/arch/arc/
DMakefile97 core-y += arch/arc/boot/dts/
107 boot := arch/arc/boot macro
118 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
121 $(Q)$(MAKE) $(build)=$(boot)/dts $(boot)/dts/$@
124 $(Q)$(MAKE) $(build)=$(boot)/dts
127 $(Q)$(MAKE) $(clean)=$(boot)
/linux-4.4.14/arch/sparc/
DMakefile63 boot := arch/sparc/boot macro
69 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
72 $(Q)$(MAKE) $(build)=$(boot) $@
75 $(Q)$(MAKE) $(clean)=$(boot)
78 KBUILD_IMAGE := $(boot)/zImage
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Drk808.txt79 regulator-boot-on;
87 regulator-boot-on;
95 regulator-boot-on;
101 regulator-boot-on;
109 regulator-boot-on;
117 regulator-boot-on;
125 regulator-boot-on;
133 regulator-boot-on;
141 regulator-boot-on;
149 regulator-boot-on;
[all …]
Dtps6507x.txt53 regulator-boot-on;
61 regulator-boot-on;
70 regulator-boot-on;
79 regulator-boot-on;
87 regulator-boot-on;
Dmax8925.txt42 regulator-boot-on;
49 regulator-boot-on;
Dtps65910.txt110 regulator-boot-on;
119 regulator-boot-on;
128 regulator-boot-on;
137 regulator-boot-on;
189 regulator-boot-on;
/linux-4.4.14/arch/score/
DMakefile32 boot := arch/score/boot macro
35 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
38 @$(MAKE) $(clean)=$(boot)
/linux-4.4.14/arch/m32r/
DMakefile41 arch/m32r/boot/ \
46 boot := arch/m32r/boot macro
53 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
58 $(Q)$(MAKE) $(clean)=$(boot)
/linux-4.4.14/arch/s390/
DMakefile50 KBUILD_IMAGE :=arch/s390/boot/image
108 boot := arch/s390/boot macro
113 $(Q)$(MAKE) $(build)=$(boot) $@
116 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
119 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
126 $(Q)$(MAKE) $(clean)=$(boot)
/linux-4.4.14/Documentation/x86/
Dearly-microcode.txt5 Kernel can update microcode in early phase of boot time. Loading microcode early
6 can fix CPU issues before they are observed during kernel boot time.
9 file and loaded to CPUs during boot time.
13 during boot time. The microcode file in cpio name space is:
17 During BSP boot (before SMP starts), if the kernel finds the microcode file in
33 /boot/initrd-3.5.0.ucode.img with original microcode microcode.bin and
34 original initrd image /boot/initrd-3.5.0.img.
42 cat ucode.cpio /boot/initrd-3.5.0.img >/boot/initrd-3.5.0.ucode.img
Dboot.txt4 On the x86 platform, the Linux kernel uses a rather complicated boot
11 Currently, the following versions of the Linux/x86 boot protocol exist.
18 boot loader and the kernel. setup.S made relocatable,
40 the boot command line.
42 Protocol 2.07: (Kernel 2.6.24) Added paravirtualised boot protocol.
55 pref_address fields. Added extended boot loader IDs.
78 | Kernel boot sector | The kernel legacy boot sector.
93 0x100000 ("high memory"), and the kernel real-mode block (boot sector,
100 low memory touched by the boot loader -- as low as possible, since
103 memory. The boot loader should use the "INT 12h" BIOS call to verify
[all …]
D00-INDEX3 boot.txt
4 - List of boot protocol versions
/linux-4.4.14/arch/xtensa/
DMakefile89 core-$(CONFIG_OF) += arch/xtensa/boot/dts/
92 boot := arch/xtensa/boot macro
99 $(Q)$(MAKE) $(build)=$(boot) $@
102 $(Q)$(MAKE) $(build)=$(boot)/dts $(boot)/dts/$@
105 $(Q)$(MAKE) $(build)=$(boot)/dts
DKconfig.debug27 bool "Perform S32C1I instruction self-test at boot"
30 Enable this option to test S32C1I instruction behavior at boot.
/linux-4.4.14/Documentation/powerpc/
Dbootwrapper.txt1 The PowerPC boot wrapper
6 a boot wrapper to make it usable by the system firmware. There is no
7 standard PowerPC firmware interface, so the boot wrapper is designed to
10 The boot wrapper can be found in the arch/powerpc/boot/ directory. The
19 The boot wrapper is built from the makefile in arch/powerpc/boot/Makefile and
20 it uses the wrapper script (arch/powerpc/boot/wrapper) to generate target
27 the image. The boot wrapper, kernel and device tree
29 with boot wrapper code that extracts data from the old
39 arch/powerpc/boot/cuboot.*.c. Selection of the correct
55 file named arch/powerpc/boot/<platform>.c; but this
[all …]
Dfirmware-assisted-dump.txt22 - Once enabled through kernel boot parameter, fadump can be
46 kernel during early boot.
49 the low memory (boot memory of size larger of 5% of system RAM
53 NOTE: The term 'boot memory' means size of the low memory chunk
54 that is required for a kernel to boot successfully when
55 booted with restricted memory. By default, the boot memory
57 Alternatively, user can also specify boot memory size
58 through boot parameter 'fadump_reserve_mem=' which will
60 if default boot memory size is not sufficient for second
61 kernel to boot successfully.
[all …]
Dmpc52xx.txt14 then, on U-boot:
23 # cp your_initrd.gz arch/ppc/boot/images/ramdisk.image.gz
/linux-4.4.14/arch/mips/
DMakefile299 boot-y := vmlinux.bin
300 boot-y += vmlinux.ecoff
301 boot-y += vmlinux.srec
303 boot-y += uImage
304 boot-y += uImage.bin
305 boot-y += uImage.bz2
306 boot-y += uImage.gz
307 boot-y += uImage.lzma
308 boot-y += uImage.lzo
345 $(boot-y): $(vmlinux-32) FORCE
[all …]
/linux-4.4.14/arch/arm64/kernel/
Dcpufeature.c448 static int check_update_ftr_reg(u32 sys_id, int cpu, u64 val, u64 boot) in check_update_ftr_reg() argument
454 if ((boot & regp->strict_mask) == (val & regp->strict_mask)) in check_update_ftr_reg()
457 regp->name, boot, cpu, val); in check_update_ftr_reg()
468 struct cpuinfo_arm64 *boot) in update_cpu_features() argument
478 info->reg_ctr, boot->reg_ctr); in update_cpu_features()
486 info->reg_dczid, boot->reg_dczid); in update_cpu_features()
490 info->reg_cntfrq, boot->reg_cntfrq); in update_cpu_features()
499 info->reg_id_aa64dfr0, boot->reg_id_aa64dfr0); in update_cpu_features()
501 info->reg_id_aa64dfr1, boot->reg_id_aa64dfr1); in update_cpu_features()
507 info->reg_id_aa64isar0, boot->reg_id_aa64isar0); in update_cpu_features()
[all …]
/linux-4.4.14/drivers/pnp/pnpbios/
Dbioscalls.c289 static int __pnp_bios_get_dev_node(u8 *nodenum, char boot, in __pnp_bios_get_dev_node() argument
297 if (!boot && pnpbios_dont_use_current_config) in __pnp_bios_get_dev_node()
301 boot ? 2 : 1, PNP_DS, 0, &tmp_nodenum, in __pnp_bios_get_dev_node()
307 int pnp_bios_get_dev_node(u8 *nodenum, char boot, struct pnp_bios_node *data) in pnp_bios_get_dev_node() argument
311 status = __pnp_bios_get_dev_node(nodenum, boot, data); in pnp_bios_get_dev_node()
323 static int __pnp_bios_set_dev_node(u8 nodenum, char boot, in __pnp_bios_set_dev_node() argument
330 if (!boot && pnpbios_dont_use_current_config) in __pnp_bios_set_dev_node()
333 boot ? 2 : 1, PNP_DS, 0, 0, data, 65536, NULL, in __pnp_bios_set_dev_node()
338 int pnp_bios_set_dev_node(u8 nodenum, char boot, struct pnp_bios_node *data) in pnp_bios_set_dev_node() argument
342 status = __pnp_bios_set_dev_node(nodenum, boot, data); in pnp_bios_set_dev_node()
[all …]
Dproc.c221 int boot = (long)data >> 8; in pnpbios_proc_show() local
228 if (pnp_bios_get_dev_node(&nodenum, boot, node)) { in pnpbios_proc_show()
248 int boot = (long)data >> 8; in pnpbios_proc_write() local
255 if (pnp_bios_get_dev_node(&nodenum, boot, node)) { in pnpbios_proc_write()
267 if (pnp_bios_set_dev_node(node->handle, boot, node) != 0) { in pnpbios_proc_write()
/linux-4.4.14/include/linux/sunrpc/
Dcache.h165 struct timespec boot; in seconds_since_boot() local
166 getboottime(&boot); in seconds_since_boot()
167 return get_seconds() - boot.tv_sec; in seconds_since_boot()
172 struct timespec boot; in convert_to_wallclock() local
173 getboottime(&boot); in convert_to_wallclock()
174 return boot.tv_sec + sinceboot; in convert_to_wallclock()
299 struct timespec boot; in get_expiry() local
305 getboottime(&boot); in get_expiry()
306 return rv - boot.tv_sec; in get_expiry()
/linux-4.4.14/Documentation/mmc/
Dmmc-dev-parts.txt7 As of this writing, MMC boot partitions as supported and exposed as
14 Read and write access is provided to the two MMC boot partitions. Due to
15 the sensitive nature of the boot partition contents, which often store
29 The boot partitions can also be locked read only until the next power on,
35 not support boot partition locking, the file will not exist. If the
38 The boot partitions can also be locked permanently, but this feature is
/linux-4.4.14/arch/xtensa/boot/boot-elf/
DMakefile17 boot-y := bootstrap.o
19 OBJS := $(addprefix $(obj)/,$(boot-y))
27 $(obj)/../Image.elf: $(obj)/Image.o $(obj)/boot.lds
29 -T $(obj)/boot.lds \
D.gitignore1 boot.lds
/linux-4.4.14/arch/ia64/
DMakefile64 boot := arch/ia64/hp/sim/boot macro
66 PHONY += boot compressed check
75 $(Q)$(MAKE) $(build)=$(boot) $@
81 $(Q)$(MAKE) $(clean)=$(boot)
85 boot: lib/lib.a vmlinux target
86 $(Q)$(MAKE) $(build)=$(boot) $@
/linux-4.4.14/arch/xtensa/boot/boot-redboot/
DMakefile13 LD_ARGS = -T $(srctree)/$(obj)/boot.ld
15 boot-y := bootstrap.o
17 OBJS := $(addprefix $(obj)/,$(boot-y))
18 LIBS := arch/xtensa/boot/lib/lib.a arch/xtensa/lib/lib.a
/linux-4.4.14/Documentation/ia64/
Dxen.txt38 # cp xen/xen.gz /boot/efi/efi/redhat/
40 /boot/efi/efi/redhat/vmlinuz-2.6.18.8-xen
45 # mkinitrd -f /boot/efi/efi/redhat/initrd-2.6.18.8-xen.img \
94 elilo of RHEL5 can boot Xen and Dom0.
97 and copy into /boot/efi/efi/redhat/
98 # cp elilo-3.6-ia64.efi /boot/efi/efi/redhat/elilo.efi
101 # vi /boot/efi/efi/redhat/elilo.conf
148 # cp vmlinux.gz /boot/efi/efi/redhat/vmlinuz-2.6-pv_ops-xenU
150 # mkinitrd -f /boot/efi/efi/redhat/initrd-2.6-pv_ops-xenU.img \
161 kernel = "/boot/efi/efi/redhat/vmlinuz-2.6-pv_ops-xenU"
[all …]
/linux-4.4.14/drivers/net/can/softing/
Dsofting_cs.c46 .boot = {0x0000, 0x000000, fw_dir "bcard.bin",},
58 .boot = {0x0000, 0x000000, fw_dir "bcard.bin",},
70 .boot = {0x0000, 0x000000, fw_dir "bcard.bin",},
82 .boot = {0x0000, 0x000000, fw_dir "bcard2.bin",},
94 .boot = {0x0000, 0x000000, fw_dir "bcard.bin",},
106 .boot = {0x0000, 0x000000, fw_dir "bcard.bin",},
118 .boot = {0x0000, 0x000000, fw_dir "bcard2.bin",},
130 .boot = {0x0000, 0x000000, fw_dir "bcard.bin",},
142 .boot = {0x0000, 0x000000, fw_dir "bcard2.bin",},
/linux-4.4.14/arch/x86/
DMakefile20 CODE16GCC_CFLAGS := -m32 -Wa,$(srctree)/arch/x86/boot/code16gcc.h
235 boot := arch/x86/boot macro
245 KBUILD_IMAGE := $(boot)/bzImage
251 $(Q)$(MAKE) $(build)=$(boot) $(KBUILD_IMAGE)
252 $(Q)mkdir -p $(objtree)/arch/$(UTS_MACHINE)/boot
253 $(Q)ln -fsn ../../x86/boot/bzImage $(objtree)/arch/$(UTS_MACHINE)/boot/$@
256 $(Q)$(MAKE) $(build)=$(boot) $@
260 $(Q)$(MAKE) $(build)=$(boot) $@
269 $(Q)$(MAKE) $(clean)=$(boot)
/linux-4.4.14/drivers/isdn/hardware/eicon/
Dos_pri.c336 struct mp_load __iomem *boot; in diva_pri_reset_adapter() local
347 boot = (struct mp_load __iomem *) DIVA_OS_MEM_ATTACH_ADDRESS(IoAdapter); in diva_pri_reset_adapter()
348 WRITE_DWORD(&boot->err, 0); in diva_pri_reset_adapter()
349 DIVA_OS_MEM_DETACH_ADDRESS(IoAdapter, boot); in diva_pri_reset_adapter()
355 boot = (struct mp_load __iomem *) DIVA_OS_MEM_ATTACH_ADDRESS(IoAdapter); in diva_pri_reset_adapter()
356 i = READ_DWORD(&boot->live); in diva_pri_reset_adapter()
359 if (i == READ_DWORD(&boot->live)) { in diva_pri_reset_adapter()
360 DIVA_OS_MEM_DETACH_ADDRESS(IoAdapter, boot); in diva_pri_reset_adapter()
365 if (READ_DWORD(&boot->err)) { in diva_pri_reset_adapter()
368 READ_DWORD(&boot->err))) in diva_pri_reset_adapter()
[all …]
/linux-4.4.14/arch/blackfin/
DMakefile140 $(Q)$(MAKE) $(clean)=$(boot)
143 boot := arch/$(ARCH)/boot macro
146 KBUILD_IMAGE := $(boot)/uImage
151 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
154 $(Q)$(MAKE) $(build)=$(boot) BOOTIMAGE=$(KBUILD_IMAGE) install
/linux-4.4.14/arch/arm/
DMakefile310 boot := arch/arm/boot macro
327 $(Q)$(MAKE) $(build)=$(boot) MACHINE=$(MACHINE) $(boot)/$@
330 $(Q)$(MAKE) $(build)=$(boot) MACHINE=$(MACHINE) $@
333 $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
338 $(Q)$(MAKE) $(build)=$(boot)/dts
341 $(Q)$(MAKE) $(dtbinst)=$(boot)/dts
351 $(Q)$(MAKE) $(clean)=$(boot)
354 bp:; $(Q)$(MAKE) $(build)=$(boot) MACHINE=$(MACHINE) $(boot)/bootpImage
355 i zi:; $(Q)$(MAKE) $(build)=$(boot) MACHINE=$(MACHINE) $@
/linux-4.4.14/arch/powerpc/
DMakefile249 boot := arch/$(ARCH)/boot macro
263 $(Q)$(MAKE) ARCH=ppc64 $(build)=$(boot) $(patsubst %,$(boot)/%,$@)
265 $(Q)$(MAKE) ARCH=ppc64 $(build)=$(boot) $(patsubst %,$(boot)/%,$@)
269 $(Q)$(MAKE) ARCH=ppc64 $(build)=$(boot) $(patsubst %,$(boot)/%,$@)
272 $(Q)$(MAKE) ARCH=ppc64 $(build)=$(boot) $(patsubst %,$(boot)/%,$@)
336 $(Q)$(MAKE) $(build)=$(boot) install
345 $(Q)$(MAKE) $(clean)=$(boot)
/linux-4.4.14/tools/testing/ktest/examples/include/
Dtests.conf33 TEST_START IF ${TEST} == boot
34 TEST_TYPE = boot
64 TEST_TYPE = boot
Ddefaults.conf63 BUILD_TARGET = arch/x86/boot/bzImage
64 TARGET_IMAGE = /boot/vmlinuz-test
/linux-4.4.14/arch/m32r/kernel/
Dvmlinux.lds.S16 kernel_entry = boot - 0x80000000;
29 .boot : { *(.boot) } = 0
/linux-4.4.14/security/apparmor/
DKconfig18 int "AppArmor boot parameter default value"
25 at boot. If this option is set to 0 (zero), the AppArmor
27 boot. If this option is set to 1 (one), the AppArmor
29 boot.
/linux-4.4.14/Documentation/zh_CN/
Dbasic_profiling.txt29 /sbin/installkernel将vmlinux拷贝到/boot目录，而System.map通常是默认安装好的
43 dump output readprofile -m /boot/System.map > captured_profile
60 opcontrol --setup --vmlinux=/boot/vmlinux
68 如果只看kernel相关的报告结果，请运行命令 opreport -l /boot/vmlinux > output_file
/linux-4.4.14/Documentation/acpi/
Ddebug.txt18 you're interested in. At boot-time, use the acpi.debug_layer and
19 acpi.debug_level kernel command line options. After boot, you can use the
30 You can set the debug_layer mask at boot-time using the acpi.debug_layer
31 command line argument, and you can change it after boot by writing values
78 You can set the debug_level mask at boot-time using the acpi.debug_level
79 command line argument, and you can change it after boot by writing values
130 AML) during boot:
142 Enable all ACPI_DB_INFO messages after boot:
Dinitrd_table_override.txt70 find kernel | cpio -H newc --create > /boot/instrumented_initrd
71 cat /boot/initrd >>/boot/instrumented_initrd
72 # reboot with increased acpi debug level, e.g. boot params:
/linux-4.4.14/Documentation/blockdev/
Dmflash.txt24 C. IO mode supports 4kB boot area, so host can boot from mflash.
27 If host boot from mflash, usually needs raw area for boot loader image. All of
29 Note that boot loader's size of reserved area and kernel configuration value
/linux-4.4.14/arch/powerpc/boot/dts/
Dmpc836x_rdk.dts45 /* filled by u-boot */
54 /* filled by u-boot */
66 /* filled by u-boot */
109 /* filled by u-boot */
119 /* filled by u-boot */
205 /* filled by u-boot */
279 /* filled by u-boot */
294 /* filled by u-boot */
309 /* filled by u-boot */
324 /* filled by u-boot */
[all …]
Damigaone.dts33 timebase-frequency = <0>; // 33.3 MHz, from U-boot
34 clock-frequency = <0>; // From U-boot
35 bus-frequency = <0>; // From U-boot
41 reg = <0 0>; // From U-boot
Da3m071.dts32 bus-frequency = <0>; /* From boot loader */
33 system-frequency = <0>; /* From boot loader */
109 label = "u-boot";
Dxpedite5200_xmon.dts6 * xMon boot loader memory map which differs from U-Boot's.
21 boot-bank = <0x0>;
52 reg = <0x0 0x0>; // Filled in by boot loader
109 * 4: Flash boot device indicator
385 0 0x0 0xf8000000 0x08000000 // NOR boot flash
391 nor-boot@0,0 {
428 label = "Alternate boot firmware";
504 /* Needed for dtbImage boot wrapper compatibility */
Dlite5200b.dts120 clock-frequency = <0>; // From boot loader
147 label = "u-boot";
151 label = "u-boot-env";
Da4m072.dts33 bus-frequency = <0>; /* From boot loader */
34 system-frequency = <0>; /* From boot loader */
144 clock-frequency = <0>; /* From boot loader */
Dmpc5121ads.dts60 u-boot@3f00000 {
61 label = "u-boot";
62 reg = <0x03f00000 0x00100000>; // 1M for u-boot
/linux-4.4.14/sound/drivers/vx/
Dvx_core.c422 int snd_vx_load_boot_image(struct vx_core *chip, const struct firmware *boot) in snd_vx_load_boot_image() argument
428 if (boot->size <= 0) in snd_vx_load_boot_image()
430 if (boot->size % 3) in snd_vx_load_boot_image()
435 unsigned int c = ((u32)boot->data[0] << 16) | ((u32)boot->data[1] << 8) | boot->data[2]; in snd_vx_load_boot_image()
436 if (boot->size != (c + 2) * 3) in snd_vx_load_boot_image()
448 if (i >= boot->size) { in snd_vx_load_boot_image()
459 const unsigned char *image = boot->data + i; in snd_vx_load_boot_image()
658 int snd_vx_dsp_boot(struct vx_core *chip, const struct firmware *boot) in snd_vx_dsp_boot() argument
666 if ((err = snd_vx_load_boot_image(chip, boot)) < 0) in snd_vx_dsp_boot()
/linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,bcm11351-cpu-method.txt10 - secondary-boot-reg = <...>;
12 The secondary-boot-reg property is a u32 value that specifies the
23 secondary-boot-reg = <0x3500417c>;
/linux-4.4.14/security/selinux/
DKconfig12 bool "NSA SELinux boot parameter"
17 to be disabled at boot. If this option is selected, SELinux
26 int "NSA SELinux boot parameter default value"
32 'selinux', which allows SELinux to be disabled at boot. If this
47 SELinux will then remain disabled until the next boot.
48 This option is similar to the selinux=0 boot parameter, but is to
50 portability across platforms where boot parameters are difficult
92 'checkreqprot=' boot parameter. It may also be changed at runtime
/linux-4.4.14/arch/xtensa/boot/dts/
Dxtfpga-flash-4m.dtsi11 label = "boot loader area";
15 label = "boot environment";
Dxtfpga-flash-128m.dtsi15 label = "boot loader area";
23 label = "boot environment";
Dxtfpga-flash-16m.dtsi11 label = "boot loader area";
23 label = "boot environment";
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfsroot.txt39 When the kernel has been loaded by a boot loader (see below) it needs to be
86 `nfsaddrs', but now the boot-time IP configuration works independently of
176 log at boot time so that administrators can verify that the correct
206 When building kernels, an easy way to create a boot floppy that uses
221 a floppy using dd, configure the boot device using rdev, and
222 boot using the resulting floppy. Linux no longer supports this
235 The resulting iso image will be arch/<ARCH>/boot/image.iso
240 cdrecord dev=ATAPI:1,0,0 arch/x86/boot/image.iso
262 loadlin may be used to boot Linux from a DOS command prompt without
270 3.5) Using a boot ROM
[all …]
/linux-4.4.14/tools/testing/selftests/rcutorture/bin/
Dfunctions.sh59 if test -r "$2.boot"
61 echo $1 `grep -v '^#' "$2.boot" | tr '\012' ' '`
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Drs485.txt16 - linux,rs485-enabled-at-boot-time: empty property telling to enable the rs485
17 feature at boot time. It can be disabled later with proper ioctl.
28 linux,rs485-enabled-at-boot-time;
/linux-4.4.14/arch/powerpc/boot/dts/fsl/
Dp1020rdb.dtsi74 /* 512KB for u-boot Bootloader Image */
75 /* 512KB for u-boot Environment Variables */
91 /* 1MB for u-boot Bootloader Image */
155 partition@u-boot {
156 /* 512KB for u-boot Bootloader Image */
158 label = "u-boot";
197 only in case of SPI and SD boot after
Dp1020rdb-pc.dtsi72 /* 512KB for u-boot Bootloader Image */
73 /* 512KB for u-boot Environment Variables */
89 /* 1MB for u-boot Bootloader Image */
158 partition@u-boot {
159 /* 512KB for u-boot Bootloader Image */
161 label = "u-boot";
Dmpc8536ds.dtsi78 label = "u-boot-nor";
92 label = "u-boot-nand";
148 partition@u-boot {
149 label = "u-boot";
Dp1021rdb-pc.dtsi80 /* 512KB for u-boot Bootloader Image */
81 /* 512KB for u-boot Environment Variables */
96 /* 1MB for u-boot Bootloader Image */
157 partition@u-boot {
158 /* 512KB for u-boot Bootloader Image */
Dp1024rdb.dtsi72 /* 512KB for u-boot Bootloader Image */
73 /* 512KB for u-boot Environment Variables */
89 /* 1MB for u-boot Bootloader Image */
137 /* 512KB for u-boot Bootloader Image */
Dp2020rdb.dts78 /* 512KB for u-boot Bootloader Image */
79 /* 512KB for u-boot Environment Variables */
95 /* 1MB for u-boot Bootloader Image */
163 /* 512KB for u-boot Bootloader Image */
/linux-4.4.14/Documentation/sound/oss/
Dmwave20 mkdir /dos95/linux/boot
21 mkdir /dos95/linux/boot/parms
23 Copy the kernel, any initrd image, and loadlin to /dos95/linux/boot/.
87 c:\linux\boot\loadlin.exe @c:\linux\boot\parms\%CONFIG%.par
109 Now build a file in c:\linux\boot\parms for each Linux config that you have.
112 initrd image, and has a parameter file named LINDOC3.PAR in c:\linux\boot\parms:
119 c:\linux\boot\zImage.krn # First value must be filename of Linux kernel.
DAudioExcelDSP1672 For all the non-supported audio cards, you have to boot MS-DOS (or WIN95)
74 <ctrl>-<alt>-<del> and boot Linux.
80 2) Install your new kernel as the default boot kernel.
81 3) Boot MS-DOS and configure the audio card with the boot time device
83 4) <ctrl>-<alt>-<del> and boot Linux. This will maintain the DOS configuration
84 and will boot the new kernel with sound driver. The sound driver will find
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-profiling6 of the boot-time profile= option.
12 as you would by issuing profile=2 on the boot
Dsysfs-class-mic.txt44 "ready" - The MIC device is ready to boot the card OS. On
45 reading this entry after an OSPM resume, a "boot" has to be
49 "online" - The MIC device has completed boot and is online
57 "boot" - Boot the card OS image specified by the combination
89 boot the card OS. This entry can be written to change the
112 OS boot can be found. The entry can be written to change
132 debugging purpose and early kernel boot messages, the user can
146 debugging purpose and early kernel boot messages, the user can
Dsysfs-kernel-boot_params6 It is used to export the kernel boot parameters of an x86
14 "version" file is the string representation of boot
/linux-4.4.14/Documentation/arm/SA1100/
DAssabet20 The resulting kernel image should be available in linux/arch/arm/boot/zImage.
26 A couple of bootloaders able to boot Linux on Assabet are available:
50 Brief examples on how to boot Linux with RedBoot are shown below. But first
104 The kernel still requires a filesystem to boot. A ramdisk image can be loaded
116 or loaded as described previously. To boot the kernel:
173 what they are in the boot process. From Redboot, the 'fis list' command
198 Therefore to boot Linux with the kernel and its root filesystem in flash, we
205 You might want to boot with a root filesystem over NFS, etc. It is also
217 time the Assabet is rebooted. Therefore it's possible to automatize the boot
220 For example, I use this to boot Linux with both the kernel and the ramdisk
[all …]
DItsy17 Finally, you will need to cd to arch/arm/boot/tools and execute a make there
18 to build the params-itsy program used to boot the kernel.
26 flash menu) Flash the kernel in arch/arm/boot/zImage into 0x08340000
/linux-4.4.14/arch/cris/boot/rescue/
Dhead_v10.S70 ;; The partitiontable is looked for at the first sector after the boot
76 ;; The normal Etrax100 on-chip boot ROM does serial boot at 0x380000f0.
77 ;; That is not where we put our downloaded serial boot-code.
82 ;; one booted through the Etrax serial boot code.
218 move.d $r1, $r7 ; remember boot partition offset
309 ;; check r7, which contains either -1 or the partition to boot from
318 jump $r7 ; boot!
/linux-4.4.14/arch/arm64/boot/dts/rockchip/
Drk3368-r88.dts120 regulator-boot-on;
133 regulator-boot-on;
143 regulator-boot-on;
153 regulator-boot-on;
163 regulator-boot-on;
172 regulator-boot-on;
182 regulator-boot-on;
227 regulator-boot-on;
/linux-4.4.14/arch/sh/include/mach-ecovec24/mach/
Dpartner-jet-setup.txt5 LIST "zImage (RAM boot)"
6 LIST "This script can be used to boot the kernel from RAM via JTAG:"
11 LIST "romImage (Flash boot)"
/linux-4.4.14/lib/
DKconfig.kgdb40 the tests. The most basic of this I/O module is to boot
41 a kernel boot arguments "kgdbwait kgdbts=V1F100"
44 bool "KGDB: Run tests on boot"
48 Run the kgdb tests on boot up automatically without the need
57 boot. See the drivers/misc/kgdbts.c for detailed
96 The config option merely sets the default at boot time. Both
/linux-4.4.14/Documentation/x86/x86_64/
D00-INDEX3 boot-options.txt
4 - AMD64-specific boot options.
/linux-4.4.14/drivers/sfi/
DKconfig11 boot on SFI-only platforms. Currently, all SFI-only platforms are
17 Say 'Y' here to enable the kernel to boot on SFI-only platforms.
/linux-4.4.14/arch/cris/kernel/
Dvmlinux.lds.S32 .boot : { *(.boot) }
/linux-4.4.14/Documentation/mic/mpssd/
Dmicctrl85 boot() function
160 boot $2
/linux-4.4.14/Documentation/accounting/
Ddelay-accounting.txt68 Delay accounting is enabled by default at boot up.
71 to the kernel boot options. The rest of the instructions
86 Get delays, since system boot, for pid 10
90 Get sum of delays, since system boot, for all pids with tgid 5
107 boot data2 data4 data6 etc lib mnt proc sbin subdomain tmp var
/linux-4.4.14/arch/sh/
DMakefile186 boot := arch/sh/boot macro
214 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
222 $(Q)$(MAKE) $(clean)=$(boot)
/linux-4.4.14/arch/sh/include/mach-kfr2r09/mach/
Dpartner-jet-setup.txt2 LIST "set up enough of the kfr2r09 hardware to boot the kernel"
4 LIST "zImage (RAM boot)"
5 LIST "This script can be used to boot the kernel from RAM via JTAG:"
10 LIST "romImage (Flash boot)"
/linux-4.4.14/Documentation/isdn/
DREADME.hysdn106 2 -> card is in an error state due to a previous boot failure
110 to this card. Up to the first successful boot this field only shows a -
113 rebooted and an boot error occurs.
118 The firmware boot files are normally called hyclient.pof for client cards
120 After successfully writing the boot file, complete config files or single
130 1005 First boot stage (bootstrap loader) failed
131 1006 Second boot stage failure
132 1007 Timeout waiting for card ready during boot
166 0x00000080 Log all card related boot messages
/linux-4.4.14/tools/testing/ktest/examples/
Dsnowball.conf30 TEST_TYPE = boot
53 BUILD_TARGET = arch/arm/boot/uImage
/linux-4.4.14/Documentation/devicetree/bindings/display/
Dsimple-framebuffer-sunxi.txt4 bindings. The sunxi simplefb u-boot code relies on the devicetree containing
7 These extensions are intended so that u-boot can select the right node based
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dgtm.txt20 /* filled by u-boot */
29 /* filled by u-boot */
/linux-4.4.14/arch/powerpc/boot/
DMakefile120 src-boot := $(src-wlib) $(src-plat) empty.c
122 src-boot := $(addprefix $(obj)/, $(src-boot))
123 obj-boot := $(addsuffix .o, $(basename $(src-boot)))
177 $(patsubst %.c,%.o, $(filter %.c, $(src-boot))): %.o: %.c FORCE
180 $(patsubst %.S,%.o, $(filter %.S, $(src-boot))): %.o: %.S FORCE
189 targets += $(patsubst $(obj)/%,%,$(obj-boot) wrapper.a)
/linux-4.4.14/arch/tile/
DKconfig357 Allow for specifying boot arguments to the kernel at
360 kernel boot arguments with the kernel itself (that is,
361 to not rely on the boot loader to provide them.)
365 the boot arguments in CONFIG_CMDLINE.
367 Systems with fully functional boot loaders (e.g. mboot, or
376 image and used at boot time. If the boot loader provides a
377 command line at boot time, it is appended to this string to
384 by the boot loader) should specify the device for the root
388 bool "Built-in command line overrides boot loader arguments"
392 Set this option to 'Y' to have the kernel ignore the boot loader
[all …]
/linux-4.4.14/Documentation/fb/
Dvesafb.txt7 The idea is simple: Turn on graphics mode at boot time with the help
11 This means we decide at boot time whenever we want to run in text or
22 * Most important: boot logo :-)
32 Switching modes is done using the vga=... boot parameter. Read
39 The graphic modes are NOT in the list which you get if you boot with
99 available) and boot linux with loadlin.
132 ugly flicker effects (boot logo flickers for
Daty128fb.txt14 * Most important: boot logo :-)
27 boot parameter or using `fbset' program.
32 You should compile in both vgacon (to boot if you remove your Rage128 from
Dgxfb.txt15 * Most important: boot logo :-)
25 Switching modes is done using gxfb.mode_option=<resolution>... boot
Dlxfb.txt15 * Most important: boot logo :-)
25 Switching modes is done using lxfb.mode_option=<resolution>... boot
/linux-4.4.14/Documentation/scsi/
Dncr53c8xx.txt56 10.3 Advised boot setup commands
57 10.4 PCI configuration fix-up boot option
58 10.5 Serial NVRAM support boot option
59 10.6 SCSI BUS checking boot option
60 10.7 IMMEDIATE ARBITRATION boot option
273 depths from the boot command-line. For example:
303 1st method: boot your system using 'ncr53c8xx=verb:0' option.
305 corresponding to your controller after boot-up.
313 checking by entering appropriate options from the boot command line.
537 th driver verbose level after boot-up.
[all …]
Dsym53c8xx_2.txt47 10.4 SCSI BUS checking boot option
244 depths from the boot command-line. For example:
274 1st method: boot your system using 'sym53c8xx=verb:0' option.
276 corresponding to your controller after boot-up.
378 th driver verbose level after boot-up.
404 this feature after boot-up only for devices that support it safely.
414 This parameter can be specified from the boot command line.
422 will use at boot time for synchronous data transfer negotiations.
429 Setup commands can be passed to the driver either at boot time or as
432 Example of boot setup command under lilo prompt:
[all …]
/linux-4.4.14/Documentation/power/
Dswsusp-dmcrypt.txt15 the swap device(s) and the boot partition which may contain a mini
41 Prepare your boot loader to use the initrd you will create or
45 image=/boot/vmlinuz
46 initrd=/boot/initrd.gz
66 continues boot with your mini system on /dev/hda1 if resume
121 for init like "single" or "emergency" as boot parameters.
/linux-4.4.14/arch/m32r/boot/
Dsetup.S61 .section .boot, "ax"
62 ENTRY(boot)
105 ;; boot AP
/linux-4.4.14/drivers/gpu/drm/nouveau/include/nvkm/core/
Dmemory.h23 void (*boot)(struct nvkm_memory *, struct nvkm_vm *); member
38 #define nvkm_memory_boot(p,v) (p)->func->boot((p),(v))
/linux-4.4.14/Documentation/timers/
DNO_HZ.txt4 This document describes Kconfig options and boot parameters that can
94 There is also a boot parameter "nohz=" that can be used to disable
96 By default, CONFIG_NO_HZ_IDLE=y kernels boot with "nohz=on", enabling
120 boot parameter specifies the adaptive-ticks CPUs. For example,
128 boot CPU is prohibited from entering adaptive-ticks mode. Specifying a
129 "nohz_full=" mask that includes the boot CPU will result in a boot-time
130 error message, and the boot CPU will be removed from the mask. Note that
135 that all CPUs other than the boot CPU are adaptive-ticks CPUs. This
136 Kconfig parameter will be overridden by the "nohz_full=" boot parameter,
138 the "nohz_full=1" boot parameter is specified, the boot parameter will
[all …]
/linux-4.4.14/fs/sysfs/
DKconfig20 partition. If sysfs is disabled you must specify the boot device on
21 the kernel boot command line via its major and minor numbers. For
/linux-4.4.14/Documentation/block/
Dcmdline-partition.txt35 'blkdevparts=mmcblk0:1G(data0),1G(data1),-;mmcblk0boot0:1m(boot),-(kernel)'
39 mmcblk0boot0: p1(boot) p2(kernel)
/linux-4.4.14/arch/x86/boot/
DMakefile174 mkisofs -J -r -o $(obj)/image.iso -b isolinux.bin -c boot.cat \
175 -no-emul-boot -boot-load-size 4 -boot-info-table \
/linux-4.4.14/drivers/firmware/
DKconfig31 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
36 BIOS tries boot from. This information is then exported via sysfs.
38 This option is experimental and is known to fail to boot on some
74 you must specify the "console=hcdp" kernel boot argument.
154 detect iSCSI boot parameters dynamically during system boot, say Y.
/linux-4.4.14/arch/metag/kernel/
Dhead.S28 MOV D1Ar1,D0Ar4 !Store kernel boot params
54 ! the boot thread might have performed prior to coherency taking effect.
/linux-4.4.14/arch/mips/include/asm/mach-cavium-octeon/
Dkernel-entry-init.h26 # a3 = address of boot descriptor block
102 # This is the variable where the next core to boot os stored
130 # Someone tried to boot SMP with a non SMP kernel. All extra cores
/linux-4.4.14/drivers/firmware/efi/
DKconfig60 Saying Y here will enable "efi_fake_mem" boot option.
68 int "maximum allowable number of ranges in efi_fake_mem boot option"
73 Maximum allowable number of ranges in efi_fake_mem boot option.
/linux-4.4.14/arch/x86/xen/
DKconfig15 kernel to boot in a paravirtualized environment under the
38 boot parameter "xen_512gb_limit".
/linux-4.4.14/arch/arm/mach-omap1/
DKconfig97 Support for the Palm Tungsten E PDA. To boot the kernel, you'll
106 Support for the Palm Zire71 PDA. To boot the kernel,
115 Support for the Palm Tungsten|T PDA. To boot the kernel, you'll
125 Support for the Siemens SX1 phone. To boot the kernel,
/linux-4.4.14/drivers/staging/unisys/Documentation/ABI/
Dsysfs-platform-visorchipset29 the previous guest boot) has no effect.
36 Description: The boottotool flag controls s-Par behavior on the next boot of
37 this guest. Setting the flag will cause the guest to boot from
48 action to perform on the next guest boot-up. The meaning of the
/linux-4.4.14/tools/lguest/
Dlguest.c489 struct boot_params boot; in load_bzimage() local
499 read(fd, &boot, sizeof(boot)); in load_bzimage()
502 if (memcmp(&boot.hdr.header, "HdrS", 4) != 0) in load_bzimage()
506 lseek(fd, (boot.hdr.setup_sects+1) * 512, SEEK_SET); in load_bzimage()
513 return boot.hdr.code32_start; in load_bzimage()
3224 struct boot_params *boot; in main() local
3319 boot = from_guest_phys(0); in main()
3328 boot->hdr.ramdisk_image = mem - initrd_size; in main()
3329 boot->hdr.ramdisk_size = initrd_size; in main()
3331 boot->hdr.type_of_loader = 0xFF; in main()
[all …]

123456