- 16 Sep, 2016 1 commit
-
-
Simon Glass authored
At present TPL uses the same options as SPL support. In a few cases the board config enables or disables the SPL options depending on whether CONFIG_TPL_BUILD is defined. With the move to Kconfig, options are determined for the whole build and (without a hack like an #undef in a header file) cannot be controlled in this way. Create new TPL options for these and update users. This will allow Kconfig conversion to proceed for these boards. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- 07 Sep, 2016 1 commit
-
-
Mian Yousaf Kaukab authored
Provide version of struct efi_mem_desc in efi_get_memory_map(). EFI_BOOT_SERVICES.GetMemoryMap() in UEFI specification v2.6 defines memory descriptor version to 1. Linux kernel also expects descriptor version to be 1 and prints following warning during boot if its not: Unexpected EFI_MEMORY_DESCRIPTOR version 0 Signed-off-by:
Mian Yousaf Kaukab <yousaf.kaukab@gmail.com>
-
- 30 Aug, 2016 1 commit
-
-
Bin Meng authored
Since commit 73c5c399 "Makefile: Drop unnecessary -dtb suffixes", EFI payload does not build anymore. This fixes the build. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- 20 Aug, 2016 8 commits
-
-
Alexander Graf authored
We were truncating the image offset within the target image to 16 bits which again meant that we were potentially overwriting random memory in the lower 16 bits of the image. This patch casts the offset to a more reasonable 32bits. With this applied, I can successfully see Shell.efi assert because it can't find a protocol it expects to be available. Signed-off-by:
Alexander Graf <agraf@suse.de>
-
Maxime Ripard authored
This adds a bunch of unit tests for the "fdt apply" command. They've all been run successfully in the sandbox. However, as you still require an out-of-tree dtc with overlay support, this is disabled by default. Acked-by:
Simon Glass <sjg@chromium.org> Acked-by:
Pantelis Antoniou <pantelis.antoniou@konsulko.com> Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com>
-
Maxime Ripard authored
The device tree overlays are a good way to deal with user-modifyable boards or boards with some kind of an expansion mechanism where we can easily plug new board in (like the BBB or the raspberry pi). However, so far, the usual mechanism to deal with it was to have in Linux some driver detecting the expansion boards plugged in and then request these overlays using the firmware interface. That works in most cases, but in some cases, you might want to have the overlays applied before the userspace comes in. Either because the new board requires some kind of an early initialization, or because your root filesystem is accessed through that expansion board. The easiest solution in such a case is to simply have the component before Linux applying that overlay, removing all these drawbacks. Reviewed-by:
Stefan Agner <stefan@agner.ch> Acked-by:
Pantelis Antoniou <pantelis.antoniou@konsulko.com> Acked-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com>
-
Maxime Ripard authored
The device tree overlays are a good way to deal with user-modifyable boards or boards with some kind of an expansion mechanism where we can easily plug new board in (like the BBB, the Raspberry Pi or the CHIP). Add a new function to merge overlays with a base device tree. Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com>
-
Maxime Ripard authored
Add a function to modify inplace only a portion of a property.. This is especially useful when the property is an array of values, and you want to update one of them without changing the DT size. Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Maxime Ripard authored
Add a namelen variant of fdt_path_offset to retrieve the node offset using only a fixed number of characters. Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com>
-
Maxime Ripard authored
The function fdt_path_next_seperator had an obvious mispell. Fix it. Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com>
-
Maxime Ripard authored
Add a function to retrieve the highest phandle in a given device tree. Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com> Reviewed-by:
Stefan Agner <stefan@agner.ch> Acked-by:
Simon Glass <sjg@chromium.org>
-
- 12 Aug, 2016 1 commit
-
-
Stephen Warren authored
Some code may want to read reg values from DT, but from nodes that aren't associated with DM devices, so using dev_get_addr_index() isn't appropriate. In this case, fdtdec_get_addr_size_*() are the functions to use. However, "translation" (via the chain of ranges properties in parent nodes) may still be desirable. Add a function parameter to request that, and implement it. Update all call sites to default to the original behaviour. Signed-off-by:
Stephen Warren <swarren@nvidia.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Squashed in build fix from Stephen: Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- 08 Aug, 2016 3 commits
-
-
Alexander Graf authored
When a target device is 0 bytes long, there's no point in exposing it to the user. Let's just skip them. Also, when an offset is passed into the efi disk creation, we should remove this offset from the total number of sectors we can handle. This patch fixes both things. Signed-off-by:
Alexander Graf <agraf@suse.de>
-
Alexander Graf authored
When using CONFIG_BLK, there were 2 issues: 1) The name we generate the device with has to match the name we set in efi_set_bootdev() 2) The device we pass into our block functions was wrong, we should not rediscover it but just use the already known pointer. This patch fixes both issues. Signed-off-by:
Alexander Graf <agraf@suse.de>
-
Simon Glass authored
We can pass all the variables down to the functions that need them, and then everything is on the stack. This is safer than using the data section. At least on firefly-rk3288, the code size is the same and the data size is 12 bytes smaller: before: 18865 2636 40 21541 5425 b/firefly-rk3288/spl/u-boot-spl after: 18865 2624 40 21529 5419 b/firefly-rk3288/spl/u-boot-spl Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Stefan Roese <sr@denx.de>
-
- 25 Jul, 2016 3 commits
-
-
Simon Glass authored
This fixes a mismatch between the %zu format and the type used on sandbox. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
mario.six@gdsys.cc authored
[NOTE: I took v1 of these patches in, and then v2 came out, this commit is squashing the minor deltas from v1 -> v2 of updates to c236ebd2 and 2b9ec762 into this commit - trini] - Added an additional NULL check, as suggested by Simon Glass to fit_image_process_sig - Re-formatted the comment blocks Signed-off-by:
Mario Six <mario.six@gdsys.cc> Reviewed-by:
Simon Glass <sjg@chromium.org> [For merging the chnages from v2 back onto v1] Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Boris Brezillon authored
We already have an SPL driver for the sunxi NAND controller, now add the normal/standard one. The source has been copied from Linux 4.6 with a few changes to make it work in u-boot. Signed-off-by:
Boris Brezillon <boris.brezillon@free-electrons.com> Acked-by:
Hans de Goede <hdegoede@redhat.com>
-
- 22 Jul, 2016 2 commits
-
-
mario.six@gdsys.cc authored
When signing images, we repeatedly call fit_add_file_data() with successively increasing size values to include the keys in the DTB. Unfortunately, if large keys are used (such as 4096 bit RSA keys), this process fails sometimes, and mkimage needs to be called repeatedly to integrate the keys into the DTB. This is because fit_add_file_data actually returns the wrong error code, and the loop terminates prematurely, instead of trying again with a larger size value. This patch corrects the return value by fixing the return value of fdt_add_bignum, fixes a case where an error is masked by a unconditional setting of a return value variable, and also removes a error message, which is misleading, since we actually allow the function to fail. A (hopefully helpful) comment is also added to explain the lack of error message. This is probably related to 1152a05e ("tools: Correct error handling in fit_image_process_hash()") and the corresponding error reported here: https://www.mail-archive.com/u-boot@lists.denx.de/msg217417.htmlSigned-off-by:
Mario Six <mario.six@gdsys.cc>
-
Andreas Färber authored
Tracing the arguments has been helpful for pinpointing overflows. Cc: Alexander Graf <agraf@suse.de> Signed-off-by:
Andreas Färber <afaerber@suse.de> Reviewed-by:
Alexander Graf <agraf@suse.de>
-
- 16 Jul, 2016 1 commit
-
-
Robert P. J. Day authored
Fix a number of typos, including: * "compatble" -> "compatible" * "eanbeld" -> "enabled" * "envrionment" -> "environment" * "FTD" -> "FDT" (for "flattened device tree") * "ommitted" -> "omitted" * "overriden" -> "overridden" * "partiton" -> "partition" * "propogate" -> "propagate" * "resourse" -> "resource" * "rest in piece" -> "rest in peace" * "suport" -> "support" * "varible" -> "variable" Signed-off-by:
Robert P. J. Day <rpjday@crashcourse.ca>
-
- 15 Jul, 2016 3 commits
-
-
Simon Glass authored
At present assert() is not supported with tiny-printf, so when DEBUG is enabled a build error is generated for each assert(). Add an __assert_fail() function to correct this. It prints a message and then hangs. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Add a Python version of the libfdt library which contains enough features to support the dtoc tool. This is only a very bare-bones implementation. It requires the 'swig' to build. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
We cannot access the device tree in this case, so avoid compiling in the various device-tree helper functions. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- 11 Jul, 2016 5 commits
-
-
Simon Glass authored
The cros-ec keyboard is always a child of the cros-ec node. Rather than searching the device tree, looking at the children. Remove the compat string which is now unused. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
The 'COMPAT_' part should appear only once so drop the duplicate part. It is ignored anyway, but let's keep things consistent. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com>
-
Simon Glass authored
The list is shrinking and we should avoid adding new things. Instead, a proper driver should be created with driver model. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com>
-
Simon Glass authored
A few drivers have moved to driver model, so we can drop these strings. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Simon Glass authored
We have drivers for several more devices now, so drop the strings which are no-longer used. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com>
-
- 08 Jul, 2016 1 commit
-
-
Andre Przywara authored
As printf calls may be executed quite early, we should avoid using any BSS stored variables, since some boards put BSS in DRAM, which may not have been initialised yet. Explicitly mark those "static global" variables as belonging to the .data section, to keep tiny-printf clear of any BSS usage. Signed-off-by:
Andre Przywara <andre.przywara@arm.com>
-
- 05 Jul, 2016 1 commit
-
-
Simon Glass authored
We have driver-model drivers for some of these now, so drop them. Signed-off-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
- 24 Jun, 2016 1 commit
-
-
Joris Lijssens authored
When the input data is not compressed at all, lzo1x_decompress_safe will fail, so call memcpy() instead. Signed-off-by:
Joris Lijssens <joris.lijssens@gmail.com>
-
- 20 Jun, 2016 1 commit
-
-
Hans de Goede authored
vprintf is used by panic() which is used in various SPL paths on some boards. Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Acked-by:
Ian Campbell <ijc@hellion.org.uk> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- 19 Jun, 2016 1 commit
-
-
Robert P. J. Day authored
A number of style fixes across the files in this directory, including: * Correct invalid kernel-doc content. * Tidy up massive comment in fdt_region.c. * Use correct spelling of "U-Boot". * Replace tests of "! <var>" with "!<var>". * Replace "libfdt_env.h" with <libfdt_env.h>. Signed-off-by:
Robert P. J. Day <rpjday@crashcourse.ca> Acked-by:
Simon Glass <sjg@chromium.org>
-
- 12 Jun, 2016 2 commits
-
-
Simon Glass authored
This should return a non-zero value if there is a missing property. Update the return value accordingly. The only expected error is -FDT_ERR_NOTFOUND. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Andreas Bießmann <andreas@biessmann.org>
-
Teddy Reed authored
This allows a board to configure verified boot within the SPL using a FIT or FIT with external data. It also allows the SPL to perform signature verification without needing relocation. The board configuration will need to add the following feature defines: CONFIG_SPL_CRYPTO_SUPPORT CONFIG_SPL_HASH_SUPPORT CONFIG_SPL_SHA256 In this example, SHA256 is the only selected hashing algorithm. And the following booleans: CONFIG_SPL=y CONFIG_SPL_DM=y CONFIG_SPL_LOAD_FIT=y CONFIG_SPL_FIT=y CONFIG_SPL_OF_CONTROL=y CONFIG_SPL_OF_LIBFDT=y CONFIG_SPL_FIT_SIGNATURE=y Signed-off-by:
Teddy Reed <teddy.reed@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org> Acked-by:
Andreas Dannenberg <dannenberg@ti.com> Acked-by:
Sumit Garg <sumit.garg@nxp.com>
-
- 09 Jun, 2016 1 commit
-
-
Simon Glass authored
This current code passes the variable arguments list to sprintf(). This is not correct. Fix it by calling _vprintf() directly. This makes firefly-rk3288 boot again. Fixes: abeb272d ("tiny-printf: Support snprintf()") Reviewed-by:
Stefan Roese <sr@denx.de> Acked-by:
Marek Vasut <marex@denx.de> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- 06 Jun, 2016 3 commits
-
-
Chris Packham authored
When setting up a DDR controller it is useful to be able to display frequencies in a readable form. Make the strmhz() function available in SPL builds provided there is full vsprintf available. Reviewed-by:
Tony O'Brien <tony.obrien@alliedtelesis.co.nz> Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Chris Packham <judge.packham@gmail.com>
-
Robert P. J. Day authored
Since bcopy() is no longer used, delete all remaining references to it. Signed-off-by:
Robert P. J. Day <rpjday@crashcourse.ca>
-
Alexander Graf authored
Some systems are starting to shift to support DM_VIDEO which exposes the frame buffer through a slightly different interface. This is a poor man's effort to support the dm video interface instead of the lcd one. We still only support a single display device. Signed-off-by:
Alexander Graf <agraf@suse.de> [trini: Remove fb_size / fb_base as they were not used] Signed-off-by:
Tom Rini <trini@konsulko.com>
-