Re: Question about GPL v3 font

Hi Wolfgang, On Fri, 23 Aug 2019 at 21:51, Wolfgang Denk wrote: > > Dear Tom, > > In message <20190726170700.GQ20116@bill-the-cat> you wrote: > > > > > It was designed in 1987. A subset of Nimbus Sans L were released > > > under the GPL. Although the characters are not exactly

Re: How to debug HW startup?

Many thanks. It appears I had completely misinterpreted the meaning of  CONFIG_DEBUG_UART_CLOCK. I see now a correct output and a new warning message: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 right after "" notification. Tomorrow I'll try to understand what it means.

Re: How to debug HW startup?

On 1/11/20 4:38 PM, Mauro Condarelli wrote: > Thanks Joel, > unfortunately I already have that defined, even if I forgot to copy it. > I attach my full .config for reference as I have no idea what I'm > still missing. > > On 1/11/20 9:42 PM, Sean Anderson wrote: >>> Could You share a Linkit _defc

Re: [PATCH] env: another attempt at fixing SPL build failures

On 10/01/2020 15.34, Tom Rini wrote: > On Fri, Jan 10, 2020 at 02:28:54PM +, Rasmus Villemoes wrote: >> On 15/12/2019 23.29, Rasmus Villemoes wrote: >>> I'm also seeing the build failure that commit >>> >>> 7d4776545b env: solve compilation error in SPL >>> >> >> Yeah, I think this is a differe

Re: How to debug HW startup?

Thanks Joel, unfortunately I already have that defined, even if I forgot to copy it. I attach my full .config for reference as I have no idea what I'm still missing. On 1/11/20 9:42 PM, Sean Anderson wrote: >> Could You share a Linkit _defconfig with early serial debug enabled? >> I'm decidedly m

Re: [PATCH] travis: Switch to QEMU v4.2.0 globally

On Sat, Jan 11, 2020 at 08:07:46AM -0500, Tom Rini wrote: > Given our tests in GitLab / Azure we can use QEMU v4.2.0 for all > platforms now. > > Signed-off-by: Tom Rini Given the results of: https://travis-ci.org/trini/u-boot/builds/635667941 Applied to u-boot/master, thanks! -- Tom signa

Re: [PATCH 08/10] arm: mvebu: enable working default boot support

I've found an issue in testing with the ENV_IS_IN_X values, they need to be changed from a "select" to an "imply" to enable disabling default values and support booting from MMC and having flash in SPI (or the other way around). I have the change queued for either a second patch submission (pe

Re: How to debug HW startup?

> Could You share a Linkit _defconfig with early serial debug enabled? > I'm decidedly missing something as, even enabling > > CONFIG_DEBUG_UART=y > CONFIG_DEBUG_UART_BASE=0x1e00 > CONFIG_DEBUG_UART_CLOCK=20 > CONFIG_DEBUG_UART_SHIFT=2 > CONFIG_DEBUG_UART_ANNOUNCE=y > > I still have plenty o

[PATCH 10/10] arm: mvebu: clearfog: don't assume MMC booting

Remove MMC booting assumptions from clearfog_defconfig. Their presence in starting config files conflicts with default ENV_IS_IN selection logic based on boot source, since the "select" option can't distinguish between user-overridden and defconfig selected. Signed-off-by: Joel Johnson --- The

[PATCH 04/10] arm: mvebu: clearfog: Add SATA mode flags

The mPCIe slots on ClearFog Pro and ClearFog Base may be alternately configured for SATA usage. Signed-off-by: Joel Johnson --- board/solidrun/clearfog/Kconfig| 17 + board/solidrun/clearfog/clearfog.c | 6 ++ 2 files changed, 23 insertions(+) diff --git a/board/solidr

[PATCH 02/10] arm: mvebu: solidrun: remove hardcoded DTS MAC address

Using a consistent hardcoded MAC address from the DTS file causes issues when using multiple devices on the same network segment. Instead rely on environment configuration or random generation. Signed-off-by: Joel Johnson --- arch/arm/dts/armada-38x-solidrun-microsom.dtsi | 1 - 1 file changed,

