Re: [U-Boot] [RFC] Reserve ATF memory on Marvell Armdada 3700/7K/8K

Hello, I think I suffered from random kernel crashed due to this issue. Could you please also submit this patch to downstream Marvell u-boot at github PR? 31.03.2018 17:13, Mark Kettenis пишет: > Currently U-Boot doesn't make any effort to reserve the memory used by > ARM Trusted Firmware on the

Re: [U-Boot] [PATCH 2/2] image: fit: Show information about OS type in firwmare case too

On 30.3.2018 10:40, Simon Glass wrote: > On 26 March 2018 at 22:31, Michal Simek wrote: >> SPL ATF implementation requires FIT image with partitions where the one >> is Firmware/ATF and another one Firmware/U-Boot. OS field is used for >> recording that difference that's why make sense to show val

Re: [U-Boot] [PATCH v2] tools: buildman: Don't use the working dir as build dir

Hi, On Mon, 2 Apr 2018 02:43:12 -0600 Simon Glass wrote: > From: Lothar Waßmann > > When the U-Boot base directory happens to have the same name as the branch > that buildman is directed to use via the '-b' option and no output > directory is specified with '-o', buildman happily starts removin

Re: [U-Boot] [PATCH 1/6] arm64: zynqmp: Add support for zcu100 aka 96ultra board

Hi, On 31.3.2018 23:38, Alexander Graf wrote: > > > On 28.03.18 17:06, Michal Simek wrote: >> Add support for Xilinx zcu100. >> >> Signed-off-by: Michal Simek > > When I apply this on top of 2018.03 and boot it on a ZCU100 with FSBL, > something seems to get stuck in i2c enumeration: > > PMUF

Re: [U-Boot] [PATCH v2 5/6] sunxi: add code for recalculating the DRAM size in U-Boot

On Thu, Mar 29, 2018 at 01:21:38PM +0100, Andre Przywara wrote: > Hi, > > On 29/03/18 10:37, Maxime Ripard wrote: > > On Wed, Mar 28, 2018 at 07:31:51PM +0800, Icenowy Zheng wrote: > >> 于 2018年3月28日 GMT+08:00 下午7:28:07, Maxime Ripard > >> 写到: > >>> On Mon, Mar 26, 2018 at 03:11:04PM +0800, Iceno

[U-Boot] [PATCH v2 u-boot 0/2] reset: Add get/assert/deassert/release for bulk of reset signals

This patch adds a "bulk" API to the reset API in order to get/deassert/ assert/release a group of reset signals associated with a device. This bulk API will avoid adding a copy of the same code to manage a group of reset signals in drivers. This serie and the "clk bulk" serie is necessary and sug

[U-Boot] [PATCH v2 u-boot 1/2] reset: Add get/assert/deassert/release for bulk of reset signals

This patch adds a "bulk" API to the reset API in order to get/deassert/ assert/release a group of reset signals associated with a device. This bulk API will avoid adding a copy of the same code to manage a group of reset signals in drivers. Signed-off-by: Neil Armstrong --- drivers/reset/reset-

[U-Boot] [PATCH v2 u-boot 2/2] reset: add sandbox test for bulk API

This patch adds the bulk reset API tests for the sandbox test suite. Unlike the main test, it also check the "other" reset signal using the bulk API and checks if the resets are correctly asserted/deasserted. To allow the bulk API to work, and avoid changing the DT, the number of resets of the sa

[U-Boot] [PATCH v2 u-boot 0/2] clk: Add get/enable/disable/release for a bulk of clocks

This patch adds a "bulk" API to the clock API in order to get/enable/disable /release a group of clocks associated with a device. This bulk API will avoid adding a copy of the same code to manage a group of clocks in drivers. This serie and the "reset bulk" serie is necessary and suggested by Mar

[U-Boot] [PATCH v2 u-boot 2/2] clk: add sandbox test for bulk API

This patch adds the bulk clock API tests for the sandbox test suite. It's very similar to the main test but only uses the _bulk() API and checks if the clocks are correctly enabled/disabled. Signed-off-by: Neil Armstrong --- arch/sandbox/include/asm/clk.h | 32

[U-Boot] [PATCH v2 u-boot 1/2] clk: Add get/enable/disable/release for a bulk of clocks

This patch adds a "bulk" API to the clock API in order to get/enable/disable /release a group of clocks associated with a device. This bulk API will avoid adding a copy of the same code to manage a group of clocks in drivers. Signed-off-by: Neil Armstrong --- drivers/clk/clk-uclass.c | 59 +

Re: [U-Boot] [PATCH] arm: stm32mp1: add PSCI support

Hi Tom > From: Tom Rini [mailto:tr...@konsulko.com] > > On Thu, Mar 29, 2018 at 04:59:21PM +, Patrick DELAUNAY wrote: > > Hi Mark, > > > > > > > From: Mark Rutland [mailto:mark.rutl...@arm.com] > > > > > > Hi, > > > > > > On Tue, Mar 20, 2018 at 01:59:03PM +0100, Patrick Delaunay wrote: > >

