Home
last modified time | relevance | path

Searched refs:kernel (Results 1 – 25 of 271) sorted by relevance

1234567891011

/rk3399_rockchip-uboot/doc/uImage.FIT/
H A Dkernel.its2 * Simple U-Boot uImage source file containing a single kernel
8 description = "Simple image with single Linux kernel";
12 kernel@1 {
13 description = "Vanilla Linux kernel";
15 type = "kernel";
33 description = "Boot Linux kernel";
34 kernel = "kernel@1";
46 description = "Simple image with single Linux kernel on x86";
50 kernel@1 {
51 description = "Vanilla Linux kernel";
[all …]
H A Dsign-configs.its4 description = "Chrome OS kernel image with one or more FDT blobs";
8 kernel@1 {
9 data = /incbin/("test-kernel.bin");
16 kernel-version = <1>;
23 data = /incbin/("sandbox-kernel.dtb");
36 kernel = "kernel@1";
41 sign-images = "fdt", "kernel";
H A Doverlay-fdt-boot.txt7 of similar boards and their expansion options. The same kernel on DT enabled
27 kernel@1 {
29 type = "kernel";
70 kernel = "kernel@1";
74 kernel = "kernel@1";
78 kernel = "kernel@1";
82 kernel = "kernel@1";
86 kernel = "kernel@1";
90 kernel = "kernel@1";
114 being passed to the booting kernel. This saves on space and avoid the combinatorial
[all …]
H A Dkernel_fdt.its2 * Simple U-Boot uImage source file containing a single kernel and FDT blob
8 description = "Simple image with single Linux kernel and FDT blob";
12 kernel@1 {
13 description = "Vanilla Linux kernel";
15 type = "kernel";
46 description = "Boot Linux kernel with FDT blob";
47 kernel = "kernel@1";
H A Dmulti.its12 kernel@1 {
15 type = "kernel";
29 kernel@2 {
32 type = "kernel";
43 kernel@3 {
46 type = "kernel";
115 kernel = "kernel@1";
122 kernel = "kernel@2";
129 kernel = "kernel@3";
H A Dsign-images.its4 description = "Chrome OS kernel image with one or more FDT blobs";
8 kernel@1 {
9 data = /incbin/("test-kernel.bin");
16 kernel-version = <1>;
24 data = /incbin/("sandbox-kernel.dtb");
38 kernel = "kernel@1";
H A Dcommand_syntax_extensions.txt17 Linux kernel. The purpose of the following list is to document a complete list
20 Note: U-Boot supports two methods of booting a PowerPC Linux kernel: old way,
22 kernel is passed a pointer to the FDT. The boot method is indicated for each
51 Ad. 2. Boot kernel image located at <addr1>.
55 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
74 Ad. 6. <addr1> is the address of a kernel image, <addr2> is the address of a
79 Ad. 7. <addr1> is the address of a kernel image and <addr3> is the address of
[all …]
H A Dhowto.txt11 types (kernel, ramdisk, etc.), it also enhances integrity protection of images
20 git://git.kernel.org/pub/scm/utils/dtc/dtc.git
27 the uImage (kernel, ramdisk, etc.) is specified in the image source file in the
30 contains all the referenced data (kernel, ramdisk, etc.) and other information
69 Example 1 -- old-style (non-FDT) kernel booting
72 Consider a simple scenario, where a PPC Linux kernel built from sources on the
75 contains a gzip-compressed PPC Linux kernel (the only data file in this case).
77 doc/uImage.FIT/kernel.its (note that kernel.its assumes that vmlinux.bin.gz is
79 specified in the kernel.its file). Here's how to create the image and inspect
83 $ mkimage -f kernel.its kernel.itb
[all …]
H A Dbeaglebone_vboot.txt21 U-Boot has its device tree packaged wtih it, and the kernel's device tree is
22 packaged with the kernel. In particular this is important with verified boot,
26 everything verifies. On the other hand the kernel's device tree typically
27 changes when the kernel changes, so it is useful to package an updated device
28 tree with the kernel binary. U-Boot supports the latter with its flexible FIT
39 2. Obtain a suitable Linux kernel
42 kernel to be packaged, compressed and signed.
46 5. Sign the kernel
50 7. Put U-Boot and the kernel onto the board
59 this for U-Boot and also for the kernel if you build it. For example if you
[all …]
H A Dmulti-with-loadables.its16 type = "kernel";
54 type = "kernel";
71 kernel = "linux_kernel@1";
77 kernel = "xen_kernel@1";
84 kernel = "xen_kernel@1";
H A Dx86-fit-boot.txt11 binary for the kernel itself, often with a small built-in serial driver to
22 mode was something of a challenge, so putting this logic in the kernel seemed
47 the kernel. It might be easier to just provide that information in the image,
51 As a result, the x86 kernel boot process is needlessly complex. The file
54 so prevalent that is actually isn't possible to produce the 'raw' kernel build
63 Build the kernel
66 Note: these instructions assume a 32-bit kernel. U-Boot also supports directly
67 booting a 64-bit kernel by jumping into 64-bit mode first (see below).
69 You can build the kernel as normal with 'make'. This will create a file called
153 line and various settings need by the kernel. Arguably the boot loader should
[all …]
H A Dsource_file_format.txt10 Evolution of the 2.6 Linux kernel for embedded PowerPC systems introduced new
12 kernel in the form of Flattened Device Tree.
50 To avoid confusion with the kernel FDT the following naming convention is
131 single component sub-image (like kernel, ramdisk, etc.). At least one
162 "standalone", "kernel", "kernel_noload", "ramdisk", "firmware", "script",
170 - os : OS name, mandatory for types "kernel" and "ramdisk". Valid OS names
174 - arch : Architecture name, mandatory for types: "standalone", "kernel",
181 "standalone" and "kernel".
183 property of the root node. Mandatory for types: "standalone" and "kernel".
207 convenient, labeled boot configurations, which combine together kernel images
[all …]
/rk3399_rockchip-uboot/test/py/tests/vboot/
H A Dsign-configs-sha256.its4 description = "Chrome OS kernel image with one or more FDT blobs";
8 kernel@1 {
9 data = /incbin/("test-kernel.bin");
16 kernel-version = <1>;
23 data = /incbin/("sandbox-kernel.dtb");
36 kernel = "kernel@1";
41 sign-images = "fdt", "kernel";
H A Dsign-configs-sha1.its4 description = "Chrome OS kernel image with one or more FDT blobs";
8 kernel@1 {
9 data = /incbin/("test-kernel.bin");
16 kernel-version = <1>;
23 data = /incbin/("sandbox-kernel.dtb");
36 kernel = "kernel@1";
41 sign-images = "fdt", "kernel";
H A Dsign-images-sha256.its4 description = "Chrome OS kernel image with one or more FDT blobs";
8 kernel@1 {
9 data = /incbin/("test-kernel.bin");
16 kernel-version = <1>;
24 data = /incbin/("sandbox-kernel.dtb");
38 kernel = "kernel@1";
H A Dsign-images-sha1.its4 description = "Chrome OS kernel image with one or more FDT blobs";
8 kernel@1 {
9 data = /incbin/("test-kernel.bin");
16 kernel-version = <1>;
24 data = /incbin/("sandbox-kernel.dtb");
38 kernel = "kernel@1";
/rk3399_rockchip-uboot/scripts/
H A Drepack-bootimg8 usage: $0 [-h] [-z] --boot_img BOOT_IMG [--out OUT] [--kernel KERNEL] [--ramdisk RAMDISK] [--second…
12 -z pack compressed kernel image
15 --kernel KERNEL path to the new kernel
37 --kernel)
38 kernel=$2
99 if [ "$kernel" == "" ]; then
100 kernel=${kernel-$out/kernel}
144 --kernel $kernel \
H A Dandroid2distro.sh55 BOOTARGS=`fdtget -ts distro/rk-kernel.dtb /chosen bootargs`
57 cp distro/rk-kernel.dtb boot/rk-kernel.dtb
58 cp distro/kernel boot/kernel
/rk3399_rockchip-uboot/doc/
H A DREADME.nokia_rx518 NOLO is expecting a kernel image and will treat any image it finds in
10 a kernel. In order to transparently boot the original kernel, it will be
16 the appended kernel image will be booted using some generated and some
23 but is disabled because it prevents the current Maemo kernel from booting.
30 * 0. if keyboard is closed boot automatically attached kernel image
33 * 3. try boot from attached kernel image
53 * run attachboot - Boot attached kernel image (attached to U-Boot binary)
57 * run kernload - Load kernel image ${mmckernfile}
59 * run kernboot - Boot loaded kernel image
60 * run kerninitrdboot - Boot loaded kernel image with loaded initrd image
[all …]
H A DREADME.vxworks11 This document describes the information about U-Boot loading VxWorks kernel.
16 For booting old kernels (6.9.x) on PowerPC and ARM, and all kernel versions
20 64-bit x86 kernel cannot be loaded as of today.
37 When booting new VxWorks kernel (uImage format), the parameters passed to bootm
40 bootm <kernel image address> - <device tree address>
44 When using 'bootvx', the kernel bootline must be prepared by U-Boot at a
52 location pointed by "bootaddr" as the kernel bootline. If "bootargs" is not
58 handle bootline fix up for the kernel dtb automatically.
70 Before loading an x86 kernel, two additional environment variables need to be
74 Check VxWorks kernel configuration to look for BIOS_E820_DATA_START and
[all …]
H A DREADME.falcon11 to boot a Linux kernel (or whatever image) without a full blown U-Boot.
21 The Falcon Mode extends this way allowing to start the Linux kernel directly
23 must pass to the kernel, using ATAGS or Device Tree.
26 loading the kernel, passing to Linux the address in memory where
29 informed to load it before running the kernel.
31 To boot the kernel, these steps under a Falcon-aware U-Boot are required:
34 After loading the desired legacy-format kernel image into memory (and DT as
35 well, if used), use the "spl export" command to generate the kernel parameters
36 area or the DT. U-Boot runs as when it boots the kernel, but stops before
37 passing the control to the kernel.
[all …]
/rk3399_rockchip-uboot/arch/m68k/lib/
H A Dbootm.c55 void (*kernel) (bd_t *, ulong, ulong, ulong, ulong); in do_bootm_linux() local
79 kernel = (void (*)(bd_t *, ulong, ulong, ulong, ulong))images->ep; in do_bootm_linux()
82 (ulong) kernel); in do_bootm_linux()
95 (*kernel)(kbd, images->initrd_start, images->initrd_end, in do_bootm_linux()
/rk3399_rockchip-uboot/arch/arm/mach-rockchip/
H A Dmake_fit_boot.sh16 gzip -k -f -9 ${srctree}/images/kernel
19 ${srctree}/scripts/compress.sh lz4 ${srctree}/images/kernel
56 kernel {
98 kernel = "kernel";
/rk3399_rockchip-uboot/doc/chromium/
H A Dchromebook_jerry.its8 kernel@1 {
38 kernel = "kernel@1";
H A Dnyan-big.its8 kernel@1 {
38 kernel = "kernel@1";

1234567891011