[PATCH 06/10] arm: mvebu: clearfog: Add config for 2GB SOM

While 1GB SOM parts are much more common, provide a build config option for supporting parts with 2GB. Signed-off-by: Joel Johnson --- board/solidrun/clearfog/Kconfig| 6 ++ board/solidrun/clearfog/clearfog.c | 8 2 files changed, 14 insertions(+) diff --git a/board/solidrun/c

[PATCH 09/10] arm: mvebu: clearfog: move ENV params to Kconfig

Migrate the values for ENV_SIZE and ENV_OFFSET into board specific Kconfig defaults so they're more accessible for configuration. Signed-off-by: Joel Johnson --- board/solidrun/clearfog/Kconfig | 8 configs/clearfog_defconfig | 2 -- 2 files changed, 8 insertions(+), 2 deletions(-

[PATCH 01/10] arm: mvebu: fix SerDes table alignment

Tested on Solidrun ClearFog Base. Table alignment was: | Lane # | Speed | Type | | 0| 3 | SATA0 | | 1| 0 | SGMII1 | | 2| 3 | SATA1 | | 3| 5 | USB3 HOST1 | | 4| 5 | USB3 HOST0 | |

[PATCH 07/10] arm: mvebu: clearfog: add SPI offsets

Add reasonable default SPI offsets and ENV size when configured to boot from SPI flash. Signed-off-by: Joel Johnson --- board/solidrun/clearfog/Kconfig | 12 1 file changed, 12 insertions(+) diff --git a/board/solidrun/clearfog/Kconfig b/board/solidrun/clearfog/Kconfig index fd880

[PATCH 08/10] arm: mvebu: enable working default boot support

With the move to driver model usage, ensure that the required driver support for SPI and MMC booting is available in SPL. Tested on SolidRun ClearFog devices. Signed-off-by: Joel Johnson --- arch/arm/mach-mvebu/Kconfig | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm/ma

[PATCH 1/2] mmc: add additional quirk for APP_CMD retry

It was observed (on ClearFog Base) that sending MMC APP_CMD returned an error on the first attempt. The issue appears to be timing related since even inserting a puts() short debug entry before the execution added sufficient delay to receive success on first attempt. Follow the existing quirks pat

[PATCH 05/10] arm: mvebu: clearfog: Add option for 2.5 Gbps SFP

Signed-off-by: Joel Johnson --- board/solidrun/clearfog/Kconfig| 7 +++ board/solidrun/clearfog/clearfog.c | 4 2 files changed, 11 insertions(+) diff --git a/board/solidrun/clearfog/Kconfig b/board/solidrun/clearfog/Kconfig index 30f53508c2..53f01daf7a 100644 --- a/board/solidrun/

[PATCH] zfs: remove unused buf variable

