| 7eb2c8d5 | 20-Apr-2013 |
Simon Glass <sjg@chromium.org> |
sandbox: fs: Add support for saving files to host filesystem
This allows write of files from the host filesystem in sandbox. There is currently no concept of overwriting the file and removing its ex
sandbox: fs: Add support for saving files to host filesystem
This allows write of files from the host filesystem in sandbox. There is currently no concept of overwriting the file and removing its existing contents - all writing is done on top of what is there. This means that writing 10 bytes to the start of a 1KB file will only update those 10 bytes, not truncate the file to 10 byte slong.
If the file does not exist it is created.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 4ca30d60 | 20-Apr-2013 |
Simon Glass <sjg@chromium.org> |
sandbox: Support 'source' command
Enhance the source command to work with sandbox, by using map_sysmem() to convert a ulong address into a pointer.
Signed-off-by: Simon Glass <sjg@chromium.org> |
| 095686d3 | 20-Apr-2013 |
Simon Glass <sjg@chromium.org> |
Revert "fdt- Tell the FDT library where the device tree is"
This reverts commit 3b73459ea3421e9f8c6c8c62e1d3fe458ca5bc56.
In practice it doesn't seem like a good idea to make the the working FDT po
Revert "fdt- Tell the FDT library where the device tree is"
This reverts commit 3b73459ea3421e9f8c6c8c62e1d3fe458ca5bc56.
In practice it doesn't seem like a good idea to make the the working FDT point to the control FDT. Now that we can access the control FDT using the 'fdt' command, there is no need for this feature. Remove it.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| a92fd657 | 20-Apr-2013 |
Simon Glass <sjg@chromium.org> |
sandbox: fdt: Support fdt command for sandbox
By using map_sysmem() we can get the fdt command to work correctly with sandbox.
Signed-off-by: Simon Glass <sjg@chromium.org> |
| 4b578655 | 20-Apr-2013 |
Simon Glass <sjg@chromium.org> |
fdt: Allow fdt command to check and update control FDT
There is an existing fdt command to deal with the working FDT. Enhance this to support the control FDT also (CONFIG_OF_CONTROL).
Signed-off-by
fdt: Allow fdt command to check and update control FDT
There is an existing fdt command to deal with the working FDT. Enhance this to support the control FDT also (CONFIG_OF_CONTROL).
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 76b8f79c | 20-Apr-2013 |
Simon Glass <sjg@chromium.org> |
Add getenv_hex() to return an environment variable as hex
This conversion is required in a number of places in U-Boot. Add a standard function to provide this feature, so we avoid all the different
Add getenv_hex() to return an environment variable as hex
This conversion is required in a number of places in U-Boot. Add a standard function to provide this feature, so we avoid all the different variations in the way it is coded.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| d14da913 | 20-Apr-2013 |
Simon Glass <sjg@chromium.org> |
fdt: Add a parameter to fdt_valid()
At present this only checks working_fdt, but we want to check other FDTs also. So add the FDT to check as a parameter to fdt_valid().
Signed-off-by: Simon Glass
fdt: Add a parameter to fdt_valid()
At present this only checks working_fdt, but we want to check other FDTs also. So add the FDT to check as a parameter to fdt_valid().
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| f828bf25 | 20-Apr-2013 |
Simon Glass <sjg@chromium.org> |
sandbox: Add CONFIG_OF_HOSTFILE to read FDT from host file
With sandbox it is tricky to add an FDT to the image at build time (or later) since we build an ELF file, not a plain binary, and the addre
sandbox: Add CONFIG_OF_HOSTFILE to read FDT from host file
With sandbox it is tricky to add an FDT to the image at build time (or later) since we build an ELF file, not a plain binary, and the address space of the whole U-Boot is not accessible in the emulated memory map of sandbox.
Sandbox can read files directly from the host, though, so add an option to read an FDT from a host file on start-up.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| a733b06b | 26-Apr-2013 |
Simon Glass <sjg@chromium.org> |
sandbox: Switch over to generic board
Add generic board support for sandbox. and remove the old board init code.
Select CONFIG_SYS_GENERIC_BOARD for sandbox now that this is supported.
Signed-off-
sandbox: Switch over to generic board
Add generic board support for sandbox. and remove the old board init code.
Select CONFIG_SYS_GENERIC_BOARD for sandbox now that this is supported.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@ti.com>
show more ...
|
| ccca7dfd | 23-Apr-2013 |
Benoît Thébaudeau <benoit.thebaudeau@advansee.com> |
Add fuse API and commands
This can be useful for fuse-like hardware, OTP SoC options, etc.
Signed-off-by: Benoît Thébaudeau <benoit.thebaudeau@advansee.com> |
| 352ef3f1 | 04-Apr-2013 |
Stefan Roese <sr@denx.de> |
flash: Add optional verify-after-write feature
Sometimes it might make sense to verify the written data to NOR flash. This patch adds this feature. To enable this verify-after-write, you need to def
flash: Add optional verify-after-write feature
Sometimes it might make sense to verify the written data to NOR flash. This patch adds this feature. To enable this verify-after-write, you need to define CONFIG_FLASH_VERIFY in your board config header.
Please note that this option is useless in nearly all cases, since such flash programming errors usually are detected earlier while unprotecting/erasing/programming. Please only enable this option if you really know what you are doing.
Signed-off-by: Stefan Roese <sr@denx.de>
show more ...
|
| 64f4a619 | 29-Jan-2013 |
Jaehoon Chung <jh80.chung@samsung.com> |
mmc: support the correct card version for eMMC
eMMC vesrion is supported up to v4.5. But bootloader isn't saw the exact eMMC version. After applied this patch, if use the mmcinfo command, then can s
mmc: support the correct card version for eMMC
eMMC vesrion is supported up to v4.5. But bootloader isn't saw the exact eMMC version. After applied this patch, if use the mmcinfo command, then can see the exactly mmc version.
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com> Acked-by: Rommel Custodio <sessyargc@gmail.com>
show more ...
|
| 22a4a6c5 | 28-Sep-2012 |
Maxime Larocque <maxmtl2002@yahoo.ca> |
printenv: Correct out-of-memory condition check.
In common/cmd_nvedit.c, en env_print(), the wrong type is used for len. hexport_r() returns -1 on error (like OOM), which is converted to 0xffffffff
printenv: Correct out-of-memory condition check.
In common/cmd_nvedit.c, en env_print(), the wrong type is used for len. hexport_r() returns -1 on error (like OOM), which is converted to 0xffffffff when put in an unsigned. Said value is obviously bigger then 0, and as a result an uninitialized string is then displayed. Other usages of hexport_r() in the code correctly uses ssize_t to keep its return value.
Signed-off-by: Maxime Larocque <maxmtl2002@yahoo.ca>
show more ...
|
| 7525c2da | 15-Apr-2013 |
Simon Glass <sjg@chromium.org> |
x86: Allow setup code to manage its own global data
Currently x86 has its own means of managing the global data and board data (bd_t), and this code resides in start.S. With generic board, we need t
x86: Allow setup code to manage its own global data
Currently x86 has its own means of managing the global data and board data (bd_t), and this code resides in start.S. With generic board, we need to ensure that we leave this alone - i.e. don't clear it as we do on other archs.
This fixes a problem where the memory init data is cleared which causes the video driver to operate very slowly.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 8b42dfc3 | 15-Apr-2013 |
Simon Glass <sjg@chromium.org> |
x86: Fix DRAM bank size init with generic board
The intention of the memory init code is that it should work the same with CONFIG_SYS_GENERIC_BOARD and without. This is tricky because dram_init() is
x86: Fix DRAM bank size init with generic board
The intention of the memory init code is that it should work the same with CONFIG_SYS_GENERIC_BOARD and without. This is tricky because dram_init() is called prior to relocation with generic board (matching other archs) and after relocation without generic board.
Adjust the init sequence so that dram_init() is not called in the generic board case, which seems like the easiest fix for now. Also ensure that relocation addresses are still calculated.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 17059f97 | 15-Apr-2013 |
Tom Rini <trini@ti.com> |
Merge branch 'master' of git://git.denx.de/u-boot-arm |
| 8732b070 | 28-Feb-2013 |
Che-liang Chiou <clchiou@chromium.org> |
tpm: Add TPM command library
TPM command library implements a subset of TPM commands defined in TCG Main Specification 1.2 that are useful for implementing secure boot. More TPM commands could be ad
tpm: Add TPM command library
TPM command library implements a subset of TPM commands defined in TCG Main Specification 1.2 that are useful for implementing secure boot. More TPM commands could be added out of necessity.
You may exercise these commands through the 'tpm' command. However, the raw TPM commands are too primitive for writing secure boot in command interpreter scripts; so the 'tpm' command also provides helper functions to make scripting easier.
For example, to define a counter in TPM non-volatile storage and initialize it to zero:
$ tpm init $ tpm startup TPM_ST_CLEAR $ tpm nv_define d 0x1001 0x1 $ tpm nv_write d 0x1001 0
And then increment the counter by one:
$ tpm nv_read d 0x1001 i $ setexpr.l i $i + 1 $ tpm nv_write d 0x1001 $i
Signed-off-by: Che-Liang Chiou <clchiou@chromium.org>
show more ...
|
| 18122019 | 12-Apr-2013 |
Albert ARIBAUD <albert.u.boot@aribaud.net> |
Merge branch 'u-boot/master' into 'u-boot-arm/master'
Conflicts: drivers/video/exynos_fb.c |
| 785881f7 | 08-Apr-2013 |
Joe Hershberger <joe.hershberger@ni.com> |
env: Add redundant env support to UBI env
Allow the user to specify two UBI volumes to use for the environment
Signed-off-by: Joe Hershberger <joe.hershberger@ni.com> |
| 2b74433f | 08-Apr-2013 |
Joe Hershberger <joe.hershberger@ni.com> |
env: Add support for UBI environment
UBI is a better place for the environment on NAND devices because it handles wear-leveling and bad blocks.
Gluebi is needed in Linux to access the env as an MTD
env: Add support for UBI environment
UBI is a better place for the environment on NAND devices because it handles wear-leveling and bad blocks.
Gluebi is needed in Linux to access the env as an MTD partition.
Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
show more ...
|
| a7eb1d66 | 08-Apr-2013 |
Joe Hershberger <joe.hershberger@ni.com> |
mtd: Make mtdparts work with pre-reloc env
The env in UBI needs to look up the mtd partition as part of relocation, which happens before relocation. Make the mtdparts code capable of working on the
mtd: Make mtdparts work with pre-reloc env
The env in UBI needs to look up the mtd partition as part of relocation, which happens before relocation. Make the mtdparts code capable of working on the default env to start with.
The code tries to set values in the env as well, but again, the env isn't there yet, so add a check to setenv to not allow sets before the env is relocated.
Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
show more ...
|
| 147162da | 08-Apr-2013 |
Joe Hershberger <joe.hershberger@ni.com> |
ubi: ubifs: Turn off verbose prints
The prints are out of control. SILENCE!
Signed-off-by: Joe Hershberger <joe.hershberger@ni.com> |
| 71829067 | 08-Apr-2013 |
Joe Hershberger <joe.hershberger@ni.com> |
ubi: Expose a few simple functions from the cmd_ubi
Part, Read, and Write functionality that will be used by env_ubi.
Signed-off-by: Joe Hershberger <joe.hershberger@ni.com> |
| 3d389101 | 09-Apr-2013 |
Vadim Bendebury <vbendeb@chromium.org> |
Do not call board_early_init_f() twice
Apparently due to a missed rebase conflict resolution board_early_init_f() is included twice in the list of initialization functions.
Leave only the first occ
Do not call board_early_init_f() twice
Apparently due to a missed rebase conflict resolution board_early_init_f() is included twice in the list of initialization functions.
Leave only the first occurrence. . built and boot an Exynos 5250 target
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
show more ...
|
| c4df2f41 | 14-Mar-2013 |
Tom Rini <trini@ti.com> |
cmd_nand.c: Fix CONFIG_CMD_NAND_YAFFS
The flag changed from WITH_INLINE_OOB to WITH_YAFFS_OOB by accident in 418396e.
Signed-off-by: Tom Rini <trini@ti.com> |