minix/u-boot
1
0
Fork 0
mirror of https://github.com/Stichting-MINIX-Research-Foundation/u-boot.git synced 2025-09-10 12:39:22 -04:00
Code Issues Packages Projects Releases Wiki Activity

[new uImage] Fix *.its files location in documentation

Browse Source 
Signed-off-by: Bartlomiej Sieka <tur@semihalf.com>
This commit is contained in:
Bartlomiej Sieka 2008-03-20 23:10:19 +01:00
parent 5e339fd9ed
commit 43142e817f
2 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
doc/uImage.FIT/howto.txt
View File

@ -49,10 +49,11 @@ Consider a simple scenario, where a PPC Linux kernel built from sources on the
development host is to be booted old-style (non-FDT) by U-Boot on an embedded development host is to be booted old-style (non-FDT) by U-Boot on an embedded
target. Assume that the outcome of the build is vmlinux.bin.gz, a file which target. Assume that the outcome of the build is vmlinux.bin.gz, a file which
contains a gzip-compressed PPC Linux kernel (the only data file in this case). contains a gzip-compressed PPC Linux kernel (the only data file in this case).
The uImage can be produced using the image source file examples/kernel.its The uImage can be produced using the image source file
(note that kernel.its assumes that vmlinux.bin.gz is in the current working doc/uImage.FIT/kernel.its (note that kernel.its assumes that vmlinux.bin.gz is
directory; if desired, an alternative path can be specified in the kernel.its in the current working directory; if desired, an alternative path can be
file). Here's how to create the image and inspect its contents: specified in the kernel.its file). Here's how to create the image and inspect
its contents:
[on the host system] [on the host system]
$ mkimage -f kernel.its kernel.itb $ mkimage -f kernel.its kernel.itb
@ -159,10 +160,10 @@ Example 2 -- new-style (FDT) kernel booting
Consider another simple scenario, where a PPC Linux kernel is to be booted Consider another simple scenario, where a PPC Linux kernel is to be booted
new-style, i.e., with a FDT blob. In this case there are two prerequisite data new-style, i.e., with a FDT blob. In this case there are two prerequisite data
files: vmlinux.bin.gz (Linux kernel) and target.dtb (FDT blob). The uImage can files: vmlinux.bin.gz (Linux kernel) and target.dtb (FDT blob). The uImage can
be produced using image source file examples/kernel_fdt.its like this (note be produced using image source file doc/uImage.FIT/kernel_fdt.its like this
again, that both prerequisite data files are assumed to be present in the (note again, that both prerequisite data files are assumed to be present in
current working directory -- image source file kernel_fdt.its can be modified the current working directory -- image source file kernel_fdt.its can be
to take the files from some other location if needed): modified to take the files from some other location if needed):
[on the host system] [on the host system]
$ mkimage -f kernel_fdt.its kernel_fdt.itb $ mkimage -f kernel_fdt.its kernel_fdt.itb
@ -292,5 +293,5 @@ Bytes transferred = 1109776 (10ef10 hex)
Example 3 -- advanced booting Example 3 -- advanced booting
----------------------------- -----------------------------
Refer to examples/multi.its for an image source file that allows more Refer to doc/uImage.FIT/multi.its for an image source file that allows more
sophisticated booting scenarios (multiple kernels, ramdisks and fdt blobs). sophisticated booting scenarios (multiple kernels, ramdisks and fdt blobs).

2
doc/uImage.FIT/source_file_format.txt
View File

@ -259,4 +259,4 @@ not* be specified in a configuration node.
8) Examples 8) Examples
----------- -----------
Please see examples/*.its for actual image source files. Please see doc/uImage.FIT/*.its for actual image source files.