Re: [PATCH 07/24] imx: update is_imx6ull to include i.MX6ULZ

Hi, Am Donnerstag, 23. April 2020, 03:33:49 CEST schrieb Peng Fan: > > Subject: Re: [PATCH 07/24] imx: update is_imx6ull to include i.MX6ULZ > > > > Am Mittwoch, 22. April 2020, 15:52:18 CEST schrieb Peng Fan: > > > Update is_imx6ull helper to include i.MX6ULZ SoC. i.MX6ULZ could share > > >

Re: [PATCH 07/24] imx: update is_imx6ull to include i.MX6ULZ

Am Mittwoch, 22. April 2020, 15:52:18 CEST schrieb Peng Fan: > Update is_imx6ull helper to include i.MX6ULZ SoC. i.MX6ULZ could > share same macro, then we no need to add is_imx6ulz in various drivers. > > Signed-off-by: Peng Fan > --- > arch/arm/include/asm/mach-imx/sys_proto.h | 2 +- > 1

Re: [U-Boot] Regression in 2019.01-rc2 for eMMC boot on mxs board?

chrieb Michael Heimpold: > Hi, > > I'm currently testing latest git tree U-Boot on an I2SE Duckbill 2 device > and it seems that I've found a regression compared to v2018.11: > > Such a Duckbill device is equipped with a NXP i.MX28 CPU and boots from > eMMC. The eMMC has a typ

[U-Boot] Regression in 2019.01-rc2 for eMMC boot on mxs board?

Hi, I'm currently testing latest git tree U-Boot on an I2SE Duckbill 2 device and it seems that I've found a regression compared to v2018.11: Such a Duckbill device is equipped with a NXP i.MX28 CPU and boots from eMMC. The eMMC has a typical DOS MBR with a special boot loader partition where

[U-Boot] [PATCH] doc: imx: fix typos in mxsimage.txt

This fixes two small typos in mxsimage.txt. Signed-off-by: Michael Heimpold --- doc/imx/mkimage/mxsimage.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/imx/mkimage/mxsimage.txt b/doc/imx/mkimage/mxsimage.txt index c3975ee5e6..9159f93a97 100644 --- a/doc/imx

[U-Boot] [PATCH] doc: imx: fix typo in imximage.txt

Signed-off-by: Michael Heimpold --- doc/imx/mkimage/imximage.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/imx/mkimage/imximage.txt b/doc/imx/mkimage/imximage.txt index 803682f558..f2cf23c5da 100644 --- a/doc/imx/mkimage/imximage.txt +++ b/doc/imx/mkimage

Re: [U-Boot] [PATCH 1/3] configs: drop CMD_CACHE from mx23_olinuxino_defconfig

Am Dienstag, 30. Oktober 2018, 11:35:25 CET schrieb Marek Vasut: > On 10/29/2018 08:21 PM, Michael Heimpold wrote: > > This prevents the warning message > > "No arch specific invalidate_icache_all available!" > > during boot. > > Can you implement it ? The cac

[U-Boot] [PATCH 2/3] configs: mx23_olinuxino_defconfig: fix status led definition

gpio driver requires not only a simple integer value, we need to use the plain value of MX23_PAD_SSP1_DETECT__GPIO_2_1. Signed-off-by: Michael Heimpold Fixes: 2d8d190c8394 ("status_led: Kconfig migration") --- configs/mx23_olinuxino_defconfig | 2 +- 1 file changed, 1 insertion(+),

[U-Boot] [PATCH 3/3] configs: mx23_olinuxino_defconfig: disable bootefi command

CONFIG_CMD_BOOTEFI is enabled by Kconfig default, but rarely used on this board/platform. So let's disable it for the boards default config. This also saves around 16 KiB in the final u-boot.sb. Signed-off-by: Michael Heimpold --- configs/mx23_olinuxino_defconfig | 1 + 1 file changed, 1

[U-Boot] [PATCH 1/3] configs: drop CMD_CACHE from mx23_olinuxino_defconfig

This prevents the warning message "No arch specific invalidate_icache_all available!" during boot. Signed-off-by: Michael Heimpold --- configs/mx23_olinuxino_defconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/configs/mx23_olinuxino_defconfig b/configs/mx23_olinuxino_defco

[U-Boot] [PATCH 0/3] Small fixes for Olimex MX23 based Olinuxino boards

Testing of v2018.11-rc2 on this board uncovered three small "issues" I would like to see fixed. See individual patch descriptions for details. Michael Heimpold (3): configs: drop CMD_CACHE from mx23_olinuxino_defconfig configs: mx23_olinuxino_defconfig: fix status led definition

