Home
last modified time | relevance | path

Searched refs:bzImage (Results 1 – 25 of 29) sorted by relevance

12

/Linux-v4.19/arch/x86/boot/
DMakefile29 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.gitignore2 bzImage
Dheader.S167 # The size of the bzImage is written in tools/build.c
/Linux-v4.19/Documentation/
Defi-stub.txt5 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 …]
Ddontdiff100 bzImage*
/Linux-v4.19/arch/parisc/boot/
DMakefile12 targets += bzImage
18 $(obj)/bzImage: $(obj)/compressed/vmlinux FORCE
24 install: $(CONFIGURE) $(obj)/bzImage
25 sh -x $(srctree)/$(obj)/install.sh $(KERNELRELEASE) $(obj)/bzImage \
D.gitignore2 bzImage
/Linux-v4.19/arch/s390/boot/
DMakefile31 targets := bzImage startup.a $(obj-y)
36 $(obj)/bzImage: $(obj)/compressed/vmlinux FORCE
48 install: $(CONFIGURE) $(obj)/bzImage
49 sh -x $(srctree)/$(obj)/install.sh $(KERNELRELEASE) $(obj)/bzImage \
D.gitignore2 bzImage
/Linux-v4.19/arch/parisc/
DMakefile120 PHONY += bzImage $(BOOT_TARGETS) $(INSTALL_TARGETS)
123 all: bzImage
128 bzImage: vmlinux target
132 vmlinuz: bzImage
133 $(OBJCOPY) $(boot)/bzImage $@
/Linux-v4.19/arch/x86/
DMakefile272 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/$@
DKconfig1937 This kernel feature allows a bzImage to be loaded directly
2019 bool "Enable bzImage signature verification support"
2024 Enable bzImage signature verification support.
2054 bzImage will decompress itself to above physical address and
2055 run from there. Otherwise, bzImage will run from the address where
2060 as now bzImage can be compiled as a completely relocatable image
2063 to use a bzImage for capturing the crash dump and want to use a
2068 So if you are using bzImage for capturing the crash dump,
2078 Usage of bzImage for capturing the crash dump is recommended as
2081 gone away after relocatable bzImage support is introduced. But it
DKconfig.debug14 (e.g. bzImage) of the boot. If you disable this you will still
/Linux-v4.19/arch/s390/
DMakefile137 all: bzImage
140 KBUILD_IMAGE := $(boot)/bzImage
145 bzImage: vmlinux target
/Linux-v4.19/tools/testing/ktest/examples/include/
Ddefaults.conf63 BUILD_TARGET = arch/x86/boot/bzImage
/Linux-v4.19/arch/h8300/boot/compressed/
Dhead.S43 .byte 1 ; Load flags bzImage=1
/Linux-v4.19/arch/sh/boot/compressed/
Dhead_32.S122 .byte 1 ! Load flags bzImage=1
/Linux-v4.19/Documentation/kdump/
Dkdump.txt325 can choose to load the uncompressed vmlinux or compressed bzImage/vmlinuz
330 - Use bzImage/vmlinuz if kernel is relocatable.
336 - Use image or bzImage
349 If you are using a compressed bzImage/vmlinuz, then use following command
352 kexec -p <dump-capture-kernel-bzImage> \
359 kexec --type zImage -p <dump-capture-kernel-bzImage> \
/Linux-v4.19/arch/arm/
DMakefile325 bzImage: zImage target
330 PHONY += bzImage $(BOOT_TARGETS) $(INSTALL_TARGETS)
/Linux-v4.19/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run.sh91 if test "$base_resdir" != "$resdir" -a -f $base_resdir/bzImage -a -f $base_resdir/vmlinux
/Linux-v4.19/Documentation/x86/
Dboot.txt16 Protocol 2.00: (Kernel 1.3.73) Added bzImage and initrd support, as
61 to struct boot_params for loading bzImage and ramdisk
92 When using bzImage, the protected-mode kernel was relocated to
110 zImage or old bzImage kernels, which need data written into the
114 For a modern bzImage kernel with boot protocol version >= 2.02, a
205 field are unusable, which means the size of a bzImage kernel
902 0x100000 for bzImage kernels.
904 The kernel is a bzImage kernel if the protocol >= 2.00 and the 0x01
913 0x90000. bzImage kernels allow much more flexibility.
/Linux-v4.19/Documentation/kbuild/
Dmakefiles.txt1027 bzImage: vmlinux
1040 echo '* bzImage - Image (arch/$(ARCH)/boot/bzImage)'
1053 all: bzImage
1055 When "make" is executed without arguments, bzImage will be built.
1184 targets += bzImage
1185 $(obj)/bzImage: $(obj)/vmlinux.bin $(obj)/tools/build FORCE
1189 When updating the $(obj)/bzImage target, the line
1191 BUILD arch/x86/boot/bzImage
/Linux-v4.19/Documentation/admin-guide/
DREADME.rst296 image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
304 kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
305 /boot/bzImage. To use the new kernel, save a copy of the old image
/Linux-v4.19/Documentation/serial/
Dmoxa-smartio360 d. make bzImage /* take probably 10-20 minutes */
369 Note that if the result of "make bzImage" is ERROR, then you have to
/Linux-v4.19/tools/perf/Documentation/
Dperf-stat.txt168 …10 --null --sync --pre 'make -s O=defconfig-build/clean' -- make -s -j64 O=defconfig-build/ bzImage

12