Re: [U-Boot] [PATCH] serial: Remove duplicated line in Makefile

Hi, On 04/16/2018 01:35 AM, Patrice Chotard wrote: > The line "-obj-$(CONFIG_STM32_SERIAL) += serial_stm32.o" > is found twice in Makefile. > > Fixes: ae74de0dfd45 ("serial: stm32: Rename serial_stm32x7.c to > serial_stm32.c" > > Signed-off-by: Patrice Chotard

Re: [U-Boot] [PATCH v2] bootm: Align cache flush begin address

Hi Bryan, 2018-04-15 7:48 GMT-03:00 Bryan O'Donoghue : > commit b4d956f6bc0f ("bootm: Align cache flush end address correctly") > aligns the end address of the cache flush operation to a cache-line size to > ensure lower-layers in the code accept the range provided and

Re: [U-Boot] [PATCH v2] bootm: Align cache flush begin address

On 15 April 2018 at 04:48, Bryan O'Donoghue wrote: > commit b4d956f6bc0f ("bootm: Align cache flush end address correctly") > aligns the end address of the cache flush operation to a cache-line size to > ensure lower-layers in the code accept the range provided and

Re: [U-Boot] [PATCH] serial: Remove duplicated line in Makefile

On 16 April 2018 at 02:35, Patrice Chotard wrote: > The line "-obj-$(CONFIG_STM32_SERIAL) += serial_stm32.o" > is found twice in Makefile. > > Fixes: ae74de0dfd45 ("serial: stm32: Rename serial_stm32x7.c to > serial_stm32.c" > > Signed-off-by: Patrice Chotard

Re: [U-Boot] [PATCH v2 1/3] arm: psci: save context id for cpu_on PSCI command

On 04/16/2018 02:13 AM, Patrick Delaunay wrote: Save and use the 3rd parameter of PSCI CPU_ON request: context_id. The context_id parameter is only meaningful to the caller. U-Boot PSCI preserves a copy of the value passed in this parameter. Following wakeup from a powerdown state, U-BOOT PSCI

[U-Boot] [PATCH V5 0/2] Update sabrelite and nitrogen6x boards to use distro boot support

This patch serie updates sabrelite and nitrogen6x boards to use distro boot support. Sabrelite has been boot tested with boot.scr script and EFI/Grub2 on mmc0 and mmc1 slots. Nitrogen6* boards have been build tested only. Currently, only the Sabrelite has fdtfile defined. Signed-off-by:

Re: [U-Boot] Please pull u-boot-cfi-flash/master

On Mon, Apr 16, 2018 at 01:25:58PM +0200, Stefan Roese wrote: > Hi Tom, > > please pull this one CFI related patch from Mario. > > Thanks, > Stefan > > The following changes since commit ebca902aeb3af3eaedd2787928184ad84a86b98f: > > Merge git://git.denx.de/u-boot-imx (2018-04-15 08:43:50

Re: [U-Boot] [Feature] Android Fastboot over Ethernet

Hi Alex, Thanks for the links, this helps a lot. Stan ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH 3/6] tegra: psci: save context id in cpu_on command

On 04/16/2018 02:15 AM, Patrick Delaunay wrote: Replace the psci_save_target_pc call by the new function psci_save(cpu, pc,context_id) So this function doesn't actually exist since it's added in a different patch series that isn't mentioned as a dependency. Luckily I managed to find it in

Re: [U-Boot] [PATCH v3 00/17] warp7: Enable automated OPTEE/HAB boot flow

Hi Bryan, 2018-04-13 12:31 GMT-03:00 Bryan O'Donoghue : > https://git.linaro.org/landing-teams/working/mbl/u-boot.git/log/?h=linaro-mbl%2bbod > > v3: > - Reword commit message of patch #16 - Breno > > - This patchset now relies on five in-flight patch-sets the first

Re: [U-Boot] u-boot 2018 SPI SPL

Dear Fabio, Thank you for your helps.. I applied the procedure which is explained in board/congatec/cgtqmx6eval/README document. Upgraded u-boot to 1018.05-rc1, but as you will see below, I received same message; I will compare my config/header files with congatec's, but I don't know which

[U-Boot] [PATCH] arm,imx6: fix PAD_CTL_SPEED_LOW constant

For most i.MX6 processors the PAD_CTL_SPEED_LOW constant is the same. Only the i.MX6 SoloLite is an exemption. So far the code did not consider that. Additionally, for a few i.MX6 processors the code used the wrong value for the constant. This patch fixes the PAD_CTL_SPEED_LOW constant for: -

Re: [U-Boot] Please pull u-boot-x86

Hi Tom, On Mon, Apr 16, 2018 at 8:31 PM, Tom Rini wrote: > On Mon, Apr 16, 2018 at 05:17:30PM +0800, Bin Meng wrote: > >> Hi Tom, >> >> This includes some fixes and enhancements to VxWorks booting support, >> as well as some mods to x86 I/O functions. >> >> The following

[U-Boot] Please pull u-boot-x86 (take 2)

Hi Tom, This includes some fixes and enhancements to VxWorks booting support, as well as some mods to x86 I/O functions. The following changes since commit ebca902aeb3af3eaedd2787928184ad84a86b98f: Merge git://git.denx.de/u-boot-imx (2018-04-15 08:43:50 -0400) are available in the git

Re: [U-Boot] [PATCH v2] mmc: mv_sdhci: zero out sdhci_host structure

On 16.04.2018 16:08, Matt Pelland wrote: The mv_sdhci driver was not zeroing the sdhci_host structure it allocates causing random access violations in parts of the mmc core where the "ops" member pointers are checked and called if not NULL. Signed-off-by: Matt Pelland ---

[U-Boot] Please pull u-boot-cfi-flash/master

Hi Tom, please pull this one CFI related patch from Mario. Thanks, Stefan The following changes since commit ebca902aeb3af3eaedd2787928184ad84a86b98f: Merge git://git.denx.de/u-boot-imx (2018-04-15 08:43:50 -0400) are available in the Git repository at:

Re: [U-Boot] [PATCH 0/6] Android A/B Bootloader support

Hi Stanislas, This work is in use in Android Things preview U-Boot bootloader for the raspberry pi. The code is available in https://android.googlesource.com/platform/external/u-boot/+/android-o-mr1-iot-preview-7 . If I remember correctly, these patches are a cleanup of that code, but they are a

[U-Boot] [PATCH v2] mmc: mv_sdhci: zero out sdhci_host structure

The mv_sdhci driver was not zeroing the sdhci_host structure it allocates causing random access violations in parts of the mmc core where the "ops" member pointers are checked and called if not NULL. Signed-off-by: Matt Pelland --- drivers/mmc/mv_sdhci.c | 2 +- 1 file

Re: [U-Boot] Please pull u-boot-x86

On Mon, Apr 16, 2018 at 05:17:30PM +0800, Bin Meng wrote: > Hi Tom, > > This includes some fixes and enhancements to VxWorks booting support, > as well as some mods to x86 I/O functions. > > The following changes since commit ebca902aeb3af3eaedd2787928184ad84a86b98f: > > Merge

Re: [U-Boot] [PATCH v5 1/2] SPI Flash: add support of sst26wf* flash ICs protection ops

Hi Jagan! Any comments? On Tue, 2018-04-10 at 14:40 +0300, Eugeniy Paltsev wrote: > sst26wf flash series block protection implementation differs > from other SST series, so add specific implementation > flash_lock/flash_unlock/flash_is_locked functions for sst26wf > flash ICs. > >

Re: [U-Boot] u-boot 2018 SPI SPL

Hi Mehmet, On Mon, Apr 16, 2018 at 8:36 AM, Mehmet Ali İPİN wrote: > U-Boot SPL 2018.05-rc1 (Apr 16 2018 - 00:31:02 -0700) > SPL: Unsupported Boot Device! You need to debug why you are getting this message when booting from SPI.

[U-Boot] [PATCH V5 1/2] imx6: Convert sabrelite and nitrogen6x boards to distro boot support

Boot tested on sabrelite board. Signed-off-by: Guillaume GARDET Cc: Troy Kisky Cc: Stefano Babic Cc: Fabio Estevam Cc: Gary Bisson ---

[U-Boot] [PATCH V5 2/2] imx6: sabrelite: update defconfig to use distro defaults

Boot tested with boot.scr script and EFI/Grub2 on mmc0 and mmc1 slots on sabrelite board. Signed-off-by: Guillaume GARDET Cc: Troy Kisky Cc: Stefano Babic Cc: Fabio Estevam Cc: Gary Bisson

Re: [U-Boot] Re-introducing support for OLD hardware

On Thu, 12 Apr 2018 09:04:20 +0200 Jason Mitchell wrote: > Good day all > > I am currently faced with a task of having to run new software on > ageing hardware. We have currently about 1000 units in the field of a > machine that runs Windows CE using the Samsung S3C6410. >

[U-Boot] [PATCH 3/5] arm: ti: boot: Extract PARTS_DEFAULT to boot.h

Eliminate code duplication: the same PARTS_DEFAULT was defined in am57xx_evm.h and in dra7xx_evm.h. Extract it to environment/boot.h and use in all OMAP5-based boards. Signed-off-by: Sam Protsenko --- include/configs/am57xx_evm.h | 25 -

[U-Boot] [PATCH 2/5] cmd: Add dtimg command

dtimg command allows user to work with Android DTB/DTBO image format. Such as, getting the address of desired DTB/DTBO file, printing the dump of the image in U-Boot shell, etc. This command is needed to provide Android boot with new Android DT image format further. Signed-off-by: Sam Protsenko

Re: [U-Boot] [PATCHv1 14/14] reset: remove request and free functions

On 04/16/2018 01:43 PM, Simon Glass wrote: > +Stephen for comment > > Hi Dinh, > > On 14 April 2018 at 12:51, Dinh Nguyen wrote: >> The request and free reset functions are not really used for any useful >> purpose but for debugging. We can safely remove them. > > The

[U-Boot] [PATCH 5/5] arm: ti: boot: Implement Android boot using DT image format

Make sure we can boot Android on TI boards using scheme described in Android documentation [1]. For this do next: 1. Enable "dtimg" command. We will need it to boot the Android using new DTB/DTBO image format. 2. Add fdt overlay support. We will need that to be able to apply fdt overlays

[U-Boot] [PATCH 4/5] arm: ti: boot: Add dtbo partition for Android boot

New Android boot scheme looks like this [1], and it involves adding new partition for storing Device Tree Overlays. This patch adds dtbo partition. While at it, let's revise Android partition table a bit. List of changes: - rename "misc" to "hole" (not used for anything, just a guard hole) -

[U-Boot] [PATCH 1/5] common: Add support for Android DT image

Android documentation recommends new image format for storing DTB/DTBO files: [1]. To support that format, two things should be done: 1. Add dt_table.h file from Android (BSD-3 relicensed version): [2]. This header defines structures and constants that we need to work with that DT image

Re: [U-Boot] [PATCH] fit: skip signature verification if board request

Hi Jun, On 13 April 2018 at 04:05, Jun Nie wrote: > 2018-04-13 1:24 GMT+08:00 Simon Glass : >> Hi, >> >> On 11 April 2018 at 09:13, Jun Nie wrote: >>> It may be unnecessary to check signature on unlocked board. >>> Get the hint from

[U-Boot] [PATCH 0/5] Use Android DT image format for TI boards

Android documentation recommends using new image format for storing dtb and dtbo files: [1]. Using that format, we can pack several dtb files to dtb.img, and also pack several dtbo files to dtbo.img. Then those images should be flashed to eMMC partitions, called "dtb" and "dtbo" respectively.

[U-Boot] [PATCH 1/3] common: Let board decide if env should be loaded

Add board_should_load_env() hook which lets board code decide whether environment should be loaded. This is useful when restoring the board over ie. JTAG where the environment may interfere and where it may be desired to ignore the environment present on the board. The return value of

Re: [U-Boot] [PATCHv1 14/14] reset: remove request and free functions

+Stephen for comment Hi Dinh, On 14 April 2018 at 12:51, Dinh Nguyen wrote: > The request and free reset functions are not really used for any useful > purpose but for debugging. We can safely remove them. The API is set to line up with clocks. I think in general we do

Re: [U-Boot] [PATCHv1 14/14] reset: remove request and free functions

On 04/16/2018 12:43 PM, Simon Glass wrote: +Stephen for comment Hi Dinh, On 14 April 2018 at 12:51, Dinh Nguyen wrote: The request and free reset functions are not really used for any useful purpose but for debugging. We can safely remove them. The API is set to line

[U-Boot] [PATCH] ARM: rmobile: Disable SDHI on R8A77970 V3M Eagle

The SDHI is not routed to a slot on the Eagle, so disable it. Signed-off-by: Marek Vasut Cc: Nobuhiro Iwamatsu --- configs/r8a77970_eagle_defconfig | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git

Re: [U-Boot] [PATCH] sunxi: improve throughput in the sunxi_mmc driver

On Fri, Apr 06, 2018 at 07:54:47AM +0200, Maxime Ripard wrote: > Hi Jaehoon, > > On Wed, Mar 21, 2018 at 12:18:58PM +0100, Maxime Ripard wrote: > > From: Philipp Tomsich > > > > Throughput tests have shown the sunxi_mmc driver to take over 10s to > > read

Re: [U-Boot] [PATCHv1 14/14] reset: remove request and free functions

On 04/16/2018 01:51 PM, Stephen Warren wrote: > On 04/16/2018 12:43 PM, Simon Glass wrote: >> +Stephen for comment >> >> Hi Dinh, >> >> On 14 April 2018 at 12:51, Dinh Nguyen wrote: >>> The request and free reset functions are not really used for any useful >>> purpose but

Re: [U-Boot] [PATCH v3 00/17] warp7: Enable automated OPTEE/HAB boot flow

On Fri, Apr 13, 2018 at 12:31 PM, Bryan O'Donoghue wrote: > Bryan O'Donoghue (17): > imximage: Specify default IVT offset in IMX image > warp7: hab: Add a CSF location definition > warp7: hab: Set environment variable indicating HAB enable > warp7: defconfig:

Re: [U-Boot] [PATCH] sunxi: improve throughput in the sunxi_mmc driver

Hi On Mon, Apr 16, 2018 at 9:55 PM, Maxime Ripard wrote: > On Fri, Apr 06, 2018 at 07:54:47AM +0200, Maxime Ripard wrote: >> Hi Jaehoon, >> >> On Wed, Mar 21, 2018 at 12:18:58PM +0100, Maxime Ripard wrote: >> > From: Philipp Tomsich

[U-Boot] [PATCH 2/3] ARM: rmobile: Ignore U-Boot env when started via JTAG on Porter

When U-Boot is started via JTAG, ignore the installed environment as it may interfere with the recovery of the board. Signed-off-by: Marek Vasut Cc: Nobuhiro Iwamatsu Cc: Tom Rini --- board/renesas/porter/porter.c | 10

[U-Boot] [PATCH 3/3] ARM: rmobile: Ignore U-Boot env when started via JTAG on Stout

When U-Boot is started via JTAG, ignore the installed environment as it may interfere with the recovery of the board. Signed-off-by: Marek Vasut Cc: Nobuhiro Iwamatsu Cc: Tom Rini --- board/renesas/stout/stout.c | 10

Re: [U-Boot] Please pull u-boot-x86 (take 2)

On Mon, Apr 16, 2018 at 11:01:25PM +0800, Bin Meng wrote: > Hi Tom, > > This includes some fixes and enhancements to VxWorks booting support, > as well as some mods to x86 I/O functions. > > The following changes since commit ebca902aeb3af3eaedd2787928184ad84a86b98f: > > Merge

[U-Boot] [PATCH v2 0/8] efi_loader: fixes for EFI_DEVICE_PATH_UTILITIES_PROTOCOL

We have merged into v2018.05-rc2 a first implementation of the EFI_DEVICE_PATH_UTILITIES_PROTOCOL. The current implementation does not correctly handle multi instance device paths. This patch series * fixes handling of multi instance device paths * adds missing services of the

[U-Boot] [PATCH v2 7/8] efi_loader: complete EFI_DEVICE_PATH_UTILITIES_PROTOCOL

The missing services of the EFI_DEVICE_PATH_UTILITIES_PROTOCOL are implemented. Signed-off-by: Heinrich Schuchardt --- v2 no change --- include/efi_api.h | 1 + include/efi_loader.h | 9 ++

[U-Boot] [PATCH v2 8/8] efi_selftest: test EFI_DEVICE_PATH_UTILITIES_PROTOCOL

Provide unit tests for the EFI_DEVICE_PATH_UTILITIES_PROTOCOL. Signed-off-by: Heinrich Schuchardt --- v2 add more comments, rename a variable --- lib/efi_selftest/Makefile | 1 + .../efi_selftest_devicepath_util.c| 286

[U-Boot] [PATCH v2 1/8] efi_selftest: do not execute test if setup failed

Executing a test after failed setup may lead to unexpected behavior like an illegal memory access. So after a setup failure we should skip to teardown. Signed-off-by: Heinrich Schuchardt --- v2 no change --- include/efi_selftest.h | 2 ++

[U-Boot] [PATCH v2 2/8] efi_selftest: fix typo in efi_selftest_devicepath.c

%s/provice/provide/ Signed-off-by: Heinrich Schuchardt --- v2 no change --- lib/efi_selftest/efi_selftest_devicepath.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/efi_selftest/efi_selftest_devicepath.c

[U-Boot] [PATCH v2 6/8] efi_loader: correcty determine total device path length

Device paths may consist of multiple instances. Up to now we have only considered the size of the first instance. For the services of the EFI_DEVICE_PATH_UTILITIES_PROTOCOL in most cases the total length of the device path is relevant. So let's rename efi_dp_size() to efi_dp_instance_size() and

[U-Boot] [PATCH v2 5/8] efi_loader: correctly determine length of empty device path

efi_dp_size() is meant to return the device path length without the end node. The length of a device path containing only an end node was incorrectly reported as 4. Signed-off-by: Heinrich Schuchardt --- v2 no change --- lib/efi_loader/efi_device_path.c | 2 ++ 1

[U-Boot] [PATCH v2 4/8] efi_loader: fix AppendDevicePath

The logic of the AppendDevicePath service of the EFI_DEVICE_PATH_UTILITIES_PROTOCOL is incorrectly implemented: * if both paths are NULL an end node has to be returned * if both paths are not NULL the end node of the second device path has to be kept Signed-off-by: Heinrich Schuchardt

[U-Boot] [PATCH v2 3/8] efi_loader: implement CreateDeviceNode

Implement the CreateDeviceNode service of the device path utility protocol. Signed-off-by: Heinrich Schuchardt --- v2 no change --- include/efi_loader.h | 5 - lib/efi_loader/efi_device_path.c | 15 +++

Re: [U-Boot] Re-introducing support for OLD hardware

Hi there Thanks for the advice. The DTP append work-around sounds like a horrible hack that might come to bite me later, so I am going to rather go with re-introducing SMDK6410 back into the U-boot and maintain it. The benefits are then of course that we will be retrofitting something modern in

Re: [U-Boot] [PATCH V4 1/2] imx6: Convert sabrelite and nitrogen6x boards to distro boot support

Hi Guillaume, On Thu, Apr 12, 2018 at 03:28:21PM +0200, Guillaume GARDET wrote: > Boot tested on sabrelite board. > > Signed-off-by: Guillaume GARDET > Cc: Troy Kisky > Cc: Stefano Babic > Cc: Fabio Estevam

[U-Boot] [PATCH 2/6] imx7: psci: save context id in cpu_on command

Replace the psci_save_target_pc call by the new function psci_save(cpu, pc,context_id) Signed-off-by: Patrick Delaunay --- arch/arm/mach-imx/mx7/psci.S | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/arm/mach-imx/mx7/psci.S

[U-Boot] [PATCH 4/6] uniphier: psci: save context id in cpu_on command

Replace the psci_save_target_pc call by the new function psci_save(cpu, pc,context_id) Signed-off-by: Patrick Delaunay --- arch/arm/mach-uniphier/arm32/psci.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/arch/arm/mach-uniphier/arm32/psci.c

[U-Boot] [PATCH v2 3/3] arm: stm32mp1: add PSCI support

Add PSCI v1.0 support for Linux and manage PSCI state for each CPU (affinity 0 level) with all mandatory functions: - PSCI_VERSION - CPU_SUSPEND - CPU_OFF - CPU_ON - AFFINITY_INFO - SYSTEM_OFF - SYSTEM_RESET - PSCI_FEATURES and 1 optional to avoid Linux warning - MIGRATE_INFO_TYPE Signed-off-by:

[U-Boot] [PATCH 6/6] psci: arm: remove armv7 function psci_save_target_pc

This function is no more used, and replaced by psci_save which save also context id as requested by PSCI requirements. Even if the context id is not used by Linux, it should be saved and restored in r0 when the CPU_ON is performed. Signed-off-by: Patrick Delaunay ---

[U-Boot] [PATCH 3/6] tegra: psci: save context id in cpu_on command

Replace the psci_save_target_pc call by the new function psci_save(cpu, pc,context_id) Signed-off-by: Patrick Delaunay --- arch/arm/mach-tegra/psci.S | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/arm/mach-tegra/psci.S

Re: [U-Boot] [PATCH] mmc: mv_sdhci: zero out sdhci_host structure

On 12.04.2018 12:24, Stefan Roese wrote: Hi Matt, On 27.03.2018 19:53, Matt Pelland wrote: The mv_sdhci driver was not zeroing the sdhci_host structure it allocates causing random access violations in parts of the mmc core where the "ops" member pointers are checked and called if not NULL.

[U-Boot] [PATCH v2 1/3] arm: psci: save context id for cpu_on PSCI command

Save and use the 3rd parameter of PSCI CPU_ON request: context_id. The context_id parameter is only meaningful to the caller. U-Boot PSCI preserves a copy of the value passed in this parameter. Following wakeup from a powerdown state, U-BOOT PSCI places this value in R0 when it first enters the

[U-Boot] [PATCH v2 2/3] arm: psci: add a weak function psci_arch_cpu_entry

The added function psci_arch_cpu_entry() is called during psci_cpu_entry() and can be used by arch to handle PSCI state transition from ON_PENDING to ON. The default weak function is empty: not behavior change. Signed-off-by: Patrick Delaunay --- Changes in v2: None

[U-Boot] [PATCH 1/6] ls102xa: psci: save context id in cpu_on command

Replace the psci_save_target_pc call by the new function psci_save(cpu, pc,context_id) Signed-off-by: Patrick Delaunay --- arch/arm/cpu/armv7/ls102xa/psci.S | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/arm/cpu/armv7/ls102xa/psci.S

[U-Boot] [PATCH 5/6] sunxi: psci: save context id in cpu_on command

Replace the psci_save_target_pc call by the new function psci_save(cpu, pc,context_id) Signed-off-by: Patrick Delaunay --- arch/arm/cpu/armv7/sunxi/psci.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/arch/arm/cpu/armv7/sunxi/psci.c

[U-Boot] [PATCH] serial: Remove duplicated line in Makefile

The line "-obj-$(CONFIG_STM32_SERIAL) += serial_stm32.o" is found twice in Makefile. Fixes: ae74de0dfd45 ("serial: stm32: Rename serial_stm32x7.c to serial_stm32.c" Signed-off-by: Patrice Chotard --- drivers/serial/Makefile | 1 - 1 file changed, 1 deletion(-) diff

Re: [U-Boot] [PATCH] arm,imx6: fix PAD_CTL_SPEED_LOW constant

Hello Mark, Am 16.04.2018 um 18:11 schrieb Mark Jonas: For most i.MX6 processors the PAD_CTL_SPEED_LOW constant is the same. Only the i.MX6 SoloLite is an exemption. So far the code did not consider that. Additionally, for a few i.MX6 processors the code used the wrong value for the constant.

Re: [U-Boot] [PATCH 1/3] common: Let board decide if env should be loaded

On 04/16/2018 10:44 PM, Marek Vasut wrote: > Add board_should_load_env() hook which lets board code decide whether > environment should be loaded. This is useful when restoring the board > over ie. JTAG where the environment may interfere and where it may be > desired to ignore the environment

[U-Boot] [PATCH 1/2] ARM: rmobile: Ignore U-Boot env when started via JTAG on Stout

When U-Boot is started via JTAG, ignore the installed environment as it may interfere with the recovery of the board. Signed-off-by: Marek Vasut Cc: Nobuhiro Iwamatsu --- board/renesas/stout/stout.c | 15 +++ 1 file changed, 15

[U-Boot] [PATCH 2/2] ARM: rmobile: Ignore U-Boot env when started via JTAG on Porter

When U-Boot is started via JTAG, ignore the installed environment as it may interfere with the recovery of the board. Signed-off-by: Marek Vasut Cc: Nobuhiro Iwamatsu --- board/renesas/porter/porter.c | 16 1 file changed,

Re: [U-Boot] part: Disable CONFIG_SPL_ISO_PARTITION by default

On Thu, Apr 12, 2018 at 09:58:44AM +0200, Alexander Graf wrote: > We enabled CONFIG_ISO_PARTITION by default for distro boot, so that U-Boot > could load distro images that usually get shipped as iso images. These images > usually come with a board agnostic boot environment. > > However, there

Re: [U-Boot] [U-Boot, v2] env: Relocate env drivers if manual reloc is required

On Fri, Apr 13, 2018 at 07:57:21AM +0200, Michal Simek wrote: > From: Siva Durga Prasad Paladugu > > Relocate env drivers if manual relocation is enabled. This > patch fixes the issue of u-boot hang incase if env is > present in any of the flash devices. > >

Re: [U-Boot] doc: Update git-mailrc entry for lukma (lu...@denx.de)

On Sun, Apr 15, 2018 at 09:50:11PM +0200, Lukasz Majewski wrote: > Signed-off-by: Lukasz Majewski Applied to u-boot/master, thanks! -- Tom signature.asc Description: PGP signature ___ U-Boot mailing list U-Boot@lists.denx.de

Re: [U-Boot] [U-Boot, v2] Kconfig: Enlarge default SYS_MALLOC_F_LEN for AM33XX

On Thu, Apr 12, 2018 at 06:09:58PM +0200, Sjoerd Simons wrote: > Since commit 8e14ba7bd524 ("gpio: omap_gpio: Add DM_FLAG_PRE_RELOC > flag") omap GPIO gets bound before relocation. Unfortunately due to > this, on at least the beaglebone black, the pre-relocation memory pool > gets exhausted

Re: [U-Boot] serial: Remove duplicated line in Makefile

On Mon, Apr 16, 2018 at 10:35:08AM +0200, Patrice Chotard wrote: > The line "-obj-$(CONFIG_STM32_SERIAL) += serial_stm32.o" > is found twice in Makefile. > > Fixes: ae74de0dfd45 ("serial: stm32: Rename serial_stm32x7.c to > serial_stm32.c" > > Signed-off-by: Patrice Chotard

Re: [U-Boot] [U-Boot, 1/1] env: mmc/fat/ext4: undefined reference to `mmc_initialize'

On Sat, Apr 14, 2018 at 03:41:00PM +0200, Heinrich Schuchardt wrote: > For CONFIG_ENV_FAT_INTERFACE != 'mmc' a link error > env/fat.c:93: undefined reference to `mmc_initialize' > occurs if CONFIG_MMC_SUPPORT is not enabled. > > Fixes: 26862b4a40c3 ("env: mmc/fat/ext4: make sure that the MMC

[U-Boot] [ANN] U-Boot v2018.05-rc2 released

Hey all, It's release day and v2018.05-rc2 is out. I think I've got my queue cleaned up since vacation, and I think most custodians have cleared theirs out as well. I am hopeful that we'll just be taking in fixes and Kconfig migrations until the release at this point. Things look on track for

Re: [U-Boot] [Feature] Android Fastboot over Ethernet

Hi Alex, > Hi all, > > Android Things on rpi supports fastboot over udp since most rpis don't > expose a suitable USB port for fastboor over USB. It also uses the A/B > booting mechanism similar to Pixel phones. > > The U-Boot code for the latest Android Things preview is in AOSP: >

Re: [U-Boot] [PATCH] mtd: cfi_flash: Make live-tree compatible

On 28.03.2018 14:38, Mario Six wrote: Make the cfi_flash driver compatible with a live device tree. Signed-off-by: Mario Six --- drivers/mtd/cfi_flash.c | 21 +++-- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/drivers/mtd/cfi_flash.c

Re: [U-Boot] [PATCH v2 01/18] doc: vxworks: Minor update for clarity

On Thu, Apr 12, 2018 at 1:02 PM, Bin Meng wrote: > This corrects a typo and updates several places for clarity. > > Signed-off-by: Bin Meng > Reviewed-by: Christian Gmeiner > --- > > Changes in v2: None > > doc/README.vxworks

Re: [U-Boot] [PATCH v2 08/18] elf: Add ELF64 related structure defines

On Fri, Apr 13, 2018 at 12:41 AM, Simon Glass wrote: > On 11 April 2018 at 23:02, Bin Meng wrote: >> This adds ELF header, program header and section header structure >> defines for the 64-bit ELF image. >> >> Signed-off-by: Bin Meng >>

Re: [U-Boot] [PATCH v2 09/18] elf: Add a very simple ELF64 loader

On Fri, Apr 13, 2018 at 12:42 AM, Simon Glass wrote: > On 11 April 2018 at 23:02, Bin Meng wrote: >> This adds a very simple ELF64 loader via program headers, similar >> to load_elf_image_phdr() that we already have. >> >> Signed-off-by: Bin Meng

Re: [U-Boot] [PATCH v2 12/18] x86: Change default FRAMEBUFFER_VESA_MODE of some boards

On Fri, Apr 13, 2018 at 12:42 AM, Simon Glass wrote: > On 11 April 2018 at 23:02, Bin Meng wrote: >> This changes some boards' default FRAMEBUFFER_VESA_MODE to use 32-bit >> pixel format for better VxWorks compatibility. >> >> Signed-off-by: Bin Meng

Re: [U-Boot] [PATCH v2 13/18] pci: video: Only print out when everything is OK

On Fri, Apr 13, 2018 at 12:42 AM, Simon Glass wrote: > On 11 April 2018 at 23:02, Bin Meng wrote: >> If video initialization fails, the "Video:" output message will be >> mixed with the next console log. Change to print out such message >> only when

Re: [U-Boot] [PATCH v2 11/18] video: vesa: Change default FRAMEBUFFER_VESA_MODE

On Fri, Apr 13, 2018 at 12:42 AM, Simon Glass wrote: > On 11 April 2018 at 23:02, Bin Meng wrote: >> This changes the default FRAMEBUFFER_VESA_MODE to use 32-bit pixel >> format for better VxWorks compatibility. >> >> Signed-off-by: Bin Meng

Re: [U-Boot] [PATCH v2 04/18] vxworks: x86: Rename e820info to e820_info

On Thu, Apr 12, 2018 at 3:26 PM, Christian Gmeiner wrote: > 2018-04-12 7:02 GMT+02:00 Bin Meng : >> This changes 'struct e820info' to 'struct e820_info' to conform >> with the coding style. >> >> Signed-off-by: Bin Meng > >

Re: [U-Boot] [PATCH v2 10/18] bios: vesa: Guard setting vesa mode with CONFIG_FRAMEBUFFER_SET_VESA_MODE

On Fri, Apr 13, 2018 at 12:42 AM, Simon Glass wrote: > Hi Bin, > > On 11 April 2018 at 23:02, Bin Meng wrote: >> If CONFIG_FRAMEBUFFER_SET_VESA_MODE is not set, don't switch >> graphics card to VESA mode. This applies to both native mode >> and emulator

Re: [U-Boot] [PATCH v2 17/18] bootvx: x86: Assign bootaddr based on kernel memory base

On Thu, Apr 12, 2018 at 1:02 PM, Bin Meng wrote: > On VxWorks x86 its bootline address is at a pre-defined offset @ > 0x1200. If 'bootaddr' is not passed via environment variable, we > assign its value based on the kernel memory base address. > > Signed-off-by: Bin Meng

Re: [U-Boot] [PATCH v2 18/18] doc: vxworks: Update x86 specific instructions

On Thu, Apr 12, 2018 at 1:02 PM, Bin Meng wrote: > This updates the doc of booting VxWorks, like loading an x64 kernel, > and how to make VxWorks graphics console driver work. > > Signed-off-by: Bin Meng > > --- > > Changes in v2: > - update the graphics

Re: [U-Boot] [PATCH v2 06/18] x86: Rename e820entry to e820_entry

On Thu, Apr 12, 2018 at 3:28 PM, Christian Gmeiner wrote: > 2018-04-12 7:02 GMT+02:00 Bin Meng : >> This changes 'struct e820entry' to 'struct e820_entry' to conform >> with the coding style. >> >> Signed-off-by: Bin Meng > >

Re: [U-Boot] [PATCH v2 02/18] bootvx: x86: Prepare e820 related stuff from the given kernel memory base address

On Thu, Apr 12, 2018 at 3:25 PM, Christian Gmeiner wrote: > 2018-04-12 7:02 GMT+02:00 Bin Meng : >> At present two environment variables 'e820data'/'e820info' are required >> to boot a VxWorks x86 kernel, but this is superfluous. The offset of >>

Re: [U-Boot] [PATCH v2 03/18] bootvx: x86: Explicitly clear the bootloader image size

On Fri, Apr 13, 2018 at 12:41 AM, Simon Glass wrote: > On 11 April 2018 at 23:02, Bin Meng wrote: >> VxWorks bootloader stores its size at a pre-defined offset @ 0x5004. >> Later when VxWorks kernel boots up and system memory information is >> retrieved

Re: [U-Boot] [PATCH v2 15/18] bootvx: Refactor the bootline copy codes a little bit

On Fri, Apr 13, 2018 at 12:42 AM, Simon Glass wrote: > On 11 April 2018 at 23:02, Bin Meng wrote: >> There is a small duplication in do_bootvx() that does the bootline >> copy. Refactor this a little bit to make it simpler. >> >> Signed-off-by: Bin Meng

Re: [U-Boot] [PATCH v2 05/18] x86: Use 'unsigned int' in install_e820_map() functions

On Thu, Apr 12, 2018 at 3:27 PM, Christian Gmeiner wrote: > 2018-04-12 7:02 GMT+02:00 Bin Meng : >> This fixes the following checkpatch warning: >> >> warning: Prefer 'unsigned int' to bare use of 'unsigned' >> >> Signed-off-by: Bin Meng

[U-Boot] Please pull u-boot-x86

Hi Tom, This includes some fixes and enhancements to VxWorks booting support, as well as some mods to x86 I/O functions. The following changes since commit ebca902aeb3af3eaedd2787928184ad84a86b98f: Merge git://git.denx.de/u-boot-imx (2018-04-15 08:43:50 -0400) are available in the git

Re: [U-Boot] [PATCH v2 16/18] bootvx: Exit if bootline address is not specified

On Thu, Apr 12, 2018 at 1:02 PM, Bin Meng wrote: > Exit the 'bootvx' command if bootline address is not specified. > > Signed-off-by: Bin Meng > --- > > Changes in v2: None > > cmd/elf.c | 109 >

Re: [U-Boot] [PATCH v2 07/18] elf: Clean up the ELF header file

On Thu, Apr 12, 2018 at 3:29 PM, Christian Gmeiner wrote: > 2018-04-12 7:02 GMT+02:00 Bin Meng : >> Fix various style violations in elf.h >> - use correct comment format if the comment fits in just one line >> - remove the ending period for the

Re: [U-Boot] [PATCH v2 14/18] bootvx: x86: Make VxWorks EFI console driver happy

On Fri, Apr 13, 2018 at 12:42 AM, Simon Glass wrote: > On 11 April 2018 at 23:02, Bin Meng wrote: >> When booting from EFI BIOS, VxWorks bootloader stores the EFI GOP >> framebuffer info at a pre-defined offset @ 0x6100. When VxWorks >> kernel boots up, its

Re: [U-Boot] [PATCH] x86: Rename coreboot-x86 to coreboot

On Fri, Apr 13, 2018 at 5:51 PM, Bin Meng wrote: > On Fri, Apr 13, 2018 at 4:04 AM, Simon Glass wrote: >> We only use coreboot as a target on x86 platforms, since on ARM platforms >> U-Boot always runs as the primary boot loader. Rename the coreboot-x86 >>

Re: [U-Boot] [Feature] Android Fastboot over Ethernet

Hi all, Android Things on rpi supports fastboot over udp since most rpis don't expose a suitable USB port for fastboor over USB. It also uses the A/B booting mechanism similar to Pixel phones. The U-Boot code for the latest Android Things preview is in AOSP:

Re: [U-Boot] [PATCH 03/12] libfdt: Safer access to strings section

2018-04-14 23:42 GMT+09:00 Warner Losh : > On Fri, Apr 13, 2018 at 9:43 PM, David Gibson > wrote: > >> On Fri, Apr 13, 2018 at 12:53:19PM -0400, Tom Rini wrote: >> > On Thu, Apr 12, 2018 at 02:39:19PM +1000, David Gibson wrote: >> > > On Tue, Apr 10,

  1   2   >