- 12 6月, 2014 40 次提交
-
-
由 Stephen Warren 提交于
Currently, get_device()/get_dev_hwpart() for MMC devices does not select an explicit HW partition unless the user explicitly requests one, i.e. by requesting device "mmc 0.0" rather than just "mmc 0". I think it makes more sense if the default is to select HW partition 0 (main data area) if the user didn't request a specific partition. Otherwise, the following happens, which feels wrong: Select HW partition 1 (boot0): mmc dev 0 1 Attempts to access SW partition 1 on HW partition 1 (boot0), rather than SW partition 1 on HW partition 0 (main data area): ls mmc 0:1 / With this patch, the second command above re-selects the main data area. Many device types don't support HW partitions at all, so if HW partition 0 is selected (either explicitly or as the default) and there's no select_hwpart function, we simply skip attempting to select a HW partition. Some MMC devices (i.e. SD cards) don't support HW partitions. However, this patch still works, since mmc_start_init() sets the current partition number to 0, and mmc_select_hwpart() succeeds if the requested partition is already selected. Signed-off-by: NStephen Warren <swarren@nvidia.com> Acked-by: NPantelis Antoniou <panto@antoniou-consulting.com>
-
由 Stephen Warren 提交于
Currently, "mmc dev 0" does not change the selected HW partition. I think it makes more sense if "mmc dev 0" is an alias for "mmc dev 0 0", i.e. that HW partition 0 (main data area) is always selected by default if the user didn't request a specific partition. Otherwise, the following happens, which feels wrong: Select HW partition 1 (boot0): mmc dev 0 1 Doesn't change the HW partition, so it's still 1 (boot0): mmc dev 0 With this patch, the second command above re-selects the main data area. Note that some MMC devices (i.e. SD cards) don't support HW partitions. However, this patch still works, since mmc_start_init() sets the current partition number to 0, and mmc_select_hwpart() succeeds if the requested partition is already selected. Signed-off-by: NStephen Warren <swarren@nvidia.com> Acked-by: NPantelis Antoniou <panto@antoniou-consulting.com>
-
由 Stephen Warren 提交于
Rather than just returning -1 everywhere, try to return something meaningful from mmc_select_hwpart(). Note that most other MMC functions don't do this, including functions called from mmc_select_hwpart(), so I'm not sure how effective this will be. Still, it's one less place with hard-coded -1. Suggested-by: NPantelis Antoniou <panto@antoniou-consulting.com> Signed-off-by: NStephen Warren <swarren@nvidia.com> Acked-by: NPantelis Antoniou <panto@antoniou-consulting.com>
-
由 Jeroen Hofstee 提交于
To prevent a warning for clang the loop without a body is made more clear by moving it to a line of its own. This prevents a clang warning. cc: sbabic@denx.de Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>
-
由 Jeroen Hofstee 提交于
Clang interpretes an if condition like "if ((a = b) == NULL) as it tries to assign a value in a statement. Hence if you do "if ((something)) it warns you that you might be confused. Hence drop the double braces for plane if statements. Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>
-
由 Jeroen Hofstee 提交于
Clang interpretes an if condition like "if ((a = b) == NULL) as it tries to assign a value in a statement. Hence if you do "if ((something)) it warns you that you might be confused. Hence drop the double braces for plane if statements. cc: Holger Brunck <holger.brunck@keymile.com> Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>
-
由 Jeroen Hofstee 提交于
Clang interpretes an if condition like "if ((a = b) == NULL) as it tries to assign a value in a statement. Hence if you do "if ((something)) it warns you that you might be confused. Hence drop the double braces for plane if statements. Simon Glass <sjg@chromium.org> Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>
-
由 Jeroen Hofstee 提交于
It seems the code tries to trick the compiler the argument is actually used. However compilers became too smart to fool them so easily an now warn. Gcc and clang don't seem to emit a warning when the argument is unused. If so it should be decorated with unused / (void). Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>
-
由 Jeroen Hofstee 提交于
cc: Troy Kisky <troy.kisky@boundarydevices.com> Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>
-
由 Jeroen Hofstee 提交于
this prevent some warnings when compiling with clang cc: Stelian Pop <stelian@popies.net> Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>
-
由 Jeroen Hofstee 提交于
cc: Simon Glass <sjg@chromium.org> Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Vasili Galka 提交于
mkconfig links ${objtree}/include/asm/proc/ to ${srctree}/arch/${arch}/include/asm/proc-armv/. This seems to be a remnant from the past. Ever since its introduction in 2003 it is used only in ARM build and always links to same place, so let's simplify the code, remove it and reference directly where needed. Successful MAKEALL for ARM and PowerPC verified on Linux. Signed-off-by: NVasili Galka <vvv444@gmail.com>
-
由 Vasili Galka 提交于
Signed-off-by: NVasili Galka <vvv444@gmail.com>
-
由 Jeroen Hofstee 提交于
This prevents some warnings when building with clang. cc:: andreas.devel@googlemail.com Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>
-
由 Jeroen Hofstee 提交于
Since ALLOC_CACHE_ALIGN_BUFFER declares a char* for filename sizeof(filename) is not the size of the buffer. Use the already known length instead. cc: Uma Shankar <uma.shankar@samsung.com> cc: Manjunatha C Achar <a.manjunatha@samsung.com> cc: Marek Vasut <marek.vasut@gmail.com> Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl> Acked-by: NMarek Vasut <marex@denx.de>
-
由 Jeroen Hofstee 提交于
if algo->digest_size is zero nothing is set in the str_output buffer. An attempt is made to zero end the buffer, but the pointer to the buffer is set to zero instead. I am unaware if it causes any actual problems, but solves the following warning: common/hash.c:217:13: warning: expression which evaluates to zero treated as a null pointer constant of type 'char *' [-Wnon-literal-null-conversion] str_ptr = '\0'; ^~~~ cc: Simon Glass <sjg@chromium.org> Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>
-
由 Masahiro Yamada 提交于
All files under spl/ and tpl/ are generated during the build process except spl/Makefile. We can simplify clean-rule and git-ignore by moving spl/Makefile to somewhere else. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
-
由 Simon Glass 提交于
Most of the warnings seem to be related to using 'int' for size_t. Change this and fix up the remaining warnings and problems. For bootm, the warning was masked by others, and there is an actual bug in the code. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Chris Packham 提交于
Signed-off-by: NChris Packham <judge.packham@gmail.com>
-
由 Masahiro Yamada 提交于
GCC on Cygwin generates executables with .exe extension, for example: scripts/basic/fixdep.exe scripts/docproc.exe To ignore them, *.exe pattern should be moved from tools/.gitignore to ./.gitignore Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
-
由 Masahiro Yamada 提交于
"SFX = .exe" was originally added for Cygwin environment. It is true that GCC on Cygwin spits executables with .exe extention. For example, gcc -o foo foo.c will generate "foo.exe", not "foo". But GNU make is also nicely adjusted for Cygwin. For example, foo: foo.c gcc -o $@ $< will compare the timestamp between "foo.exe" and "foo.c". You do not have to tweak Makefiles like this: foo$(SFX): foo.c gcc -o $@ $< And "make clean" works as well without adjustment for Cygwin because the command "rm foo" on Cygwin will delete both "foo" and "foo.exe". In conclusion, makefiles do not need special care for Cygwin. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
-
由 Masahiro Yamada 提交于
This pattern was added by commit cc4f427b to ignore the intermidiate file for generating DTB. When Kbuild was introduced, dts/Makefile was totally re-written. This ignore pattern is already useless. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
-
由 Masahiro Yamada 提交于
There are many source files shared between U-boot image and tools. Instead of adding a lot of dummy wrapper files that just include the corresponding file in lib/ or common/ directory, Makefile should automatically generate them. The original inspiration for this came from scripts/Makefile.asm-generic of Linux Kernel. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Acked-by: NSimon Glass <sjg@chromium.org> Tested-by: NSimon Glass <sjg@chromium.org>
-
由 Darwin Dingel 提交于
Bug: SDCard with a messed up partition but still has a FAT signature intact is readable in Linux but unreadable in uboot with 'fatls'. Fix: When partition info checking fails, there is no checking for a FAT signature (DOS_PBR) which will fail 'fatls'. FAT signature checking is done when no valid partition is found in partition table. If FAT signature is found, the disk will be read as PBR and continue processing. Signed-off-by: NDarwin Dingel <darwin.dingel@alliedtelesis.co.nz>
-
由 Masahiro Yamada 提交于
Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
-
由 Thomas Betker 提交于
Replace run_command() by run_command_repeatable() in places which depend on the return code to indicate repeatability. Signed-off-by: NThomas Betker <thomas.betker@rohde-schwarz.com> Acked-by: NSimon Glass <sjg@chromium.org> Tested-by: NSimon Glass <sjg@chromium.org>
-
由 Thomas Betker 提交于
run_command() returns 0 on success and 1 on error. However, there are some invocations which expect 0 or 1 for success (not repeatable or repeatable) and -1 for error; add run_command_repeatable() for this purpose. Signed-off-by: NThomas Betker <thomas.betker@rohde-schwarz.com> Acked-by: NSimon Glass <sjg@chromium.org> Tested-by: NSimon Glass <sjg@chromium.org>
-
由 Thomas Betker 提交于
run_command() returns 0 for success, 1 for failure. Fix places which assume that failure is indicated by a negative return code. Signed-off-by: NThomas Betker <thomas.betker@rohde-schwarz.com> Acked-by: NSimon Glass <sjg@chromium.org> Tested-by: NSimon Glass <sjg@chromium.org> Tested-by: NStefan Roese <sr@denx.de>
-
由 Simon Glass 提交于
Enable verified boot functionality for a new am335x_boneblack_vboot target. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Enable booting a FIT containing a kernel/device tree. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Add support for device tree control and add device tree files for the beaglebone black initially. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
The current size of 1MB is not enough use to use DFU. Increase it for ARMv7 boards, all of which should have 32MB or more SDRAM. With this change it is possible to do 'dfu mmc 0' on a Beaglebone Black. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
When adding hashes or signatures, the target FDT may be full. Detect this and automatically try again after making 1KB of space. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Make the error handling common, and make sure the file is always closed on error. Rename the parameter to be more description and add comments. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
When writing values into an FDT it is possible that there will be insufficient space. If the caller gets a useful error then it can potentially deal with the situation. Adjust these functions to return -ENOSPC when the FDT is full. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
In some cases, an externally-built device tree binary is required to be attached to U-Boot. An example is when using image signing, since in that case the .dtb file must include the public keys. Add a DEV_TREE_BIN option to the Makefile, and update the documentation. Usage is something like: make DEV_TREE_BIN=boot/am335x-boneblack-pubkey.dtb Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
This function is useful for displaying a hash value, so export it. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Enable the cache for all devices, unless CONFIG_SYS_DCACHE_OFF is defined. This speeds up the Beaglebone Black boot considerable. (Tested only on Beaglebone Black with SD card boot) Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Check that the image size matches the size we get from u-boot.bin. If it doesn't, that generally means that some extra sections are being added to u-boot.bin, meaning that it is not possible to access data appended to the U-Boot binary. This is used for device tree, so needs to work. This problem was introduced by commit b02bfc4d. By adding a test we can prevent a reccurence. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Correct the binary output so that image_binary_size is really at the end of the image. Signed-off-by: NSimon Glass <sjg@chromium.org>
-