Home
last modified time | relevance | path

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

/linux-4.4.14/arch/x86/boot/
DMakefile21 targets := vmlinux.bin setup.bin setup.elf bzImage
64 $(obj)/bzImage: asflags-y := $(SVGA_MODE)
70 $(obj)/bzImage: $(obj)/setup.bin $(obj)/vmlinux.bin $(obj)/tools/build FORCE
126 bzdisk: $(obj)/bzImage $(obj)/mtools.conf
134 MTOOLSRC=$(obj)/mtools.conf mcopy $(obj)/bzImage a:linux ; sync
137 fdimage fdimage144: $(obj)/bzImage $(obj)/mtools.conf
146 MTOOLSRC=$(obj)/mtools.conf mcopy $(obj)/bzImage v:linux ; sync
148 fdimage288: $(obj)/bzImage $(obj)/mtools.conf
157 MTOOLSRC=$(obj)/mtools.conf mcopy $(obj)/bzImage w:linux ; sync
159 isoimage: $(obj)/bzImage
[all …]
D.gitignore2 bzImage
Dheader.S168 # The size of the bzImage is written in tools/build.c
/linux-4.4.14/Documentation/
Defi-stub.txt4 On the x86 and ARM platforms, a kernel zImage/bzImage can masquerade
6 it as an EFI executable. The code that modifies the bzImage header,
28 **** How to install bzImage.efi
30 The bzImage located in arch/x86/boot/bzImage must be copied to the EFI
33 not possible to execute bzImage.efi from the usual Linux file systems
42 Arguments to the kernel can be passed after bzImage.efi, e.g.
44 fs0:> bzImage.efi console=ttyS0 root=/dev/sda4
61 bzImage.efi
71 fs0:\Kernels> bzImage.efi initrd=\Kernels\initrd-large.img
73 Notice how bzImage.efi can be specified with a relative path. That's
[all …]
Ddontdiff99 bzImage*
Dinitrd.txt183 image = /bzImage
/linux-4.4.14/arch/s390/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-4.4.14/arch/x86/
DMakefile239 PHONY += bzImage $(BOOT_TARGETS)
242 all: bzImage
245 KBUILD_IMAGE := $(boot)/bzImage
247 bzImage: vmlinux target
253 $(Q)ln -fsn ../../x86/boot/bzImage $(objtree)/arch/$(UTS_MACHINE)/boot/$@
DKconfig1705 This kernel feature allows a bzImage to be loaded directly
1784 bool "Enable bzImage signature verification support"
1789 Enable bzImage signature verification support.
1819 bzImage will decompress itself to above physical address and
1820 run from there. Otherwise, bzImage will run from the address where
1825 as now bzImage can be compiled as a completely relocatable image
1828 to use a bzImage for capturing the crash dump and want to use a
1833 So if you are using bzImage for capturing the crash dump,
1843 Usage of bzImage for capturing the crash dump is recommended as
1846 gone away after relocatable bzImage support is introduced. But it
DKconfig.debug30 (e.g. bzImage) of the boot. If you disable this you will still
/linux-4.4.14/arch/parisc/
DMakefile119 PHONY += bzImage $(BOOT_TARGETS) $(INSTALL_TARGETS)
121 bzImage zImage: vmlinuz target
/linux-4.4.14/arch/s390/
DMakefile110 all: image bzImage
115 image bzImage: vmlinux target
/linux-4.4.14/tools/testing/ktest/examples/include/
Ddefaults.conf63 BUILD_TARGET = arch/x86/boot/bzImage
/linux-4.4.14/arch/frv/boot/
DMakefile42 bzImage: zImage target
/linux-4.4.14/arch/h8300/boot/compressed/
Dhead.S42 .byte 1 ; Load flags bzImage=1
/linux-4.4.14/arch/xtensa/
DMakefile96 bzImage : zImage target
/linux-4.4.14/arch/sh/boot/compressed/
Dhead_32.S121 .byte 1 ! Load flags bzImage=1
/linux-4.4.14/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run.sh172 echo $QEMU $qemu_args -m 512 -kernel $resdir/bzImage -append \"$qemu_append $boot_args\" > $resdir/…
/linux-4.4.14/Documentation/kdump/
Dkdump.txt323 can choose to load the uncompressed vmlinux or compressed bzImage/vmlinuz
328 - Use bzImage/vmlinuz if kernel is relocatable.
334 - Use image or bzImage
345 If you are using a compressed bzImage/vmlinuz, then use following command
348 kexec -p <dump-capture-kernel-bzImage> \
355 kexec --type zImage -p <dump-capture-kernel-bzImage> \
/linux-4.4.14/arch/arm/
DMakefile316 bzImage: zImage target
321 PHONY += bzImage $(BOOT_TARGETS) $(INSTALL_TARGETS)
/linux-4.4.14/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-4.4.14/Documentation/kbuild/
Dmakefiles.txt1042 bzImage: vmlinux
1055 echo '* bzImage - Image (arch/$(ARCH)/boot/bzImage)'
1068 all: bzImage
1070 When "make" is executed without arguments, bzImage will be built.
1189 targets += bzImage
1190 $(obj)/bzImage: $(obj)/vmlinux.bin $(obj)/tools/build FORCE
1194 When updating the $(obj)/bzImage target, the line
1196 BUILD arch/x86/boot/bzImage
/linux-4.4.14/tools/lguest/
Dlguest.txt80 can also use a standard bzImage.
/linux-4.4.14/
DREADME292 image (e.g. .../linux/arch/i386/boot/bzImage after compilation)
300 kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
301 /boot/bzImage. To use the new kernel, save a copy of the old image
/linux-4.4.14/tools/perf/Documentation/
Dperf-stat.txt135 …10 --null --sync --pre 'make -s O=defconfig-build/clean' -- make -s -j64 O=defconfig-build/ bzImage
/linux-4.4.14/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-4.4.14/Documentation/blockdev/
DREADME.DAC960215 make bzImage (or zImage)
217 Then install "arch/x86/boot/bzImage" or "arch/x86/boot/zImage" as your
/linux-4.4.14/Documentation/sound/oss/
DIntroduction117 5. Make the kernel (e.g., make bzImage), and install the kernel.
/linux-4.4.14/Documentation/networking/
Dcs89x0.txt330 image=/boot/bzImage-2.3.48