[U-Boot] [PATCH] binman: fix a few typos in documentation

This fixes four small typos in the README file. Signed-off-by: Michael Heimpold Cc: Simon Glass --- tools/binman/README | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tools/binman/README b/tools/binman/README index cb34171e5f..9d9d1832ee 100644 --- a/tools/binman

Re: [U-Boot] [PATCH] fix: fw_env: Prevent writing error message on special files, which don't support fsync

o == EINVAL || errno == EROFS)) { > fprintf (stderr, >"fsync failed on %s: %s\n", >DEVNAME (dev_current), strerror > (errno)); Other than this nitpick: Acked-by: Michael Heimpold <m...@heimpold.de> Regards, Michael ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] arm: mxs: No arch specific invalidate_icache_all available!

Hi Fabio, Am 03.05.2017 um 02:56 schrieb Fabio Estevam: Hi Michael, On Sat, Apr 29, 2017 at 4:21 AM, Michael Heimpold <m...@heimpold.de> wrote: we could move the implementation in arch/arm/mach-at91/arm926ejs/cache.c to a more generic place and re-use it. However, the warning i

Re: [U-Boot] arm: mxs: No arch specific invalidate_icache_all available!

Hi, Am Montag, 24. April 2017, 20:12:55 CEST schrieb Fabio Estevam: > Hi Stefan, > > On Mon, Apr 24, 2017 at 8:03 AM, Stefan Wahren wrote: > > Hi, > > > > i tried to port our Duckbill (based on NXP i.MX28 SoC) to U-Boot > > v2017.03 [1]. The startup works fine, except

[U-Boot] [PATCH] arm: mxs: Remove misleading comments

Both comments look like being copy & paste errors. Signed-off-by: Michael Heimpold <michael.heimp...@i2se.com> Cc: Peng Fan <peng@freescale.com> Cc: Stefano Babic <sba...@denx.de> --- arch/arm/cpu/arm926ejs/mxs/mxs.c | 4 ++-- 1 file changed, 2 insertions(+), 2 de

[U-Boot] [PATCH v2] arm: mxs: add support for I2SE's Duckbill boards

Signed-off-by: Michael Heimpold <m...@heimpold.de> --- Please note, that this board setup files need the function mxs_power_switch_dcdc_clocksource() as introduced in my patch "ARM: mxs: allow boards to select DC-DC switching clock source" Changes in v2: - added autoboot st

[U-Boot] [PATCH v3] ARM: mxs: allow boards to select DC-DC switching clock source

) { mxs_power_switch_dcdc_clocksource(POWER_MISC_FREQSEL_20MHZ); } Signed-off-by: Michael Heimpold <m...@heimpold.de> Cc: Marek Vasut <ma...@denx.de> Cc: Otavio Salvador <ota...@ossystems.com.br> Cc: Fabio Estevam <fabio.este...@freescale.com> --- Changes in v3: - fixe

Re: [U-Boot] [PATCH v2] arm: mxs: add support for I2SE's Duckbill boards

Hi Marek, thanks for your review. My comments inline below. Am Sunday 13 December 2015, 16:40:14 schrieb Marek Vasut: > On Sunday, December 13, 2015 at 12:09:58 PM, Michael Heimpold wrote: > > Commit message describing the board would be real nice. > Ok, I'll

Re: [U-Boot] [PATCH v2] ARM: mxs: allow boards to select DC-DC switching clock source

Hi Marek, Am Saturday 12 December 2015, 02:42:47 schrieb Marek Vasut: > On Friday, December 11, 2015 at 12:05:36 AM, Michael Heimpold wrote: > > For some board designs, it might be useful to switch the DC-DC > > clock source to something else rather the default 24 MHz, e.g. >

[U-Boot] [PATCH v2] ARM: mxs: allow boards to select DC-DC switching clock source

) { mxs_power_select_dcdc_clocksource(POWER_MISC_FREQSEL_20MHZ); } Signed-off-by: Michael Heimpold <m...@heimpold.de> Cc: Marek Vasut <ma...@denx.de> Cc: Otavio Salvador <ota...@ossystems.com.br> Cc: Fabio Estevam <fabio.este...@freescale.com> --- Changes in v2: - use

[U-Boot] [PATCH] ARM: mxs: allow boards to select DC-DC switching clock source