Remove unused variable to silence compiler warning Signed-off-by: Joel Johnson --- cmd/zfs.c | 1 - 1 file changed, 1 deletion(-) diff --git a/cmd/zfs.c b/cmd/zfs.c index ed5402bb13..79dbb21e7a 100644 --- a/cmd/zfs.c +++ b/cmd/zfs.c @@ -40,7 +40,6 @@ static int do_zfs_load(cmd_tbl_t *cmdtp, in

[PATCH 03/10] arm: mvebu: clearfog: initial ClearFog Base variant

Add a unique entry for ClearFog Base variant, reflected in the board name and adjusted SerDes topology. Signed-off-by: Joel Johnson --- arch/arm/mach-mvebu/Kconfig| 2 ++ board/solidrun/clearfog/Kconfig| 10 ++ board/solidrun/clearfog/clearfog.c | 10 +- 3 files cha

[PATCH 2/2] mmc: config help typo fix

Fix typo in description of MMC_QUIRKS config option. Signed-off-by: Joel Johnson --- drivers/mmc/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mmc/Kconfig b/drivers/mmc/Kconfig index 85fd1906bd..5696ef0339 100644 --- a/drivers/mmc/Kconfig +++ b/drivers/mmc/

Re: How to debug HW startup?

Hi Stefan, I managed to find ONE of the reasons why my ROM build didn't run: I forgot to enable `CONFIG_BOARD_EARLY_INIT_F=y`. I wanted, nonetheless, be prepared for further mishaps, but I have some other problems (see below). On 1/10/20 2:33 PM, Stefan Roese wrote: > Hi Mauro, > > (added Weijie

[PATCH 0/2] configs: Khadas Edge-V/Edge-Captain: Fix a typo

From: Nick Xie Fix a typo of Khadas Edge-V/Edge-Captain configuration. Nick Xie (2): configs: Khadas Edge-V: Fix a typo configs: Khadas Edge-Captain: Fix a typo configs/khadas-edge-captain-rk3399_defconfig | 2 +- configs/khadas-edge-v-rk3399_defconfig | 2 +- 2 files changed, 2 inse

[PATCH 2/2] configs: Khadas Edge-Captain: Fix a typo

From: Nick Xie Signed-off-by: Nick Xie --- configs/khadas-edge-captain-rk3399_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configs/khadas-edge-captain-rk3399_defconfig b/configs/khadas-edge-captain-rk3399_defconfig index c408a1a..27d54db 100644 --- a/configs/kh

[PATCH 1/2] configs: Khadas Edge-V: Fix a typo

From: Nick Xie Signed-off-by: Nick Xie --- configs/khadas-edge-v-rk3399_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configs/khadas-edge-v-rk3399_defconfig b/configs/khadas-edge-v-rk3399_defconfig index e70e1ec..c0ffba6 100644 --- a/configs/khadas-edge-v-rk3399

Re: regression with sunxi: psci: avoid error address-of-packed-member

On Fri, Jan 10, 2020 at 6:51 PM Heinrich Schuchardt wrote: > On 1/10/20 4:30 PM, Nuno Gonçalves wrote: > > While this commit changed the order of clamp_set fixing it did not > > solve the problem for me. > > Do you mean that both with and without the patch your system does not start? Affirm. Even

regression with sunxi: psci: avoid error address-of-packed-member

After [1] on a Orange Pi Zero I hang on Starting kernel. While this commit changed the order of clamp_set fixing it did not solve the problem for me. It appears that the problem is simply that a memcpy to sunxi_prcm_reg.cpu_pwroff does not have the same behaviour as writing a single bit. Thanks,

[PATCH] travis: Switch to QEMU v4.2.0 globally

Given our tests in GitLab / Azure we can use QEMU v4.2.0 for all platforms now. Signed-off-by: Tom Rini --- .travis.yml | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/.travis.yml b/.travis.yml index 5da046ca7ed5..3991eb7716fb 100644 --- a/.travis.yml +++ b/.travis.yml @@

Re: [PATCHv3 1/3] mmc: meson-gx: Fix clk phase tuning for MMC

Hi Jerome, On Tue, 7 Jan 2020 at 15:31, Jerome Brunet wrote: > > > On Thu 26 Dec 2019 at 12:33, Anand Moon wrote: > > > As per mainline line kernel fix the clk tunnig phase for > > mmc, set Core=180, Tx=0, Rx=0 clk phase for mmc initialization. > > > > Signed-off-by: Anand Moon > > --- > > Chan

[PATCH 1/1] efi_selftest: enable CONFIG_CMD_POWEROFF

For automating testing we should be able to power off the test system. The implementation of EFI_RESET_SHUTDOWN requires the do_poweroff() function which is only available if CONFIG_CMD_POWEROFF=y. Enable CONFIG_CMD_POWEROFF if PSCI reset is available. Signed-off-by: Heinrich Schuchardt --- lib

[RFC PATCH] rockchip: boot_mode: find the saradc device name

adc_channel_single_shot() requires the full device name e.g. "saradc@ff10", which differs between Rockchip SoC's, but they all share the prefix "saradc"; find the ADC device with this name prefix and use its full name. Signed-off-by: Hugh Cole-Baker --- I'd noticed a "rockchip_dnl_key_pressed