Home
last modified time | relevance | path

Searched refs:initrd (Results 1 – 25 of 642) sorted by relevance

12345678910>>...26

/OK3568_Linux_fs/kernel/Documentation/admin-guide/
H A Dinitrd.rst1 Using the initial RAM disk (initrd)
8 initrd provides the capability to load a RAM disk by the boot loader.
11 from a different device. The previous root (from initrd) is then moved
14 initrd is mainly designed to allow system startup to occur in two phases,
16 where additional modules are loaded from initrd.
18 This document gives a brief overview of the use of initrd. A more detailed
25 When using initrd, the system typically boots as follows:
28 2) the kernel converts initrd into a "normal" RAM disk and
29 frees the memory used by initrd
33 4) root device is mounted. if it is ``/dev/ram0``, the initrd image is
[all …]
H A Defi-stub.rst50 The "initrd=" option
54 multiple initrd files using the "initrd=" option. This is the only EFI
58 The path to the initrd file must be an absolute path from the
66 initrd-large.img
69 initrd-small.img
70 initrd-medium.img
72 to boot with the initrd-large.img file if the current working
75 fs0:\Kernels> bzImage.efi initrd=\Kernels\initrd-large.img
99 "dtb=" is processed in the same manner as the "initrd=" option that is
H A Dbootconfig.rst161 Since the boot configuration file is loaded with initrd, it will be added
162 to the end of the initrd (initramfs) image file with padding, size,
165 [initrd][bootconfig][padding][size(le32)][checksum(le32)][#BOOTCONFIG\n]
169 When the boot configuration is added to the initrd image, the total
174 The Linux kernel decodes the last part of the initrd image in memory to
178 loader passes the correct initrd file size. If by any chance, the boot
183 to/from initrd image. You can build it by the following command::
187 To add your boot config file to initrd image, run bootconfig as below
190 # tools/bootconfig/bootconfig -a your-config /boot/initrd.img-X.Y.Z
194 # tools/bootconfig/bootconfig -d /boot/initrd.img-X.Y.Z
[all …]
/OK3568_Linux_fs/kernel/tools/testing/selftests/rcutorture/doc/
H A Dinitrd.txt1 The rcutorture scripting tools automatically create an initrd containing
7 userspace environments, you might wish to press an existing initrd
12 zcat /initrd.img > /tmp/initrd.img.zcat
13 mkdir initrd
14 cd initrd
15 cpio -id < /tmp/initrd.img.zcat
16 # Manually verify that initrd contains needed binaries and libraries.
/OK3568_Linux_fs/yocto/poky/scripts/lib/wic/plugins/source/
H A Dbootimg-efi.py55 initrd = source_params.get('initrd')
57 if initrd:
62 initrds = initrd.split(';')
94 if initrd:
95 initrds = initrd.split(';')
127 initrd = source_params.get('initrd')
129 if initrd and source_params.get('create-unified-kernel-image') != "true":
135 initrds = initrd.split(';')
183 if initrd:
184 initrds = initrd.split(';')
[all …]
H A Disoimage-isohybrid.py148 initrd = get_bitbake_var("INITRD_LIVE") or get_bitbake_var("INITRD")
149 if not initrd:
167 initrd = files[0]
169 if not initrd or not os.path.exists(initrd):
171 initrd = "%s/initrd.cpio.gz" % cr_workdir
195 return initrd
274 initrd = source_params['initrd']
277 cp_cmd = "cp %s/%s %s" % (deploy_dir, initrd, cr_workdir)
281 initrd = "%s/initrd" % deploy_dir
282 if not os.path.isfile(initrd):
[all …]
/OK3568_Linux_fs/kernel/arch/arm/boot/bootp/
H A Dinit.S24 bl move @ move the initrd
30 ldmia r13, {r5-r9} @ get size and addr of initrd
33 @ r7 = initrd start
34 @ r8 = initrd end
56 mov r5, #4 @ Size of initrd tag (4 words)
76 data: .word initrd_start @ source initrd address
77 .word initrd_phys @ destination initrd address
78 .word initrd_size @ initrd size
/OK3568_Linux_fs/kernel/arch/um/kernel/
H A Dinitrd.c14 static char *initrd __initdata = NULL;
23 if (initrd == NULL) in read_initrd()
26 err = os_file_size(initrd, &size); in read_initrd()
35 printk(KERN_ERR "\"%s\" is a zero-size initrd\n", initrd); in read_initrd()
43 if (load_initrd(initrd, area, size) == -1) in read_initrd()
53 initrd = line; in uml_initrd_setup()
/OK3568_Linux_fs/kernel/Documentation/power/
H A Dswsusp-dmcrypt.rst13 You did read Documentation/admin-guide/initrd.rst and know how an initrd works.
14 You know how to create or how to modify an initrd.
19 an initrd that does your current crypto setup already.
25 or an usb stick prior to resume. So you need an initrd, that sets
31 always the same major/minor within the initrd as well as
43 Prepare your boot loader to use the initrd you will create or
48 initrd=/boot/initrd.gz
52 Finally you need to create or modify your initrd. Lets assume
53 you create an initrd that reads the required dm-crypt setup
57 named "swapkey". /etc/fstab of your initrd contains something
[all …]
/OK3568_Linux_fs/yocto/poky/meta/classes/
H A Dlive-vm-common.bbclass56 if [ -f "$iso_dir/initrd" ] ; then
57 cp $iso_dir/initrd ${EFIIMGDIR}
72 # Install bzImage, initrd, and rootfs.img in DEST for all loaders to use.
80 # initrd is made of concatenation of multiple filesystem images
82 rm -f $dest/initrd
86 cat $fs >> $dest/initrd
88 bbfatal "$fs is invalid. initrd image creation failed."
91 chmod 0644 $dest/initrd
H A Dsystemd-boot-cfg.bbclass58 initrd = localdata.getVar('INITRD')
60 if initrd:
61 entrycfg.write('initrd /initrd\n')
H A Dgrub-efi-cfg.bbclass10 # ${INITRD} - indicates a list of filesystem images to concatenate and use as an initrd (optional)
108 initrd = localdata.getVar('INITRD')
117 if initrd:
118 cfgfile.write('initrd /initrd')
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-core/plymouth/
H A Dplymouth_0.9.5.bb36 PACKAGECONFIG ??= "pango initrd"
43 PACKAGECONFIG[initrd] = ",,,"
55 if ! ${@bb.utils.contains('PACKAGECONFIG', 'initrd', 'true', 'false', d)}; then
60 PACKAGES =. "${@bb.utils.contains('PACKAGECONFIG', 'initrd', '${PN}-initrd ', '', d)}"
63 FILES:${PN}-initrd = "${libexecdir}/plymouth/*"
70 RDEPENDS:${PN}-initrd = "bash dracut"
/OK3568_Linux_fs/kernel/arch/powerpc/boot/
H A DREADME2 To extract the kernel vmlinux, System.map, .config or initrd from the zImage binary:
7 objcopy -j .kernel:initrd -O binary zImage.initrd initrd.gz
H A Dwrapper39 initrd=
104 initrd="$1"
228 isection=.kernel:initrd
275 isection=initrd
314 isection=.kernel:initrd
447 if [ -n "$initrd" ]; then
448 real_rd="$initrd"
455 if [ -z "$initrd" ]; then
476 if [ -n "$initrd" ]; then
477 addsec $tmp "$initrd" $isection
/OK3568_Linux_fs/kernel/Documentation/x86/
H A Dmicrocode.rst24 The microcode is stored in an initrd file. During boot, it is read from
27 The format of the combined initrd image is microcode in (uncompressed)
28 cpio format followed by the (possibly compressed) initrd image. The
29 loader parses the combined initrd image during boot.
39 scans the microcode file in the initrd. If microcode matching the
47 Here's a crude example how to prepare an initrd with microcode (this is
49 initrd, so you don't really have to do it yourself. It is documented
56 echo "You need to supply an initrd file"
63 TMPDIR=/tmp/initrd
/OK3568_Linux_fs/yocto/poky/meta/recipes-core/os-release/
H A Dos-release.bb53 ln -rs ${D}${nonarch_libdir}/os-release ${D}${sysconfdir}/initrd-release
58 PACKAGES += "${PN}-initrd"
59 FILES:${PN}-initrd = "${sysconfdir}/initrd-release"
60 RDEPENDS:${PN}-initrd += "${PN}"
/OK3568_Linux_fs/u-boot/doc/uImage.FIT/
H A Dcommand_syntax_extensions.txt55 kernel and a ramdisk, respectively. The kernel is booted with initrd loaded
61 | (kernel, initrd) | (kernel, initrd, fdt) |
66 Ad. 4. Similar to case 3, but the kernel is booted without initrd. Second
70 Ad. 5. Boot kernel image located at <addr1> with initrd loaded with ramdisk
76 booted with initrd loaded with ramdisk from the image at <addr2>.
80 a FDT binary blob. Kernel is booted without initrd.
97 at <addr1> with initrd loaded with ramdisk <subimg2> from the image at
102 at <addr1> with initrd loaded with ramdisk <subimg2> from the image at
111 at <addr1>, without initrd, and pass FDT blob <subimg3> from the image at
151 - boot "kernel@1" from a new uImage at 200000 with initrd "ramdisk@2" found in
[all …]
/OK3568_Linux_fs/u-boot/arch/sh/lib/
H A Dbootm.c32 #define GET_INITRD_START(initrd, linux) (initrd - linux + CONFIG_SH_SDRAM_OFFSET) argument
34 #define GET_INITRD_START(initrd, linux) (initrd - linux) argument
/OK3568_Linux_fs/yocto/poky/scripts/pybootchartgui/
H A DNEWS51 + better check for initrd (Riccardo Magliocchetti)
116 + add rdinit support for very early initrd tracing
135 + if run inside an initrd detect when /dev is writable
153 + fix initrd sanity check to use the right proc path
158 + even simpler initrd setup
167 be present (also in the initrd) [ with a kmsg
191 + initrd portability & fixes (Federic Crozat)
195 + improved initrd detection / jail tagging
197 + implement a built-in usleep to help initrd deps (Michael)
200 + fix initrd bug
/OK3568_Linux_fs/kernel/arch/x86/boot/
H A Dgenimage.sh54 mcopy "$FDINITRD" a:initrd.img
66 mcopy "$FDINITRD" v:initrd.img
78 mcopy "$FDINITRD" w:initrd.img
115 cp "$FDINITRD" $tmp_dir/initrd.img
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/
H A Dchosen.txt124 linux,initrd-start and linux,initrd-end
127 These properties hold the physical start and end address of an initrd that's
128 loaded by the bootloader. Note that linux,initrd-start is inclusive, but
129 linux,initrd-end is exclusive.
134 linux,initrd-start = <0x82000000>;
135 linux,initrd-end = <0x82800000>;
/OK3568_Linux_fs/yocto/meta-openembedded/meta-initramfs/recipes-kernel/kexec/kexec-tools-klibc/
H A D140-mips_disable_devicetree_support.patch41 - {"initrd", 1, 0, OPT_RAMDISK },
42 + {"initrd", 1, 0, OPT_RAMDISK }, \
82 - /* Create initrd entries in dtb - although at this time
92 + /* Create initrd entries in dtb - although at this time
96 - /* Now that the buffer for initrd is prepared, update the dtb
105 + /* Now that the buffer for initrd is prepared, update the dtb
135 " --initrd=FILE Use FILE as initial ramdisk.\n"
/OK3568_Linux_fs/debian/
H A Dmk-iso-debian.sh30 cp $DEBIAN_DIR/install.a64/initrd.gz $INITRD/
32 gunzip initrd.gz --quiet
33 cpio -di < initrd
34 rm initrd
43 find . | cpio --quiet -o -H newc --owner 0:0 | gzip > $DEBIAN_DIR/install.a64/initrd.gz
/OK3568_Linux_fs/buildroot/fs/iso9660/
H A DConfig.in18 optionally an external initrd image. In this case, the
66 initrd images respectively.
69 bool "Use initrd"
74 initrd/initramfs rather than directly as the ISO9660
76 contain a kernel image, an initrd image (unless an initramfs

12345678910>>...26