Blame view
doc/README.ext4
2.21 KB
28983f4b1
|
1 2 |
U-Boot supports access of both ext2 and ext4 filesystems, either in read-only mode or in read-write mode. |
ed34f34db
|
3 |
|
28983f4b1
|
4 5 |
First, to enable support for both ext4 (and, automatically, ext2 as well), but without selecting the corresponding commands, use one of: |
03e2ecf6b
|
6 |
|
28983f4b1
|
7 8 |
#define CONFIG_FS_EXT4 (for read-only) #define CONFIG_EXT4_WRITE (for read-write) |
03e2ecf6b
|
9 |
|
28983f4b1
|
10 |
Next, to select the ext2-related commands: |
ed34f34db
|
11 |
|
28983f4b1
|
12 13 |
* ext2ls * ext2load |
ed34f34db
|
14 |
|
28983f4b1
|
15 |
or ext4-related commands: |
03e2ecf6b
|
16 |
|
28983f4b1
|
17 18 19 |
* ext4size * ext4ls * ext4load |
ed34f34db
|
20 |
|
28983f4b1
|
21 |
use one or both of: |
ed34f34db
|
22 |
|
28983f4b1
|
23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 |
#define CONFIG_CMD_EXT2 #define CONFIG_CMD_EXT4 Selecting either of the above automatically defines CONFIG_FS_EXT4 if it wasn't defined already. In addition, to get the write access command "ext4write", use: #define CONFIG_CMD_EXT4_WRITE which automatically defines CONFIG_EXT4_WRITE if it wasn't defined already. Also relevant are the generic filesystem commands, selected by: #define CONFIG_CMD_FS_GENERIC This does not automatically enable EXT4 support for you, you still need to do that yourself. Some sample commands to test ext4 support: |
ed34f34db
|
44 |
|
28983f4b1
|
45 46 47 48 |
1. Check that the commands can be seen in the output of U-Boot help: UBOOT #help ... |
93e145964
|
49 50 |
ext4load- load binary file from a Ext4 file system ext4ls - list files in a directory (default /) |
28983f4b1
|
51 |
ext4size - determine a file's size |
93e145964
|
52 |
ext4write- create a file in ext4 formatted partition |
28983f4b1
|
53 54 55 |
... 2. To list the files in an ext4-formatted partition, run: |
ed34f34db
|
56 |
|
93e145964
|
57 |
ext4ls <interface> <dev[:part]> [directory] |
28983f4b1
|
58 |
|
93e145964
|
59 60 |
For example: UBOOT #ext4ls mmc 0:5 /usr/lib |
ed34f34db
|
61 |
|
28983f4b1
|
62 |
3. To read and load a file from an ext4-formatted partition to RAM, run: |
93e145964
|
63 |
ext4load <interface> <dev[:part]> [addr] [filename] [bytes] |
28983f4b1
|
64 |
|
93e145964
|
65 66 |
For example: UBOOT #ext4load mmc 2:2 0x30007fc0 uImage |
ed34f34db
|
67 |
|
28983f4b1
|
68 |
4. To write a file to an ext4-formatted partition. |
93e145964
|
69 |
a) First load a file to RAM at a particular address for example 0x30007fc0. |
28983f4b1
|
70 |
Now execute ext4write command: |
93e145964
|
71 |
ext4write <interface> <dev[:part]> [filename] [Address] [sizebytes] |
28983f4b1
|
72 |
|
93e145964
|
73 74 75 76 |
For example: UBOOT #ext4write mmc 2:2 /boot/uImage 0x30007fc0 6183120 (here 6183120 is the size of the file to be written) Note: Absolute path is required for the file to be written |
ed34f34db
|
77 78 79 80 81 |
References : -- ext4 implementation in Linux Kernel -- Uboot existing ext2 load and ls implementation -- Journaling block device JBD2 implementation in linux Kernel |