Searched refs:bzImage (Results 1 – 25 of 29) sorted by relevance
12
| /Linux-v5.4/arch/x86/boot/ |
| D | Makefile | 29 targets := vmlinux.bin setup.bin setup.elf bzImage
73 $(obj)/bzImage: asflags-y := $(SVGA_MODE)
80 $(obj)/bzImage: $(obj)/setup.bin $(obj)/vmlinux.bin $(obj)/tools/build FORCE
127 cmd_genimage = sh $(srctree)/$(src)/genimage.sh $2 $3 $(obj)/bzImage \
131 bzdisk: $(obj)/bzImage $(obj)/mtools.conf
135 fdimage fdimage144: $(obj)/bzImage $(obj)/mtools.conf
139 fdimage288: $(obj)/bzImage $(obj)/mtools.conf
143 isoimage: $(obj)/bzImage
147 bzlilo: $(obj)/bzImage
150 cat $(obj)/bzImage > $(INSTALL_PATH)/vmlinuz
[all …]
|
| D | .gitignore | 2 bzImage
|
| D | header.S | 167 # The size of the bzImage is written in tools/build.c
|
| /Linux-v5.4/arch/parisc/boot/ |
| D | Makefile | 7 targets += bzImage
13 $(obj)/bzImage: $(obj)/compressed/vmlinux FORCE
19 install: $(CONFIGURE) $(obj)/bzImage
20 sh -x $(srctree)/$(obj)/install.sh $(KERNELRELEASE) $(obj)/bzImage \
|
| D | .gitignore | 2 bzImage
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | efi-stub.rst | 5 On the x86 and ARM platforms, a kernel zImage/bzImage can masquerade
7 it as an EFI executable. The code that modifies the bzImage header,
29 How to install bzImage.efi
32 The bzImage located in arch/x86/boot/bzImage must be copied to the EFI
35 not possible to execute bzImage.efi from the usual Linux file systems
45 Arguments to the kernel can be passed after bzImage.efi, e.g.::
47 fs0:> bzImage.efi console=ttyS0 root=/dev/sda4
65 bzImage.efi
75 fs0:\Kernels> bzImage.efi initrd=\Kernels\initrd-large.img
77 Notice how bzImage.efi can be specified with a relative path. That's
[all …]
|
| D | README.rst | 295 image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
303 kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
304 /boot/bzImage. To use the new kernel, save a copy of the old image
|
| /Linux-v5.4/arch/parisc/ |
| D | Makefile | 143 PHONY += bzImage $(BOOT_TARGETS) $(INSTALL_TARGETS)
146 all: bzImage
151 bzImage: vmlinux target
155 vmlinuz: bzImage
156 $(OBJCOPY) $(boot)/bzImage $@
|
| /Linux-v5.4/arch/s390/boot/ |
| D | Makefile | 43 targets := bzImage startup.a section_cmp.boot.data section_cmp.boot.preserved.data $(obj-y)
61 $(obj)/bzImage: $(obj)/compressed/vmlinux $(obj)/section_cmp.boot.data $(obj)/section_cmp.boot.pres…
73 install: $(CONFIGURE) $(obj)/bzImage
74 sh -x $(srctree)/$(obj)/install.sh $(KERNELRELEASE) $(obj)/bzImage \
|
| D | .gitignore | 2 bzImage
|
| /Linux-v5.4/arch/x86/ |
| D | Makefile | 272 PHONY += bzImage $(BOOT_TARGETS)
275 all: bzImage
278 KBUILD_IMAGE := $(boot)/bzImage
280 bzImage: vmlinux target
286 $(Q)ln -fsn ../../x86/boot/bzImage $(objtree)/arch/$(UTS_MACHINE)/boot/$@
|
| D | Kconfig | 2009 This kernel feature allows a bzImage to be loaded directly
2101 bool "Enable bzImage signature verification support"
2106 Enable bzImage signature verification support.
2136 bzImage will decompress itself to above physical address and
2137 run from there. Otherwise, bzImage will run from the address where
2142 as now bzImage can be compiled as a completely relocatable image
2145 to use a bzImage for capturing the crash dump and want to use a
2150 So if you are using bzImage for capturing the crash dump,
2160 Usage of bzImage for capturing the crash dump is recommended as
2163 gone away after relocatable bzImage support is introduced. But it
|
| D | Kconfig.debug | 14 (e.g. bzImage) of the boot. If you disable this you will still
|
| /Linux-v5.4/arch/s390/ |
| D | Makefile | 144 all: bzImage
147 KBUILD_IMAGE := $(boot)/bzImage
152 bzImage: vmlinux target
|
| /Linux-v5.4/tools/testing/ktest/examples/include/ |
| D | defaults.conf | 63 BUILD_TARGET = arch/x86/boot/bzImage
|
| /Linux-v5.4/arch/h8300/boot/compressed/ |
| D | head.S | 43 .byte 1 ; Load flags bzImage=1
|
| /Linux-v5.4/arch/sh/boot/compressed/ |
| D | head_32.S | 122 .byte 1 ! Load flags bzImage=1
|
| /Linux-v5.4/Documentation/admin-guide/kdump/ |
| D | kdump.rst | 329 can choose to load the uncompressed vmlinux or compressed bzImage/vmlinuz
335 - Use bzImage/vmlinuz if kernel is relocatable.
347 - Use image or bzImage
364 If you are using a compressed bzImage/vmlinuz, then use following command
367 kexec -p <dump-capture-kernel-bzImage> \
374 kexec --type zImage -p <dump-capture-kernel-bzImage> \
|
| /Linux-v5.4/arch/arm/ |
| D | Makefile | 329 bzImage: zImage target
334 PHONY += bzImage $(BOOT_TARGETS) $(INSTALL_TARGETS)
|
| /Linux-v5.4/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-test-1-run.sh | 73 if test "$base_resdir" != "$resdir" -a -f $base_resdir/bzImage -a -f $base_resdir/vmlinux
|
| /Linux-v5.4/Documentation/ |
| D | dontdiff | 101 bzImage*
|
| /Linux-v5.4/Documentation/filesystems/cifs/ |
| D | cifsroot.txt | 93 -kernel /path/to/linux/arch/x86/boot/bzImage -nographic \
|
| /Linux-v5.4/Documentation/x86/ |
| D | boot.rst | 20 Protocol 2.00 (Kernel 1.3.73) Added bzImage and initrd support, as
65 to struct boot_params for loading bzImage and ramdisk
102 When using bzImage, the protected-mode kernel was relocated to
120 zImage or old bzImage kernels, which need data written into the
124 For a modern bzImage kernel with boot protocol version >= 2.02, a
217 field are unusable, which means the size of a bzImage kernel
1023 0x100000 for bzImage kernels.
1025 The kernel is a bzImage kernel if the protocol >= 2.00 and the 0x01
1034 0x90000. bzImage kernels allow much more flexibility.
|
| /Linux-v5.4/Documentation/kbuild/ |
| D | makefiles.rst | 1063 bzImage: vmlinux
1077 echo '* bzImage - Image (arch/$(ARCH)/boot/bzImage)'
1091 all: bzImage
1093 When "make" is executed without arguments, bzImage will be built.
1256 targets += bzImage
1257 $(obj)/bzImage: $(obj)/vmlinux.bin $(obj)/tools/build FORCE
1261 When updating the $(obj)/bzImage target, the line:
1263 BUILD arch/x86/boot/bzImage
|
| /Linux-v5.4/Documentation/driver-api/serial/ |
| D | moxa-smartio.rst | 414 make bzImage # take probably 10-20 minutes
424 Note that if the result of "make bzImage" is ERROR, then you have to
|
12
