On Wed, May 03, 2017 at 11:31:58PM +0200, xypron.g...@gmx.de wrote:
> In dram_init_banksize there seems to be a typo concerning
> a plausibility check of the fdt.
> Testing sc > 2 twice does not make any sense.
>
> The problem was indicated by cppcheck.
>
> Signed-off-by: Heinrich Schuchardt
On Thu, May 04, 2017 at 10:26:42PM +0200, xypron.g...@gmx.de wrote:
> The evaluation of option -c is incorrect:
>
> According to the C99 standard endptr in the first strtol is always
> set as is not NULL.
> So the first part of the or condition is always true.
> If all digits in optarg are
On Fri, May 05, 2017 at 08:57:32PM +0200, xypron.g...@gmx.de wrote:
> The logical expression to check the dtb is incorrect in
> load_devicetree.
>
> The problem was indicated by cppcheck.
>
> The inconsistent variable name dtppart is changed to dtbpart.
>
> Signed-off-by: Heinrich Schuchardt
On Fri, Apr 14, 2017 at 07:54:40PM +0200, xypron.g...@gmx.de wrote:
> A feature rich Linux kernel needs more than 8 MiB.
> Hence enlarge CONFIG_SYS_BOOTM_LEN to 64 MiB for the GXBB systems.
> As all known GXBB systems have at least 512 MiB of RAM this poses no problem.
>
> Cc: Andreas Färber
On Wed, May 03, 2017 at 10:40:11PM +0200, xypron.g...@gmx.de wrote:
> va_start must always be matched by va_end.
>
> The problem was indicated by cppcheck.
>
> Signed-off-by: Heinrich Schuchardt
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description:
On Wed, May 03, 2017 at 11:20:10PM +0200, xypron.g...@gmx.de wrote:
> We should not first dereference p and afterwards assert that is
> was not NULL. Instead do the assert first.
>
> The problem was indicated by cppcheck.
>
> Signed-off-by: Heinrich Schuchardt
Applied to
On Wed, May 03, 2017 at 05:43:46PM +0530, Jagan Teki wrote:
> Hi Tom,
>
> Please take this PR.
>
> thanks!
> Jagan.
>
> The following changes since commit a63d800196ebee59b0f8ff924f67843cd597a8c1:
>
> Prepare v2017.05-rc3 (2017-05-01 19:54:41 -0400)
>
> are available in the git repository
From: Jagan Teki
Usually the drive strength values for DQ and SDL are 0x30 and
0x28 respectively, update them accordingly.
Cc: Stefano Babic
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by:
From: Jagan Teki
Move board_late_init into common area from supported boards.
Cc: Stefano Babic
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
---
From: Jagan Teki
SPL FIT is able to pick the suitable fdt file for u-boot,
so add that function through board_fit_config_name_match.
Cc: Stefano Babic
Cc: Matteo Lisi
Cc: Michael Trimarchi
From: Jagan Teki
SPL code for geam6 and isiot are same, so
move them in common area.
Cc: Stefano Babic
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
From: Jagan Teki
Since, u-boot handle fdt through uart so move the UART code
to SPL instead make it to global area.
Cc: Stefano Babic
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan
From: Jagan Teki
mmc2 in Is.IoT using usdhc1_pads instead usdhc2_pads,
so update the same.
Cc: Stefano Babic
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
From: Jagan Teki
Move possible common board code into common area
from supported boards.
Cc: Stefano Babic
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
From: Jagan Teki
Add generic SETUP_IOMUX_PADS function, for imx6ul mux pads.
Cc: Stefano Babic
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
---
From: Jagan Teki
Use driver strength macros instead of hex numbers.
- IMX6DQ_DRIVE_STRENGTH - 0x30
- IMX6SDL_DRIVE_STRENGTH - 0x28
Cc: Stefano Babic
Cc: Matteo Lisi
Cc: Michael Trimarchi
From: Jagan Teki
SPL code for icorem6 and icorem6_rqs are same, so
move them in common area.
Cc: Stefano Babic
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
From: Jagan Teki
Add generic SETUP_IOMUX_PADS function, for imx6ul mux pads
and use them in Is.IoT board.
Cc: Stefano Babic
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
From: Jagan Teki
Add runtime, modeboot env which is setting mmcboot, or
nandboot based on the bootdevice so-that conditional
macros b/w MMC and NAND for CONFIG_BOOTCOMMAND should
be avoided in config files.
Cc: Matteo Lisi
Cc: Michael
From: Jagan Teki
Let the runtime code can set the mmcdev and mmcroot based
on the devno using mmc_get_env_dev instead of defining
separately in build-time configs using mmc_late_init func.
Cc: Matteo Lisi
Cc: Michael Trimarchi
From: Jagan Teki
Let the runtime code can set the mmcdev and mmcroot based
on the devno using mmc_get_env_dev instead of defining
separately in build-time configs using mmc_late_init func.
Cc: Stefano Babic
Cc: Matteo Lisi
From: Jagan Teki
Set fdt_file env variable during board_late_init
Cc: Stefano Babic
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
---
From: Jagan Teki
Add runtime, modeboot env which is setting mmcboot, or
nandboot based on the bootdevice so-that conditional
macros b/w MMC and NAND for CONFIG_BOOTCOMMAND should
be avoided in config files.
Cc: Matteo Lisi
Cc: Michael
From: Jagan Teki
Engicam boards have some common code, so move them as
(1) SPL board_init_f and UART MUX init to common/spl.c
(2) board_init, dram_init, board_late_init and mmc_late_init to
common/board.c
This series also add board_fit_config_name_match to make
Till now get_ldo_reg did a return _ldo[num - 1]; to return
the ldo register offset but didn't take into account that its
calling functions already created the ldo as ldo = dev->driver_data - 1.
This resulted in the setting for ldo8 writing to the register of ldo7
and so on. So fix this and get
Hi
On 6/05/2017 3:57 PM, "Kernel Hacker" wrote:
On 04/25/2017 09:04 PM, Kernel Hacker wrote:
> I have a Guruplug server standard that I would like to upgrade with a
> newer version of u-boot. Serial output during boot currently shows the
> following:
>
>
26 matches
Mail list logo