For some board designs, it might be useful to switch the DC-DC clock source to something else rather the default 24 MHz, e.g. for EMI reasons. For this, use something like this in your board configuration: Signed-off-by: Michael Heimpold <m...@heimpold.de> Cc: Marek Vasut <ma...@de

Re: [U-Boot] [PATCH 0/5] tools: env: simplify argument parsing

Hi Andreas, Am Tuesday 24 November 2015, 14:21:10 schrieb Andreas Fenkart: > I want to add -c config_file parameter to fw_setenv/fw_printenv, > so I can switch between old/new u-boot environment after u-boot > upgrade. for a similar use-case a patch was accepted/merged some days ago:

Re: [U-Boot] [PATCH] ARM: mxs: fix VDDD brownout setting

Hi Marek, Am Monday 16 November 2015, 12:01:36 schrieben Sie: > On Sunday, November 15, 2015 at 10:47:12 PM, Michael Heimpold wrote: > > At the moment, the desired brownout is at 1.0V. However, > > this setting cannot be realized by hardware since we have > > only 3 bits to

[U-Boot] [PATCH] ARM: mxs: fix VDDD brownout setting

as desired BO value (which is also the same as FSL bootlets use). Signed-off-by: Michael Heimpold <m...@heimpold.de> Cc: Marek Vasut <ma...@denx.de> Cc: Otavio Salvador <ota...@ossystems.com.br> Cc: Fabio Estevam <fabio.este...@freescale.com> --- arch/arm/cpu/arm926ejs/

[U-Boot] [PATCH] arm: mxs: add support for I2SE's Duckbill boards

Signed-off-by: Michael Heimpold <m...@heimpold.de> --- arch/arm/Kconfig | 8 ++ arch/arm/include/asm/mach-types.h | 13 +++ board/i2se/duckbill/Kconfig | 15 +++ board/i2se/duckbill/MAINTAINERS | 6 ++ board/i2se/duckbill/Makefile | 12 +++ board/i2se/du

[U-Boot] [PATCH] tools/env: allow config filename to be passed via command line argument

./fw_env.config fdt_file fdt_file=imx28-duckbill.dtb $ tools/env/fw_setenv -c ./fw_env.config fdt_file imx28-duckbill-spi.dtb $ tools/env/fw_printenv -c ./fw_env.config fdt_file fdt_file=imx28-duckbill-spi.dtb Signed-off-by: Michael Heimpold <m...@heimpold.de> --- tools/env/fw_env.c

[U-Boot] [PATCH] mxs: mxsboot: fix endianess for sd boot images

. Signed-off-by: Michael Heimpold <m...@heimpold.de> --- tools/mxsboot.c | 19 ++- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/tools/mxsboot.c b/tools/mxsboot.c index 185b327..8284e95 100644 --- a/tools/mxsboot.c +++ b/tools/mxsboot.c @@ -7,6 +7,7 @@

Re: [U-Boot] [PATCH] arm: mxs: fix mac address of second interface

Hi Stefano, Am Sonntag, 23. August 2015, 17:38:05 schrieb Stefano Babic: Hi Michael, On 16/08/2015 00:16, Michael Heimpold wrote: In the rare case that an overflow occurs, propagate it. Signed-off-by: Michael Heimpold m...@heimpold.de Cc: Stefano Babic sba...@denx.de Cc: Marek

Re: [U-Boot] [PATCH v4 1/4] bitops: introduce BIT() definition

Hi, Am Freitag, 21. August 2015, 19:01:56 schrieb Heiko Schocher: introduce BIT() definition, used in at91_udc gadget driver. Signed-off-by: Heiko Schocher h...@denx.de --- Changes in v4: None Changes in v3: - new in v3 Changes in v2: None include/linux/bitops.h | 2 ++ 1

Re: [U-Boot] [PATCH] arm: mxs: fix mac address of second interface

Hi Marek, Am Sonntag, 16. August 2015, 00:49:36 schrieb Marek Vasut: On Sunday, August 16, 2015 at 12:16:21 AM, Michael Heimpold wrote: In the rare case that an overflow occurs, propagate it. Hi! Signed-off-by: Michael Heimpold m...@heimpold.de Cc: Stefano Babic sba...@denx.de Cc

Re: [U-Boot] u-boot license: SPDX GPL-2.0+ deprecated?

Hi Bhupesh, Am Freitag, 14. August 2015, 08:24:27 schrieb Sharma Bhupesh: Hi Wolfgang, Others I was going through the Software Package Data Exchange (SPDX) licensing terms for GNU General Public License v2.0 or later, as u-boot licensing uses the same on the header files

