Re: [PATCH 2/2] ARM: i.MX: Add support for ZII i.MX8MQ based devices

On Fri, Jan 25, 2019 at 5:29 PM Andrey Smirnov wrote: > > Add support for the following ZII i.MX8MQ based boards: > >- ZII i.MX8MQ RMB3 >- ZII i.MX8MQ Zest > > Most of the basic peripherals are supported by this patch. More > advanced features such as PCIe, display support, etc, are planne

[PATCH 1/2] ARM: i.MX8MQ: bbu: Add MMC boot handler

Signed-off-by: Andrey Smirnov --- arch/arm/mach-imx/imx-bbu-internal.c | 5 + arch/arm/mach-imx/include/mach/bbu.h | 9 + 2 files changed, 14 insertions(+) diff --git a/arch/arm/mach-imx/imx-bbu-internal.c b/arch/arm/mach-imx/imx-bbu-internal.c index 5f85b13dc..188369fe3 100644 ---

[PATCH 2/2] ARM: i.MX: Add support for ZII i.MX8MQ based devices

Add support for the following ZII i.MX8MQ based boards: - ZII i.MX8MQ RMB3 - ZII i.MX8MQ Zest Most of the basic peripherals are supported by this patch. More advanced features such as PCIe, display support, etc, are planned to be added later. Signed-off-by: Andrey Smirnov --- arch/arm/bo

[PATCH 1/2] i2c_probe: limit slave addresses to [0x04, 0x77]

Adresses below 0x04 and above 0x77 are reserved in the i2c bus specification, so don't probe these addresses unless requested explicitly. Also do more strict boundary checking: - ensure start address is greater or equal to zero; - don't decrease stopaddr after checking it being greater or equal

[PATCH 2/2] i2c_probe: Use a quick write transfer instead of writing a zero

This matches the method implemented in i2cdetect(8) when using its -q option. With this change an rx8130 RTC is detectable using i2c_probe. This failed before because this chip acks the first byte (containing its address and the R/̅W bit) but nacks the following 0 (representing the target address

[PATCH] gen-dtb-s: annotate magic values with their meaning

This helps understand how the imd stuff works because now $(git grep IMD_TYPE_OF_COMPATIBLE) also matches the critical code location that creates the imd entry. Signed-off-by: Uwe Kleine-König --- scripts/gen-dtb-s | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/g

[PATCH 2/3] Documentation: imx8mq-evk: add instructions for HDMITX firmware

Signed-off-by: Lucas Stach --- Documentation/boards/imx/nxp-imx8mq-evk.rst | 14 -- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/Documentation/boards/imx/nxp-imx8mq-evk.rst b/Documentation/boards/imx/nxp-imx8mq-evk.rst index ba8cf01452d6..250e51743842 100644 --- a/D

[PATCH 1/3] Documentation: imx8mq-evk: point to current version of the firmware

There were some updates to the i.MX8MQ DDR training firmware, so better point to the current version. Signed-off-by: Lucas Stach --- Documentation/boards/imx/nxp-imx8mq-evk.rst | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/boards/imx/nxp-imx8mq-evk.rst

[PATCH 3/3] ARM: nxp-imx8mq-evk: include the HDMI firmware in the image

The board has a HDMI output by default, so it makes sense to include the necessary firmware for this. Signed-off-by: Lucas Stach --- arch/arm/boards/nxp-imx8mq-evk/flash-header-imx8mq-evk.imxcfg | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boards/nxp-imx8mq-evk/flash-header-imx8m

Re: [HELP] Barebox porting

Hello, friends! I'm interested if there is any internal Barebox convention about return types and values of initcall functions. What shall return my initcall if I want to stop booting and display error message? --  Yours sincerely, Seraphim Dolbilov _

Re: build barebox for imx8mqevk

Hello Sascha, Am Freitag, 11. Januar 2019, 12:13:16 CET schrieb Sascha Hauer: > You have to pass ARCH=arm as environment variable. It seems that you > pass ARCH=arm64. > > In barebox both ARM 32bit and 64bit are handled under arch/arm, > nevertheless you have to pass a suitable toolchain. Is the

Re: [HELP] Barebox porting

Hello Sascha, 23.01.2019, 13:17, "Sascha Hauer" : > How is the integrity checked? Some md5sum or something? Anyway, you're > better off doing that in C. Well, how can I call C functions from shell without implementing own shell command? --  Yours sincerely, Seraphim Dolbilov _