Re: [U-Boot] [PATCH v2 5/6] sunxi: add code for recalculating the DRAM size in U-Boot

Hi, On 03/04/18 10:29, Maxime Ripard wrote: > On Thu, Mar 29, 2018 at 01:21:38PM +0100, Andre Przywara wrote: >> Hi, >> >> On 29/03/18 10:37, Maxime Ripard wrote: >>> On Wed, Mar 28, 2018 at 07:31:51PM +0800, Icenowy Zheng wrote: 于 2018年3月28日 GMT+08:00 下午7:28:07, Maxime Ripard 写到:

Re: [U-Boot] [PATCH v3 00/20] Bring NAND support to Nintendo NES Classic

On Wed, Feb 28, 2018 at 08:51:42PM +0100, Miquel Raynal wrote: > Hello, > > This series first adds fixes and enhancements to sunxi NAND drivers (SPL > and U-Boot). Once this is done, the SPL NAND driver is converted to use > PIO instead of DMA with the goal to support all SoCs with this IP > witho

Re: [U-Boot] [PATCH v2 5/6] sunxi: add code for recalculating the DRAM size in U-Boot

于 2018年4月3日 GMT+08:00 下午6:13:17, Andre Przywara 写到: >Hi, > >On 03/04/18 10:29, Maxime Ripard wrote: >> On Thu, Mar 29, 2018 at 01:21:38PM +0100, Andre Przywara wrote: >>> Hi, >>> >>> On 29/03/18 10:37, Maxime Ripard wrote: On Wed, Mar 28, 2018 at 07:31:51PM +0800, Icenowy Zheng wrote: >

Re: [U-Boot] [PATCH v2 5/6] sunxi: add code for recalculating the DRAM size in U-Boot

> On 3 Apr 2018, at 12:39, Icenowy Zheng wrote: > > > > 于 2018年4月3日 GMT+08:00 下午6:13:17, Andre Przywara > 写到: >> Hi, >> >> On 03/04/18 10:29, Maxime Ripard wrote: >>> On Thu, Mar 29, 2018 at 01:21:38PM +0100, Andre Przywara wrote: Hi, On 29/03/1

Re: [U-Boot] [PATCH v2 5/6] sunxi: add code for recalculating the DRAM size in U-Boot

On Tue, Apr 03, 2018 at 11:13:17AM +0100, Andre Przywara wrote: > For hacking it, see my implementation in v1, which assumes the > only size supported bigger than 2GiB is 3GiB (which is > acceptable on sunxi, but might not work on other platforms). > > As Andre said, that f

Re: [U-Boot] [PATCH v2 5/6] sunxi: add code for recalculating the DRAM size in U-Boot