[U-Boot] [PATCH] arm: mxs: fix mac address of second interface

In the rare case that an overflow occurs, propagate it. Signed-off-by: Michael Heimpold m...@heimpold.de Cc: Stefano Babic sba...@denx.de Cc: Marek Vasut ma...@denx.de CC: Fabio Estevam fabio.este...@freescale.com --- arch/arm/cpu/arm926ejs/mxs/mxs.c | 12 ++-- 1 file changed, 10

[U-Boot] [PATCH] mxs_gpio: fix the handling in gpio_direction_output()

Setting the direction and an output value should be done by 1) set the desired output value, 2) switch to output. If this is done in the inverse order, there can be a glitch on the GPIO line. This patch fixes this by using the order as described above. Signed-off-by: Michael Heimpold m

Re: [U-Boot] can u-boot tools fw_{printenv, setenv} work with eMMC HW partition?

Hi, right, i can see that and that clarifies things for me. my *original* question was whether there was a way to set up /etc/fw_env.config to refer to the eMMC partition /dev/mmcblk1boot1 *directly*, treating it as a regular block partition and bypassing all the MTD-related processing.

Re: [U-Boot] [PATCH] tools/fw_env: use fsync to ensure that data is physically stored

Hi, ... fw_setenv state=2 dd if=... of=/dev/mmcblk0... fw_setenv state=1 ... reboot Not sure what final OS environment you're running, but I would think that reboot would sync for you ? I'm using OpenWRT and reboot links to the busybox implementation. This implemenetation calls

Re: [U-Boot] [PATCH] tools/fw_env: use fsync to ensure that data is physically stored

Hi Wolfgang Denx, Closing a file descriptor does not guarantee that the data has been successfully saved to disk, as the kernel might defer the write. What is the exact problem you are trying to fix? I mean, when exactly does adding the sync play a role? I'm using fw_setenv during

[U-Boot] [PATCH] tools/fw_env: use fsync to ensure that data is physically stored

Closing a file descriptor does not guarantee that the data has been successfully saved to disk, as the kernel might defer the write. Signed-off-by: Michael Heimpold m...@heimpold.de --- tools/env/fw_env.c | 12 1 file changed, 12 insertions(+) diff --git a/tools/env/fw_env.c b

Re: [U-Boot] [PATCH] mmc: fix env in mmc with redundant compile error

/redundant/ Reviewed-by: Michael Heimpold m...@heimpold.de ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] Your message to U-Boot awaits moderator approval

Hi, Thanks for a prompt reply. I see now that the post made it to this list [1], but strangely I neither got the acknowledgement, nor the reply. I had the same issue: for my first patch I got a waiting for moderator reply and I don't see the post in my email client nor the reply at all. Now,

[U-Boot] [SOLVED] Re: Your message to U-Boot awaits moderator approval

Dear Wolfgang Denk, I had the same issue: for my first patch I got a waiting for moderator reply and I don't see the post in my email client nor the reply at all. But it did make it to the list, i. e. you can find it in the archives and in patchwork? Or was it really lost? yes, the mail

Re: [U-Boot] [PATCH v2 2/8] mxs: Fix PULLUP/NOPULL definitions

Hi Fabio, On mx23 and mx28 the pullup bits are defined as: - 0: Enable the internal pad keeper - 1: Disable the internal pad keeper Fix the definitions as they are currently the opposite. Sorry, but I think this is not correct. Please have a look at the reference manual for i.MX28 page

Re: [U-Boot] [PATCH v2 2/8] mxs: Fix PULLUP/NOPULL definitions

Hi Fabio, mx23 does not have the Set this bit to one to _enable_ the internal pullup option. Hm, in the RM for i.MX233, page 1480 and above (http://cache.freescale.com/files/dsp/doc/ref_manual/IMX23RM.pdf) I can only find definitions like Set this bit to one to _disable_ the internal pad

[U-Boot] [PATCH RESEND] env_mmc: add support for redundant environment

This patch add support for storing the environment redundant on mmc devices. Substantially it re-uses the logic from the NAND implementation, that means using an incremental counter for marking newer data. Signed-off-by: Michael Heimpold m...@heimpold.de --- board/freescale/common/sdhc_boot.c

[U-Boot] [PATCH] env_mmc: add support for redundant environment

This patch add support for storing the environment redundant on mmc devices. Substantially it re-uses the logic from the NAND implementation, that means using an incremental counter for marking newer data. Signed-off-by: Michael Heimpold m...@heimpold.de --- board/freescale/common/sdhc_boot.c