Searched refs:bzImage (Results 1 – 25 of 36) sorted by relevance
12
| /kernel/linux/linux-5.10/arch/x86/boot/ |
| D | Makefile | 31 targets := vmlinux.bin setup.bin setup.elf bzImage
76 $(obj)/bzImage: asflags-y := $(SVGA_MODE)
83 $(obj)/bzImage: $(obj)/setup.bin $(obj)/vmlinux.bin $(obj)/tools/build FORCE
130 cmd_genimage = sh $(srctree)/$(src)/genimage.sh $2 $3 $(obj)/bzImage \
136 bzdisk: $(obj)/bzImage $(obj)/mtools.conf
140 fdimage fdimage144: $(obj)/bzImage $(obj)/mtools.conf
144 fdimage288: $(obj)/bzImage $(obj)/mtools.conf
148 isoimage: $(obj)/bzImage
155 cat $(obj)/bzImage > $(INSTALL_PATH)/vmlinuz
160 sh $(srctree)/$(src)/install.sh $(KERNELRELEASE) $(obj)/bzImage \
|
| D | .gitignore | 3 bzImage
|
| /kernel/linux/linux-5.10/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 | 3 bzImage
|
| /kernel/linux/linux-5.10/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 | 302 image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
310 kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
311 /boot/bzImage. To use the new kernel, save a copy of the old image
|
| /kernel/linux/linux-5.10/arch/parisc/ |
| D | Makefile | 22 KBUILD_IMAGE := $(boot)/bzImage
154 PHONY += bzImage $(BOOT_TARGETS) $(INSTALL_TARGETS)
157 all: bzImage
162 bzImage: vmlinux target
166 vmlinuz: bzImage
167 $(OBJCOPY) $(boot)/bzImage $@
|
| /kernel/linux/linux-5.10/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…
74 sh -x $(srctree)/$(obj)/install.sh $(KERNELRELEASE) $(obj)/bzImage \
|
| D | .gitignore | 3 bzImage
|
| /kernel/linux/build/ |
| D | build_kernel.sh | 42 cp ${2}/kernel/OBJ/${8}/arch/x86/boot/bzImage ${3}/bzImage
|
| D | BUILD.gn | 29 kernel_image = "bzImage"
|
| /kernel/linux/linux-5.10/arch/x86/ |
| D | Makefile | 262 PHONY += bzImage $(BOOT_TARGETS)
265 all: bzImage
268 KBUILD_IMAGE := $(boot)/bzImage
270 bzImage: vmlinux target
276 $(Q)ln -fsn ../../x86/boot/bzImage $(objtree)/arch/$(UTS_MACHINE)/boot/$@
|
| /kernel/linux/linux-5.10/arch/s390/ |
| D | Makefile | 155 all: bzImage
158 KBUILD_IMAGE := $(boot)/bzImage
163 bzImage: vmlinux target
|
| /kernel/linux/linux-5.10/tools/testing/ktest/examples/include/ |
| D | defaults.conf | 63 BUILD_TARGET = arch/x86/boot/bzImage
|
| /kernel/linux/linux-5.10/arch/h8300/boot/compressed/ |
| D | head.S | 43 .byte 1 ; Load flags bzImage=1
|
| /kernel/linux/linux-5.10/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-check-branches.sh | 92 ( cd $resdir/$ds/$idir/$rrd; rm -f */vmlinux */bzImage */System.map */Module.symvers )
|
| D | kvm-test-1-run.sh | 76 if test "$base_resdir" != "$resdir" -a -f $base_resdir/bzImage -a -f $base_resdir/vmlinux
|
| /kernel/linux/linux-5.10/arch/sh/boot/compressed/ |
| D | head_32.S | 122 .byte 1 ! Load flags bzImage=1
|
| /kernel/linux/linux-5.10/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> \
|
| /kernel/linux/linux-5.10/arch/arm/ |
| D | Makefile | 319 bzImage: zImage target
324 PHONY += bzImage $(BOOT_TARGETS) $(INSTALL_TARGETS)
|
| /kernel/linux/linux-5.10/Documentation/ |
| D | dontdiff | 102 bzImage*
|
| /kernel/linux/linux-5.10/Documentation/filesystems/cifs/ |
| D | cifsroot.rst | 101 -kernel /path/to/linux/arch/x86/boot/bzImage -nographic \
|
| /kernel/linux/linux-5.10/tools/testing/selftests/wireguard/qemu/ |
| D | Makefile | 115 KERNEL_BZIMAGE := $(KERNEL_BUILD_PATH)/arch/x86/boot/bzImage
125 KERNEL_BZIMAGE := $(KERNEL_BUILD_PATH)/arch/x86/boot/bzImage
|
| /kernel/linux/linux-5.10/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
120 When using bzImage, the protected-mode kernel was relocated to
138 zImage or old bzImage kernels, which need data written into the
142 For a modern bzImage kernel with boot protocol version >= 2.02, a
236 field are unusable, which means the size of a bzImage kernel
1194 0x100000 for bzImage kernels.
1196 The kernel is a bzImage kernel if the protocol >= 2.00 and the 0x01
1205 0x90000. bzImage kernels allow much more flexibility.
|
| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| D | makefiles.rst | 1206 bzImage: vmlinux
1220 echo '* bzImage - Image (arch/$(ARCH)/boot/bzImage)'
1234 all: bzImage
1236 When "make" is executed without arguments, bzImage will be built.
1382 targets += bzImage
1383 $(obj)/bzImage: $(obj)/vmlinux.bin $(obj)/tools/build FORCE
1387 When updating the $(obj)/bzImage target, the line:
1389 BUILD arch/x86/boot/bzImage
|
12