[U-Boot] [PATCH v2 3/3] ax25: Switch to CONFIG_BOOTP_PREFER_SERVERIP

The ax25-ae350 target currently uses CONFIG_BOOTP_SERVERIP which means we ignore the DHCP provided TFTP ip address. This breaks every case where we do now provide a serverip environment variable. Instead, let's use the new CONFIG_BOOT_PREFER_SERVERIP option to fall back to the DHCP provided TFTP

[U-Boot] [PATCH v2 0/3] net: Sanitize DHCP variable override

While trying to boot from network on a RISC-V AX25 platform, I saw that the DHCP IP address did not get populated from the DHCP server IP address. The reason for that was simple: CONFIG_BOOTP_SERVERIP was set. I don't know the history of that option, but it seems to decrease intuitivity levels of

[U-Boot] [PATCH 3/5] serial: zynq: Initialize uart only before relocation

This issue was found when OF_LIVE was enabled that there are scrambled chars on the console like this: Chip ID:zu3eg Watchdog: Started��j� sdhci@ff16: 0, sdhci@ff17: 1 In:serial@ff01 I found a solution for this problem exactly the same as I found later in serial_msm

[U-Boot] [PATCH 4/5] serial: zynq: Check priv pointer get via dev_get_priv()

Make sure that functions are working with proper strcture. Signed-off-by: Michal Simek --- Reported by: Coverity (local) --- drivers/serial/serial_zynq.c | 27 --- 1 file changed, 24 insertions(+), 3 deletions(-) diff --git a/drivers/serial/serial_zynq.c

[U-Boot] [PATCH 2/5] serial: zynq: Write chars till output fifo is full

Change logic and put char to fifo till there is a space in output fifo. Origin logic was that output fifo needs to be empty. It means only one char was in output queue. Also remove unused ZYNQ_UART_SR_TXEMPTY macro. Signed-off-by: Michal Simek --- drivers/serial/serial_zynq.c | 4 ++-- 1 file

[U-Boot] [PATCH 5/5] serial: zynq: Make zynq_serial_setbrg static

This function is used only inside this driver that's why should be static. Signed-off-by: Michal Simek --- drivers/serial/serial_zynq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/serial/serial_zynq.c b/drivers/serial/serial_zynq.c index

[U-Boot] [PATCH 1/5] serial: zynq: Use BIT macros instead of shifts and full hex numbers

Coding style is checking to use BIT macros instead of shifts. The patch is also fixing the rest of macros which should be BITs instead of hex numbers. Signed-off-by: Michal Simek --- drivers/serial/serial_zynq.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git

[U-Boot] [PATCH 0/5] serial: zynq: Fix serial driver

Hi, this series contain some changes in this driver. 1. Coding style fixes - using BIT macro 2. Using output fifo more effectively 3. Avoid initialization after relocation again 4. Make sure that priv is valid all the time 5. Keep sparse happy Thanks, Michal Michal Simek (5): serial: zynq:

Re: [U-Boot] efi_loader: Allocate memory handle for mem dp

> When we boot using memdp (bootefi on an address without previous > load that populates the device path) then the memory device path > we pass in is not backed by any handle. > > That can result in weird effects. For example grub gets very grumpy > about this inside the efi_net module and just

Re: [U-Boot] [PATCH v3 0/3] efi_loader: ARM: add support for ARMV7_NONSEC=y

On 06/14/2018 12:41 AM, Mark Kettenis wrote: This series makes it possible to run EFI applications in non-secure mode. It allows me to run OpenBSD on the Technexion PICO-PI-IMX7 and Banana Pi boards using the PSCI implementation provided by U-Boot. The second version avoids using r3 to pass

Re: [U-Boot] [PATCH v5] x86: use EFI calling convention for efi_main on x86_64

On 06/14/2018 02:27 AM, Ivan Gorinov wrote: UEFI specifies the calling convention used in Microsoft compilers; first arguments of a function are passed in (%rcx, %rdx, %r8, %r9). All other compilers use System V ABI by default, passing first integer arguments of a function in (%rdi, %rsi, %rdx,

[U-Boot] [PATCH] net: zynq_gem: Initialize val variable in zynq_gem_miiphy_read()

phyread can timeout and val will contain random value. Initialize it to zero not to report random value in case of error. Signed-off-by: Michal Simek --- Reported by: Coverity (local) --- drivers/net/zynq_gem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [U-Boot] [UBOOT PATCH] spi: zynq_qspi: Fixed incorrect return value error

On 14.6.2018 08:46, Vipul Kumar wrote: > This patch replaced "return 0" with "return status" to fix the > incorrect return value error reported by the coverity. > > Signed-off-by: Vipul Kumar > --- > drivers/spi/zynq_qspi.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [U-Boot] [PATCH v2 01/13] x86: doc: Fix reference to EFI doc in U-Boot

Hi Heinrich, On Wed, Jun 13, 2018 at 7:06 AM, Bin Meng wrote: > Hi Heinrich, > > On Wed, Jun 13, 2018 at 12:04 AM, Heinrich Schuchardt > wrote: >> On 06/12/2018 05:36 PM, Bin Meng wrote: >>> Since commit f3b5056c4e72 ("efi_loader: split README.efi into two >>> separate documents"), the original

Re: [U-Boot] [PATCH 1/4] lib: fdtdec: Fill initial ram top with DDR start value from dt

Hi Simon, > -Original Message- > From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass > Sent: Saturday, June 09, 2018 3:29 AM > To: Michal Simek > Cc: Siva Durga Prasad Paladugu ; U-Boot Mailing List > ; Tom Rini > Subject: Re: [PATCH 1/4] lib: fdtdec: Fill initial

[U-Boot] [UBOOT PATCH] spi: zynq_qspi: Fixed incorrect return value error

This patch replaced "return 0" with "return status" to fix the incorrect return value error reported by the coverity. Signed-off-by: Vipul Kumar --- drivers/spi/zynq_qspi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/spi/zynq_qspi.c b/drivers/spi/zynq_qspi.c

[U-Boot] [PATCH] microblaze: Add new syscalls io_pgetevents and rseq

Wire up new syscalls io_pgetevents and rseq. Signed-off-by: Michal Simek --- arch/microblaze/include/asm/unistd.h | 2 +- arch/microblaze/include/uapi/asm/unistd.h | 2 ++ arch/microblaze/kernel/syscall_table.S| 2 ++ 3 files changed, 5 insertions(+), 1 deletion(-) diff --git

[U-Boot] [PATCH v2] usb: sunxi: access ahb_reset0_cfg in CCM using its offset

struct sunxi_ccm_reg doesn't have ahb_reset0_cfg on sun4i and sun5i, thus compilation fails with: drivers/usb/host/ohci-sunxi.c:96:26: error: 'struct sunxi_ccm_reg' has no member named 'ahb_reset0_cfg' Access this reg using its offset to fix this issue. Fixes commit 1ed9c1118 ("usb: sunxi:

<    1   2   3