Home
last modified time | relevance | path

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

12

/linux/Documentation/admin-guide/
A Defi-stub.rst5 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 …]
A DREADME.rst303 image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
311 kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
312 /boot/bzImage. To use the new kernel, save a copy of the old image
/linux/arch/parisc/
A DMakefile20 KBUILD_IMAGE := $(boot)/bzImage
147 PHONY += bzImage $(BOOT_TARGETS) $(INSTALL_TARGETS)
150 all: bzImage
155 bzImage: vmlinux target
159 vmlinuz: bzImage
160 $(OBJCOPY) $(boot)/bzImage $@
/linux/arch/x86/boot/
A DMakefile31 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
123 imgdeps = $(obj)/bzImage $(obj)/mtools.conf $(src)/genimage.sh
133 cmd_genimage = $(BASH) $(srctree)/$(src)/genimage.sh $2 $3 $(obj)/bzImage \
A D.gitignore3 bzImage
/linux/arch/x86/
A DMakefile241 PHONY += bzImage $(BOOT_TARGETS)
244 all: bzImage
247 KBUILD_IMAGE := $(boot)/bzImage
249 bzImage: vmlinux target
255 $(Q)ln -fsn ../../x86/boot/bzImage $(objtree)/arch/$(UTS_MACHINE)/boot/$@
/linux/arch/parisc/boot/
A DMakefile7 targets += bzImage
13 $(obj)/bzImage: $(obj)/compressed/vmlinux FORCE
A D.gitignore3 bzImage
/linux/arch/s390/
A DMakefile132 all: bzImage
135 KBUILD_IMAGE := $(boot)/bzImage
141 bzImage: vmlinux target
/linux/arch/s390/boot/
A DMakefile44 targets := bzImage startup.a section_cmp.boot.data section_cmp.boot.preserved.data $(obj-y)
62 $(obj)/bzImage: $(obj)/compressed/vmlinux $(obj)/section_cmp.boot.data $(obj)/section_cmp.boot.pres…
A D.gitignore3 bzImage
/linux/Documentation/translations/zh_CN/admin-guide/
A DREADME.rst259 .../linux/arch/x86/boot/bzImage)复制到常规可引导内核的位置。
265 /bzImage或/boot/bzImage。使用新内核前,请保存旧映像的副本,并复制
/linux/Documentation/translations/zh_TW/admin-guide/
A DREADME.rst262 .../linux/arch/x86/boot/bzImage)複製到常規可引導內核的位置。
268 /bzImage或/boot/bzImage。使用新內核前,請保存舊映像的副本,並複製
/linux/tools/testing/ktest/examples/include/
A Ddefaults.conf63 BUILD_TARGET = arch/x86/boot/bzImage
/linux/arch/h8300/boot/compressed/
A Dhead.S43 .byte 1 ; Load flags bzImage=1
/linux/tools/testing/selftests/rcutorture/bin/
A Dkvm-check-branches.sh91 ( cd $resdir/$ds/$idir/$rrd; rm -f */vmlinux */bzImage */System.map */Module.symvers )
A Dkvm-test-1-run.sh75 if test "$base_resdir" != "$resdir" && test -f $base_resdir/bzImage && test -f $base_resdir/vmlinux
/linux/Documentation/translations/zh_CN/virt/
A Dne_overview.rst66 内核bzImage、内核命令行、ramdisk(s)是enclave镜像格式(EIF)的一部分;另外
/linux/arch/arm/
A DMakefile297 bzImage: zImage target
302 PHONY += bzImage $(BOOT_TARGETS) $(INSTALL_TARGETS)
/linux/arch/sh/boot/compressed/
A Dhead_32.S122 .byte 1 ! Load flags bzImage=1
/linux/Documentation/admin-guide/kdump/
A Dkdump.rst374 can choose to load the uncompressed vmlinux or compressed bzImage/vmlinuz
379 - Use bzImage/vmlinuz if kernel is relocatable.
392 - Use image or bzImage
409 If you are using a compressed bzImage/vmlinuz, then use following command
412 kexec -p <dump-capture-kernel-bzImage> \
419 kexec --type zImage -p <dump-capture-kernel-bzImage> \
/linux/Documentation/filesystems/cifs/
A Dcifsroot.rst101 -kernel /path/to/linux/arch/x86/boot/bzImage -nographic \
/linux/Documentation/
A Ddontdiff102 bzImage*
/linux/Documentation/x86/
A Dboot.rst20 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.
/linux/tools/testing/selftests/wireguard/qemu/
A DMakefile115 KERNEL_BZIMAGE := $(KERNEL_BUILD_PATH)/arch/x86/boot/bzImage
125 KERNEL_BZIMAGE := $(KERNEL_BUILD_PATH)/arch/x86/boot/bzImage

Completed in 29 milliseconds

12