Hi, On 03/04/18 12:34, Maxime Ripard wrote: > On Tue, Apr 03, 2018 at 11:13:17AM +0100, Andre Przywara wrote: >> For hacking it, see my implementation in v1, which assumes the >> only size supported bigger than 2GiB is 3GiB (which is >> acceptable on sunxi, but might not work on other

Re: [U-Boot] [PATCH v2 1/5] Migrate CONFIG_DRIVER_TI_CPSW to Kconfig

On 02.04.2018 17:43, Alex Kiernan wrote: > On Mon, Apr 2, 2018 at 12:13 PM, Felix Brack wrote: >> Hi Alex, >> >> On 01.04.2018 11:22, Alex Kiernan wrote: >>> This converts CONFIG_DRIVER_TI_CPSW to Kconfig >>> >>> Signed-off-by: Alex Kiernan >>> Acked-by: Joe Hershberger >>> --- >>> >>> Changes i

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

Has there been any development to support Android Fastboot Ethernet feature in U-Boot ? https://android.googlesource.com/platform/system/core/+/android-7.1.2_r36/fastboot/fastboot_protocol.txt The target board has not USB device port available to flash the on-board eMMC. Flashing the eMMC via

[U-Boot] [PATCH v2 0/3] This series adds support for gpio-leds "default-state" property. The

From: Patrick Bruenn main usecase in mind are LEDs which indicate a state like "power on". With this patchset applied, all you have to do is: Add a gpio-led node with 'default-state = "on";' property to your device tree. And the LED will automatically light up during U-Boot startup. Changes in v

[U-Boot] [PATCH v2 1/3] dm: led: Support "default-state" property

From: Patrick Bruenn Add support for the device tree property "default-state". This feature might be useful for LEDs indicating "power on" or similar states. Note: Even with this commit gpio-leds remain in reset state. That's because the led_gpio is not probed until DM_FLAG_ACTIVATED is set. Si

[U-Boot] [PATCH v2 3/3] dm: led: add testcase for "default-state" property

From: Patrick Bruenn Add two more gpio-leds to sandbox test device tree with default-state property set to "on"/"off". Add dm_test_led_default_state() to check that these new LED's are set to LEDST_ON and LEDST_OFF. Signed-off-by: Patrick Bruenn --- patman complains about: test/dm/led.c:45: che

[U-Boot] [PATCH v2 2/3] dm: led: auto probe() LEDs with "default-state"

From: Patrick Bruenn To avoid board specificy LED activation code, automatically activate gpio-leds with "default-state" property during bind(). Signed-off-by: Patrick Bruenn --- Changes in v2: None drivers/led/led_gpio.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/l

Re: [U-Boot] [PATCH v2 5/6] sunxi: add code for recalculating the DRAM size in U-Boot

于 2018年4月3日 GMT+08:00 下午7:41:41, Andre Przywara 写到: >Hi, > >On 03/04/18 12:34, Maxime Ripard wrote: >> On Tue, Apr 03, 2018 at 11:13:17AM +0100, Andre Przywara wrote: >>> For hacking it, see my implementation in v1, which assumes the >>> only size supported bigger than 2GiB is 3GiB (whic

Re: [U-Boot] [PATCH v2 5/6] sunxi: add code for recalculating the DRAM size in U-Boot

于 2018年4月3日 GMT+08:00 下午7:34:55, Maxime Ripard 写到: >On Tue, Apr 03, 2018 at 11:13:17AM +0100, Andre Przywara wrote: >> For hacking it, see my implementation in v1, which assumes the >> only size supported bigger than 2GiB is 3GiB (which is >> acceptable on sunxi, but might not wor

Re: [U-Boot] [PATCH v2] timer: add High Precision Event Timers (HPET) support

On Tue, Apr 3, 2018 at 2:00 AM, Ivan Gorinov wrote: > On Sat, Mar 31, 2018 at 06:31:03AM -0600, Andy Shevchenko wrote: >> >> > + tl = readl(regs + HPET_MAIN_COUNT_L); >> >> > + th = readl(regs + HPET_MAIN_COUNT_H); >> >> >> >> Ditto. >> > >> > If readq() is defined as t

Re: [U-Boot] [PATCH v2 5/6] sunxi: add code for recalculating the DRAM size in U-Boot

Hi Icenowy, On 03/04/18 12:51, Icenowy Zheng wrote: > > > 于 2018年4月3日 GMT+08:00 下午7:34:55, Maxime Ripard 写到: >> On Tue, Apr 03, 2018 at 11:13:17AM +0100, Andre Przywara wrote: >>> For hacking it, see my implementation in v1, which assumes the >>> only size supported bigger than 2GiB is

Re: [U-Boot] [PATCH] reset: socfpga: add reset driver for SoCFPGA platform

On 03/30/2018 02:45 PM, Marek Vasut wrote: > On 03/30/2018 06:53 PM, Dinh Nguyen wrote: >> Add a DM compatible reset driver for the SoCFPGA platform. >> >> Signed-off-by: Dinh Nguyen >> --- >> drivers/reset/Kconfig | 7 +++ >> drivers/reset/Makefile| 1 + >> drivers/reset/re

Re: [U-Boot] [PATCH] reset: socfpga: add reset driver for SoCFPGA platform

On 04/03/2018 04:04 PM, Dinh Nguyen wrote: > > > On 03/30/2018 02:45 PM, Marek Vasut wrote: >> On 03/30/2018 06:53 PM, Dinh Nguyen wrote: >>> Add a DM compatible reset driver for the SoCFPGA platform. >>> >>> Signed-off-by: Dinh Nguyen >>> --- >>> drivers/reset/Kconfig | 7 +++ >>> dr

Re: [U-Boot] [linux-sunxi] Re: [PATCH v2 5/6] sunxi: add code for recalculating the DRAM size in U-Boot

On Tue, 3 Apr 2018 13:43:43 +0100 Andre Przywara wrote: > Hi Icenowy, > > On 03/04/18 12:51, Icenowy Zheng wrote: > > > > > > 于 2018年4月3日 GMT+08:00 下午7:34:55, Maxime Ripard > > 写到: > >> On Tue, Apr 03, 2018 at 11:13:17AM +0100, Andre Przywara wrote: > >>> For hacking it, see my imple

Re: [U-Boot] [PATCH] reset: socfpga: add reset driver for SoCFPGA platform

On 04/03/2018 09:07 AM, Marek Vasut wrote: [...] > >> >> I have a patchset that tested this code, the i2c support in SoCFPGA was >> converted to DM, and uses this reset framework. Should I send that along >> with this patch in v2? > > Yes please, otherwise this will be just another dead code. >

Re: [U-Boot] [PATCH v3 1/2] warp7: defconfig: Fix CAAM on boot with tip-of-tree

Hi Bryan, 2018-03-31 17:04 GMT-03:00 Bryan O'Donoghue : > Booting the following image with tip-of-tree we get a CAAM DECO error (and > subsequent crash due to a kernel bug in 4.1). > > http://freescale.github.io/#download -> BoardsWaRPboard community - WaRP - > Wearable Reference PlatformFSL Commu

Re: [U-Boot] [PATCH v4 00/19] sunxi: sync H3, H5, A64 DTs from mainline Linux

Hi Andre, On Wed, Mar 14, 2018 at 7:26 AM, Andre Przywara wrote: > A minor update to the v3 version sent earlier this month. > I reworked patch 09 to drop the direct MMC environment for 32-bit Allwinner > boards as well and keep the current MMC offset. > For now I also dropped the two patches cha

[U-Boot] FIT Image with same kernel but different load/entry point

Hi, Is it possible to have one kernel entry in a FIT image with two different load/entry point. I have 2 boards which share the same kernel but doesn't have the same entry/load point. Thanks, Clement ___ U-Boot mailing list U-Boot@lists.denx.de https:/

Re: [U-Boot] [PATCH] reset: socfpga: add reset driver for SoCFPGA platform

On 04/03/2018 04:43 PM, Dinh Nguyen wrote: > > > On 04/03/2018 09:07 AM, Marek Vasut wrote: > > [...] >> >>> >>> I have a patchset that tested this code, the i2c support in SoCFPGA was >>> converted to DM, and uses this reset framework. Should I send that along >>> with this patch in v2? >> >> Y

Re: [U-Boot] [PATCH v2 1/3] dm: led: Support "default-state" property

On 3 April 2018 at 15:31, wrote: > From: Patrick Bruenn > > Add support for the device tree property "default-state". This feature > might be useful for LEDs indicating "power on" or similar states. > > Note: Even with this commit gpio-leds remain in reset state. That's > because the led_gpio is

Re: [U-Boot] [PATCH v2 2/3] dm: led: auto probe() LEDs with "default-state"

On 3 April 2018 at 15:31, wrote: > From: Patrick Bruenn > > To avoid board specificy LED activation code, automatically > activate gpio-leds with "default-state" property during bind(). > > Signed-off-by: Patrick Bruenn > --- > > Changes in v2: None > > drivers/led/led_gpio.c | 9 + >

Re: [U-Boot] [PATCH v2 3/3] dm: led: add testcase for "default-state" property

On 3 April 2018 at 15:31, wrote: > From: Patrick Bruenn > > Add two more gpio-leds to sandbox test device tree with default-state > property set to "on"/"off". > Add dm_test_led_default_state() to check that these new LED's are set to > LEDST_ON and LEDST_OFF. > > Signed-off-by: Patrick Bruenn

Re: [U-Boot] [PATCH 1/3] dm: Add migration plan for CONFIG_BLK

Hi Andre, On 2 April 2018 at 19:00, André Przywara wrote: > Hi, > > On 02/04/18 03:30, Simon Glass wrote: >> >> Hi Andre, >> >> On 2 April 2018 at 09:43, André Przywara wrote: >>> Hi, >>> >>> On 01/04/18 14:19, Tom Rini wrote: On Tue, Mar 27, 2018 at 11:34:19PM +0530, Jagan Teki wrote:

Re: [U-Boot] [PATCH v2 u-boot 2/2] clk: add sandbox test for bulk API

On 3 April 2018 at 17:44, Neil Armstrong wrote: > This patch adds the bulk clock API tests for the sandbox test suite. > > It's very similar to the main test but only uses the _bulk() API and > checks if the clocks are correctly enabled/disabled. > > Signed-off-by: Neil Armstrong > --- > arch/sa

Re: [U-Boot] [PATCH v2 u-boot 2/2] reset: add sandbox test for bulk API

On 3 April 2018 at 17:40, Neil Armstrong wrote: > This patch adds the bulk reset API tests for the sandbox test suite. > > Unlike the main test, it also check the "other" reset signal using the bulk > API > and checks if the resets are correctly asserted/deasserted. > > To allow the bulk API to w

Re: [U-Boot] [PATCH v2 u-boot 1/2] reset: Add get/assert/deassert/release for bulk of reset signals

On 3 April 2018 at 17:40, Neil Armstrong wrote: > This patch adds a "bulk" API to the reset API in order to get/deassert/ > assert/release a group of reset signals associated with a device. > > This bulk API will avoid adding a copy of the same code to manage > a group of reset signals in drivers.

Re: [U-Boot] [PATCH v2 u-boot 1/2] clk: Add get/enable/disable/release for a bulk of clocks

On 3 April 2018 at 17:44, Neil Armstrong wrote: > This patch adds a "bulk" API to the clock API in order to get/enable/disable > /release a group of clocks associated with a device. > > This bulk API will avoid adding a copy of the same code to manage > a group of clocks in drivers. > > Signed-off

Re: [U-Boot] [linux-sunxi] Re: [PATCH v2 5/6] sunxi: add code for recalculating the DRAM size in U-Boot

On 03/04/18 15:13, Siarhei Siamashka wrote: Hi Siarhei, thanks for chiming in! > On Tue, 3 Apr 2018 13:43:43 +0100 > Andre Przywara wrote: >> On 03/04/18 12:51, Icenowy Zheng wrote: I guess we'd need to find another way (put some information in an SRAM somewhere?) to try to do

[U-Boot] [PATCH v2 3/3] efi_selftest: test unaligned memory access

According to the UEFI spec unaligned memory access should be enabled on CPUs supporting it. Signed-off-by: Heinrich Schuchardt --- lib/efi_selftest/Makefile | 4 ++ lib/efi_selftest/efi_selftest_unaligned.c | 67 +++ 2 files changed, 71 insertions(+)

[U-Boot] [PATCH v2 1/3] efi_loader: allow unaligned memory access

The UEFI spec mandates that unaligned memory access should be enabled if supported by the CPU architecture. This patch adds an empty weak function unaligned_access() that can be overridden by an architecture specific routine. Signed-off-by: Heinrich Schuchardt --- cmd/bootefi.c

[U-Boot] [PATCH v2 2/3] arm: armv7: allow unaligned memory access

The UEFI spec mandates that unaligned memory access should be enabled if supported by the CPU architecture. This patch implements the function unaligned_access() to reset the aligned access flag in the system control register (SCTLR). It is called when the bootefi command is invoked. Signed-off-b

[U-Boot] [PATCH v2 0/3] efi_loader: armv7: enable unaligned access

We use the command bootefi to run UEFI executables like GRUB and iPXE. The UEFI spec requires that unaligned access is enabled if the CPU supports it. This is true for armv7. So we should not set bit 1 of the system control register, the alignment bit. Without this patch iPXE snp.efi cannot be ex

[U-Boot] [PATCH 1/1] efi_loader: completely initialize network

Add missing network initialization code. Before the patch the network was only usable if a network command like dhcp or tftp had beed executed. This was visible when interrupting the console countdown and executing bootefi selftest for vexpress_ca15_tc2_defconfig. Signed-off-by: Heinrich Schucha

Re: [U-Boot] [PATCH 1/3] dm: Add migration plan for CONFIG_BLK

On Wed, Apr 04, 2018 at 01:53:17AM +0800, Simon Glass wrote: > Hi Andre, > > On 2 April 2018 at 19:00, André Przywara wrote: > > Hi, > > > > On 02/04/18 03:30, Simon Glass wrote: > >> > >> Hi Andre, > >> > >> On 2 April 2018 at 09:43, André Przywara wrote: > >>> Hi, > >>> > >>> On 01/04/18 14:19

Re: [U-Boot] [PATCH] Makefile: Disable stack-usage check for ARC

On Mon, Apr 02, 2018 at 12:18:02PM +0300, Alexey Brodkin wrote: > With the most recent tools for ARC (arc-2017.09) in case of > "naked" function compiler throws a warning: > -->8- > board/synopsys/hsdk/hsdk.c: In function 'hsdk_core_init_

Re: [U-Boot] [PATCH] Makefile: Disable stack-usage check for ARC

Hi Tom, On Tue, 2018-04-03 at 16:17 -0400, Tom Rini wrote: > On Mon, Apr 02, 2018 at 12:18:02PM +0300, Alexey Brodkin wrote: > > > With the most recent tools for ARC (arc-2017.09) in case of > > "naked" function compiler throws a warning: > > -->8--

Re: [U-Boot] [PATCH] Makefile: Disable stack-usage check for ARC

On Tue, Apr 03, 2018 at 08:21:06PM +, Alexey Brodkin wrote: > Hi Tom, > > On Tue, 2018-04-03 at 16:17 -0400, Tom Rini wrote: > > On Mon, Apr 02, 2018 at 12:18:02PM +0300, Alexey Brodkin wrote: > > > > > With the most recent tools for ARC (arc-2017.09) in case of > > > "naked" function compile

Re: [U-Boot] [PATCH] Makefile: Disable stack-usage check for ARC

Hi Tom, On Tue, 2018-04-03 at 16:25 -0400, Tom Rini wrote: > On Tue, Apr 03, 2018 at 08:21:06PM +, Alexey Brodkin wrote: > > Hi Tom, > > > > On Tue, 2018-04-03 at 16:17 -0400, Tom Rini wrote: > > > On Mon, Apr 02, 2018 at 12:18:02PM +0300, Alexey Brodkin wrote: > > > > > > > With the most re

[U-Boot] [PATCH v2 4/6] efi_loader: correct types for EFI_LOADED_IMAGE_PROTOCOL

We should not use void * but specific types for * device_handle * file_path Signed-off-by: Heinrich Schuchardt --- v2 no change --- include/efi_api.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/include/efi_api.h b/include/efi_api.h index ca8e7849ff..c8a41a499d

[U-Boot] [PATCH v2 0/6] efi_loader: fixes for loaded image protocol

This patch series fixes various bugs in the handling of loaded images. The following new functionality is provided: If a crash occurs the relocation information of loaded EFI images is displayed. --- v2 Merge with "efi_loader: print information about loaded UEFI images" patch ser

[U-Boot] [PATCH v2 2/6] efi_loader: save image relocation address and size

For analyzing crash output the relocation address and size are needed. Save them in the loaded image info. Signed-off-by: Heinrich Schuchardt --- v2 GRUB does not allow the relocated address to be used as ImageBase in the loaded image information. So the relocation address has to

[U-Boot] [PATCH v2 1/6] efi_loader: use efi_uintn_t for LoadImage

We generally use efi_uintn_t where the UEFI spec uses UINTN. Signed-off-by: Heinrich Schuchardt --- v2 Fix typo in commit message. --- include/efi_api.h | 2 +- lib/efi_loader/efi_boottime.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/include/efi_

[U-Boot] [PATCH v2 5/6] efi_loader: new functions to print loaded image information

Introduce functions to print information about loaded images. If we want to analyze an exception in an EFI image we need the offset between the PC and the start of the loaded image. With efi_print_image_info() we can print the necessary information for a single image, e.g. UEFI image start 0x7fd

[U-Boot] [PATCH v2 3/6] efi_loader: ImageSize must be multiple of SectionAlignment

According to the Portable Executable and Common Object File Format Specification the image size must be a multiple of the alignment of sections. Signed-off-by: Heinrich Schuchardt --- v2 no change --- lib/efi_loader/efi_image_loader.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a

[U-Boot] [PATCH v2 6/6] arm: print information about loaded UEFI images

If an exception occurs in a UEFI loaded image we need the start address of the image to determine the relocation offset. This patch adds the necessary lines after the registers in the crash dump. A possible output would be: UEFI image start 0x7fdb4000, size 0xa7b60 pc offset 0x72ca /\snp.efi Wit

[U-Boot] [PATCH 1/2] efi_loader: use correct types in EFI_FILE_PROTOCOL

In the EFI_FILE_PROTOCOL buffer sizes and positions are passed as UINTN and not as u64. Signed-off-by: Heinrich Schuchardt --- include/efi_api.h| 14 + lib/efi_loader/efi_boottime.c| 5 +-- lib/efi_loader/efi_file.c| 47 +++

[U-Boot] [PATCH 2/2] efi_loader: implement EFI_FILE_SYSTEM_INFO

Implement the information type EFI_FILE_SYSTEM_INFO in the service GetInfo() of the EFI_FILE_PROTOCOL. Signed-off-by: Heinrich Schuchardt --- include/efi_api.h | 13 + include/efi_loader.h | 2 ++ lib/efi_loader/efi_file.c | 34 ++ 3 file

[U-Boot] [PATCH 0/2] efi_loader: EFI_FILE_PROTOCOL

This patch series contains correction for the EFI_FILE_PROTOCOL. The formation type EFI_FILE_SYSTEM_INFO in the service GetInfo() of the EFI_FILE_PROTOCOL is implemented. Heinrich Schuchardt (2): efi_loader: use correct types in EFI_FILE_PROTOCOL efi_loader: implement EFI_FILE_SYSTEM_INFO i

[U-Boot] [PATCH 1/1] efi_loader: correctly determine the boot partition

The device path of the loaded image should be set to the partition from which the image was loaded. This requires using the same logic as the load command. Without the patch the device path pointed to the whole disk after executing load mmc 0: 0x4300 FILE and not to the boot partitio

Re: [U-Boot] [PATCH] Makefile: Disable stack-usage check for ARC

On Tue, Apr 03, 2018 at 08:27:20PM +, Alexey Brodkin wrote: > Hi Tom, > > On Tue, 2018-04-03 at 16:25 -0400, Tom Rini wrote: > > On Tue, Apr 03, 2018 at 08:21:06PM +, Alexey Brodkin wrote: > > > Hi Tom, > > > > > > On Tue, 2018-04-03 at 16:17 -0400, Tom Rini wrote: > > > > On Mon, Apr 02,

Re: [U-Boot] [linux-sunxi] Re: [PATCH 1/3] dm: Add migration plan for CONFIG_BLK

> "Tom" == Tom Rini writes: Hi, >> That seems like a good idea to me. > I've lamented before (and I think others have too) that it's really a > shame that gcc treats arm32 and arm64 as totally distinct builds (and > where clang is a win). But I don't think we can require people to have

[U-Boot] [PATCH 1/1] MAINTAINERS: ARM STM STM32MP: correct file paths

Provide correct file paths. Signed-off-by: Heinrich Schuchardt --- MAINTAINERS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index fde77b2b61..510ad12a41 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -201,8 +201,8 @@ ARM STM STM32MP M: Pat

Re: [U-Boot] [PATCH v2] timer: add High Precision Event Timers (HPET) support

On Tue, Apr 03, 2018 at 06:17:42AM -0600, Andy Shevchenko wrote: > >> > If readq() is defined as two read operations in 32-bit code, main counter > >> > rollover (low part overflow, high part increment) can happen between > >> > them. > >> And how this contradicts ther current code? > > It just do

[U-Boot] [PATCH 1/1] get_maintainer.pl: update from Linux kernel v4.16

The most significant change is the addition of the --self-test option which allows to run a consistency check on all MAINTAINERS files. Signed-off-by: Heinrich Schuchardt --- scripts/get_maintainer.pl | 211 ++ 1 file changed, 193 insertions(+), 18 del

[U-Boot] [PATCH v5 00/11] sunxi: update H3/H5/A64 EMAC DT nodes

This is the first half of the DT update series, just updating the EMAC DT nodes, for which the bindings have diverged. Just fixed some checkpatch warnings and rebased (without conflicts) against v2018.05-rc1. As before, this includes the patches to drop the direct MMC environment for all Allwinner

[U-Boot] [PATCH v5 02/11] sunxi: gpio: add missing compatible strings

The sunxi GPIO driver is missing some compatible strings for recent SoCs. While most of the sunxi GPIO code seems to not rely on this (and so works anyway), the sunxi_name_to_gpio() function does and fails at the moment (for instance when resolving the MMC CD pin name). Add the compatible strings f

[U-Boot] [PATCH v5 01/11] sunxi: README.sunxi64: Add hint about non-debug of ARM Trusted Firmware

As we are running into issues where the final U-Boot FIT image file is exceeding our size limit, add a hint to the README.sunxi64 file to point out the possibility of building non-debug versions of the ATF binary. These are about 12KB smaller than the standard debug build, and so allow successful U

[U-Boot] [PATCH v5 05/11] arm: dts: sunxi: update A64 to new EMAC binding

The U-Boot driver for the sun8i-emac was using some preliminary DT binding. Now since Linux got its own driver in v4.15 and our driver can now cope with both bindings, let's convert the DT nodes used for the Pine64+ board over to the new bindings used by the kernel. Signed-off-by: Andre Przywara

[U-Boot] [PATCH v5 10/11] sunxi: revert disabling of features

In January some commits were introduced to mitigate the U-Boot image size issues we encountered on sunxi builds. Now with the MMC environment removed we can bring them back, as we practically don't have a size limit anymore. Signed-off-by: Andre Przywara Acked-by: Maxime Ripard --- cmd/Kconfig

[U-Boot] [PATCH v5 08/11] net: sun8i-emac: remove support for old binding

The original DT binding used by U-Boot's sun8i-emac driver was not really agreed upon, and deviated from the "official" binding now used by the kernel. Since now all U-Boot users have been converted to the new binding, we can remove support for the old DT nodes from the driver. Signed-off-by: Andr

[U-Boot] [PATCH v5 07/11] arm: dts: sunxi: update H5 to new EMAC binding

The U-Boot driver for the sun8i-emac was using some preliminary DT binding. Now since Linux got its own driver in v4.15 and our driver can now cope with both bindings, let's convert the DT nodes used by the OrangePi PC2 over to the new bindings used by the kernel. Signed-off-by: Andre Przywara Ac

[U-Boot] [PATCH v5 06/11] arm: dts: sunxi: update H3 to new EMAC binding

The U-Boot driver for the sun8i-emac was using some preliminary DT binding. Now since Linux got its own driver in v4.15 and our driver can now cope with both bindings, let's convert the DT nodes used by the various H3 boards over to the new bindings used by the kernel. Signed-off-by: Andre Przywar

[U-Boot] [PATCH v5 03/11] net: sun8i-emac: support new pinctrl DT bindings

The Linux kernel driver for the Allwinner pin controller gained support for generic properties, which are now also used in the DTs. The sun8i-emac Ethernet driver for new Allwinner MACs reads the pins from the DT, but so far only supported the old binding. Update the parsing routine to cope with bo

[U-Boot] [PATCH v5 09/11] sunxi: disable direct MMC environment

Since the dawn of time for the Allwinner support in mainline U-Boot we store the environment to the SD card and write directly at 544KB from the beginning of the device. This leads to problems when the U-Boot proper image grows beyond 504KB and eventually overlaps. With one release of having the en

[U-Boot] [PATCH v5 04/11] net: sun8i-emac: add support for new EMAC DT binding

The Ethernet MAC used in newer Allwinner SoCs (H3, A64, H5) got an upstream Linux driver in v4.15. This one uses a slightly different binding from the original one used by the U-Boot driver. The differences to the old binding are: - The "syscon" address is held in a separate node, referenced via a

[U-Boot] [PATCH v5 11/11] Revert "sunxi: Pine64: temporarily remove extra Pine64 non-plus DT"

Now with the MMC environment gone, we have enough space to accommodate the Pine64 "non-plus" .dtb again. This reverts commit 47952b8e42c2790150e16d3d4235b3a1ee0ba9bb. Signed-off-by: Andre Przywara --- configs/pine64_plus_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/configs/pine

Re: [U-Boot] Marvell Armada-38x DDR training code

On Thu, Mar 29, 2018 at 4:01 PM, Chris Packham wrote: > Hi, > > I've posted a couple of improvements to the in-tree ddr training code > but we've known for a while that u-boot proper is a bit behind > Marvell's code for ddr training. And now I really do have a problem on > my board that is fixed b

Re: [U-Boot] [PATCH v2] timer: add High Precision Event Timers (HPET) support

On Wed, Apr 4, 2018 at 7:26 AM, Ivan Gorinov wrote: > On Tue, Apr 03, 2018 at 06:17:42AM -0600, Andy Shevchenko wrote: >> >> > If readq() is defined as two read operations in 32-bit code, main >> >> > counter >> >> > rollover (low part overflow, high part increment) can happen between >> >> > th

Re: [U-Boot] [PATCH v2] timer: add High Precision Event Timers (HPET) support

On Wed, Apr 04, 2018 at 12:15:24PM +0800, Bin Meng wrote: > > Doesn't readX/writeX imply a single I/O operation? > > It may be misleading to define it as two. > > > > Assuming MMX or SSE2 to be supported by all x86 processors, 64-bit I/O > > registers can be accessed as a single operation even in 3

[U-Boot] [PATCH v1 0/2] ARM: mvebu: a38x: updates

This small series represents some low hanging fruit needed before we can bring in the updated version of Marvell's DDR training code. These are things that really shouldn't have been part of the DDR code in the first place but for one reason or another ended up there. Patch 2 is borrowed in part f

[U-Boot] [PATCH v1 2/2] ARM: mvebu: a38x: move sys_env_device_rev_get

Move sys_env_device_rev_get() from the ddr training code to sys_env_lib.c (which currently resides with the serdes code). This brings sys_env_device_rev_get() into line with sys_env_device_id_get() and sys_env_model_get(). Signed-off-by: Chris Packham --- arch/arm/mach-mvebu/serdes/a38x/sys_env

[U-Boot] [PATCH v1 1/2] ARM: mvebu: a38x: move definition of PEX_CFG_DIRECT_ACCESS

PEX_CFG_DIRECT_ACCESS was defined in ddr3_hws_hw_training_def.h despite only being used in the serdes code. Move this definition to ctrl_pex.h where all the other PEX defines are. Also remove the duplicate definition of PEX_DEVICE_AND_VENDOR_ID which is already defined in ctrl_pex.h. Signed-off-by

Re: [U-Boot] [PATCH] kconfig: add CONFIG_CC_COVERAGE

Gentle ping.. 2018-03-29 9:49 GMT+02:00 Christian Gmeiner : > Make it possible to use gcc code coverage analysis. > > Signed-off-by: Christian Gmeiner > --- > .gitignore | 4 > Kconfig| 8 > Makefile | 6 ++ > 3 files changed, 18 insertions(+) > > diff --git a/.gitignore

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

On Wed, Mar 21, 2018 at 4:48 PM, Maxime Ripard wrote: > From: Philipp Tomsich > > Throughput tests have shown the sunxi_mmc driver to take over 10s to > read 10MB from a fast eMMC device due to excessive delays in polling > loops. > > This commit restructures the main polling loops to use get_tim

Re: [U-Boot] [PATCH v5 09/11] sunxi: disable direct MMC environment

On Wed, Apr 04, 2018 at 01:31:21AM +0100, Andre Przywara wrote: > Since the dawn of time for the Allwinner support in mainline U-Boot > we store the environment to the SD card and write directly at > 544KB from the beginning of the device. This leads to problems when > the U-Boot proper image grows

Re: [U-Boot] [PATCH v5 00/11] sunxi: update H3/H5/A64 EMAC DT nodes

On Wed, Apr 4, 2018 at 6:01 AM, Andre Przywara wrote: > This is the first half of the DT update series, just updating the > EMAC DT nodes, for which the bindings have diverged. > Just fixed some checkpatch warnings and rebased (without conflicts) > against v2018.05-rc1. > As before, this includes

Re: [U-Boot] [PATCH] ARM: mx6: ddr: Add write leveling correction code

On 30/03/2018 18:10, Eric Nelson wrote: > Hi Marek, > > Thanks for this update and the detailed notes. > > On 03/29/2018 06:04 PM, Marek Vasut wrote: >> When the DDR calibration is enabled, a situation may happen that it >> will fail on a few select boards out of a whole production lot. In >> par

Re: [U-Boot] [PATCH] ARM: mx6: ddr: Add write leveling correction code

On 30/03/2018 03:04, Marek Vasut wrote: > When the DDR calibration is enabled, a situation may happen that it > will fail on a few select boards out of a whole production lot. In > particular, after the first write leveling stage, the MPWLDECTRLx > registers will contain a value 0x1nn , for nn usua