12 Jun, 2017
10 commits
-
Since the parameter can be NULL we must be careful not to dereference it
in this case.Signed-off-by: Simon Glass
Reported-by: Coverity (CID: 163250)
Fixes: 1043d0a0 (fdt: Add fdtgrep tool) -
We should not use an open-coded value here. Use sizeof() instead.
Signed-off-by: Simon Glass
Reported-by: Coverity (CID: 163252)
Fixes: 43c6bdd0 (edid: Add HDMI flag to timing info) -
We know that uclass_get_device() does not return NULL for dev when it
succeeds but coverity does not. Add an extra check to hopefully keep it
happy.Signed-off-by: Simon Glass
Reported-by: Coverity (CID: 161690)
Fixes: 43b4156 (dm: sandbox: pwm: Add a basic pwm test) -
There was for long time no activity in the 5xx area.
We need to go further and convert to Kconfig, but it
turned out, nobody is interested anymore in 5xx,
so remove it.Signed-off-by: Heiko Schocher
-
There was for long time no activity in the 8260 area.
We need to go further and convert to Kconfig, but it
turned out, nobody is interested anymore in 8260,
so remove it.Signed-off-by: Heiko Schocher
-
There was for long time no activity in the 8xx area.
We need to go further and convert to Kconfig, but it
turned out, nobody is interested anymore in 8xx,
so remove it (with a heavy heart, knowing that I remove
here the root of U-Boot).Signed-off-by: Heiko Schocher
-
One can obtain those variables using next commands:
$ fastboot getvar cpu
$ fastboot getvar secure
$ fastboot getvar board_rev
$ fastboot getvar userdata_sizeThose variables are needed for fastboot.sh script.
Signed-off-by: Sam Protsenko
Reviewed-by: Tom Rini -
One can obtain those variables using next commands:
$ fastboot getvar cpu
$ fastboot getvar secure
$ fastboot getvar board_rev
$ fastboot getvar userdata_sizeThose variables are needed for fastboot.sh script.
Signed-off-by: Sam Protsenko
Reviewed-by: Tom Rini -
This patch reuses new option, which allows us to expose variables
from environment to "fastboot getvar" command. Those variables must be
of "fastboot.%s" format.Signed-off-by: Sam Protsenko
-
Using u-boot-2017.05 on i.MX6UL we ran into following problem:
Initially U-Boot could be started normally.
If we added one random command in configuration, the newly generated
image hung at startup (last output was DRAM: 256 MiB).We tracked this down to a data abort within relocation (relocated_code).
relocated_code in arch/arm/lib/relocate.S copies 8 bytes per loop
iteration until the source pointer is equal to __image_copy_end.
In a good case __image_copy_end was aligned to 8 bytes, so the loop
stopped as suggested, but in an errornous case __image_copy_end was
not aligned to 8 bytes, so the loop ran out of bounds and caused a
data abort exception.This patches solves the issue by aligning __image_copy_end to 8 byte
using the linker script related to arm.I don't know if it's the correct way to solve this, so some review would
be very appreciated.
11 Jun, 2017
1 commit
10 Jun, 2017
29 commits
-
When we don't have CONFIG_BLK defined we don't have a forward
declaration of struct udevice, and thus get a warning about it on
blk_get_from_parent(), which we only have when CONFIG_BLK is set. Move
the declaration of blk_get_from_parent() to be with the other CONFIG_BLK
parts.Fixes 9f103b9cb5f8 ("dm: blk: Add a way to obtain a block device from ...")
Signed-off-by: Tom Rini -
The kwbimage utility fails to compile when LibreSSL is present on
the host system instead of OpenSSL. This one-line patch resolves
this.Signed-off-by: Marek Behun
-
CONFIG_FAT_WRITE is imply'ed when CONFIG_CMD_FAT
is selected (see CONFIG_TI_COMMON_CMD_OPTIONS).Dont disable it in defconfig so the imply takes
effect and 'fatwrite' is available for users.Signed-off-by: Sekhar Nori
Reviewed-by: Tom Rini -
As only FIT image is supported now, this patch is to support loading
32-bit uImage, dtb and rootfs separately.Signed-off-by: Alison Wang
Reviewed-by: Tom Rini -
Fixed checkpatch.pl errors/warnings in board/mpl/common/pci.c
Signed-off-by: Chakra Divi
-
Like commit 3337e3af5d3d this enables suitable commands needed for booting
general purpose Linux distribution. This is required for example if we want
to use PXE or DHCP as default boot targets, symbols no longer enabled by
config_distro_defaults.h.Signed-off-by: Enric Balletbo i Serra
-
Update the board pinmux for AM572x-evm using latest PMT[1] and the
board files named am572x_gp_evm_A3a_sr2p0 and am572x_gp_evm_A2b_sr1p1
that were autogenerated on 30th January, 2017 by
"Ahmad Rashed " and "Tom Johnson ".Signed-off-by: Lokesh Vutla
-
Update the board pinmux for AM571x-IDK board using latest PMT[1] and the
board files named am571x_idk_v1p3b_sr2p0 that were autogenerated on
23rd March, 2017 by "Ahmad Rashed " and
"Tom Johnson ".[1] https://dev.ti.com/pinmux/app.html#/default/
Signed-off-by: Lokesh Vutla
-
Update the board pinmux for AM572x-IDK board using latest PMT[1] and the
board files named am572x_idk_v1p3b_sr2p0 that were autogenerated on
30th January, 2017 by "Ahmad Rashed " and
"Tom Johnson ".[1] https://dev.ti.com/pinmux/app.html#/default/
Signed-off-by: Lokesh Vutla
-
Add poweroff description to Kconfig to make it selectable
via menuconfig.Signed-off-by: Michal Simek
Reviewed-by: Simon Glass -
Disable D-Cache is required when booting nommu Linux kernel.
(please see Linux kernel source "arch/arm/kernel/head-nommu.S")U-Boot is enabled D-cache and I-Cache at startup.
However, it does not disable D-Cache before
booting nommu Linux kernel.
Therefore, I call dcache_disable()
when the CPU is ARMv7M to fix this problem.Signed-off-by: Toshifumi NISHINAGA
-
Refactor OMAP3/4/5 code so that we have only one get_device_type()
function for all platforms.Details:
- Add ctrl variable for AM33xx and OMAP3 platforms (like it's done for
OMAP4/5), so we can obtain status register in common way
- For now ctrl structure for AM33xx/OMAP3 contains only status register
address
- Run hw_data_init() in order to assign ctrl to proper structure
- Remove DEVICE_MASK and DEVICE_GP definitions as they are not used
(DEVICE_TYPE_MASK and GP_DEVICE are used instead)
- Guard structs in omap_common.h with #ifdefs, because otherwise
including omap_common.h on non-omap4/5 board files breaks compilationBuildman script was run for all OMAP boards. Result output:
arm: (for 38/616 boards)
all +352.5
bss -1.4
data +3.5
rodata +300.0
spl/u-boot-spl:all +284.7
spl/u-boot-spl:data +2.2
spl/u-boot-spl:rodata +252.0
spl/u-boot-spl:text +30.5
text +50.4
(no errors to report)Tested on AM57x EVM and BeagleBoard xM.
Signed-off-by: Sam Protsenko
Reviewed-by: Lokesh Vutla
[trini: Rework the guards as to not break TI81xx]
Signed-off-by: Tom Rini -
Almost all users of CONFIG_AM33XX/AM43XX have been migrated. Finish
moving the last few over to Kconfig, and put all of the boards under the
appropriate Kconfig chocie now. This board choice is non-optional, so
remove that keyword on am33xx.Signed-off-by: Tom Rini
-
With this commit we can modify single values within an array of a dts
property.This is useful if we have for example a pwm-backlight where we want to
modifiy the pwm frequency per u-boot script.The pwm is described in dts like this:
backlight {
pwms = ;
};For changing the frequency, here the 3rd parameter, we simply type:
fdt set /backlight pwms ;
For doing all this we:
- backup the property content into our 'SCRATCHPAD'
- only modify the array-cell if the new content doesn't start with '?'Signed-off-by: Hannes Schmelzer
Reviewed-by: Simon Glass -
The build output can still produce unicode encoded output. But in
the buildman's log and err files we only want plain ASCII characters.To handle all situations with unicode and non-unicode output, encode
the stdout and stderr strings to UTF-8 and afterwards to ASCII with
replacing all special characters.Signed-off-by: Daniel Schwierzeck
-
Build tools like Make, gcc or binutils support localized output
or unicode encoded output dependent on the default system locale.
This is not useful for buildman, where we want reproducible
warning or error messages or where the output of binutils is
further processed.Signed-off-by: Daniel Schwierzeck
-
Add instructions for chromebook_jerry.
Signed-off-by: Simon Glass
-
The display on jerry is so fast that this option is not needed. Drop it so
that the display scrolls more smoothly.Signed-off-by: Simon Glass
-
Show the U-Boot banner and board information on the video display during
boot.Signed-off-by: Simon Glass
-
If U-Boot is chain-loaded from a previous boot loader we must set up the
clocks the way U-Boot wants them. Add code for this. It will do nothing if
SPL has already done the job.Signed-off-by: Simon Glass
-
Detect with a previous boot loader has already set up the clocks and set
them up again so that U-Boot gets what it expects.Signed-off-by: Simon Glass
-
Shifted masks are the standard approach with rockchip since it allows
use of the mask without shifting it each time. Update the definitions and
the driver to match.Signed-off-by: Simon Glass
-
Add a sample .its file for booting U-Boot on a jerry Chromebook.
Signed-off-by: Simon Glass
-
On reset the standby bit is clear, but if U-Boot is chain-loaded from
another boot loader it may be set. Clear it before starting up video so
that it works correctly.Signed-off-by: Simon Glass
Acked-by: Anatolij Gustschin
Squashed in 'rockchip: video: fix taking the VOP device out of standby':
Signed-off-by: Philipp Tomsich -
Add remove() methods for EDP and VOP so that U-Boot can shut down the
video on exit. This avoids leaving DMA running while booting Linux which
can cause problems if Linux uses the frame buffer for something else.It also makes it clear what is needed to shut down video.
While we are here, make rkvop_enable() static.
Signed-off-by: Simon Glass
Acked-by: Anatolij Gustschin
Squashed in 'rockchip: video: fix taking the VOP device out of standby':
Signed-off-by: Philipp Tomsich -
Add a debug() statement so we can see when something goes wrong with the
regulator.Signed-off-by: Simon Glass
-
This typo doesn't actually cause any problems, but is wrong. Fix it.
Signed-off-by: Simon Glass
