[U-Boot] [PATCH v4 0/2] Rename ax25-ae350 defconfig

From: Rick Chen Remove cpu name from the defconfig naming. Because other cpus maybe run on AE350 platform. So only use platfrom name in defconfig naming will be better. Changes since v3: - squashed [PATCH v3 2/3] MAINTAINERS: Sync for ax25-ae350 rename into [PATCH v3 1/3] riscv:

[U-Boot] [PATCH v8 07/10] bootm: use new common function lmb_init_and_reserve

This reduces duplicate code only. Signed-off-by: Simon Goldschmidt --- Changes in v8: None Changes in v7: None Changes in v6: None Changes in v5: None Changes in v4: None Changes in v2: None common/bootm.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git

[U-Boot] [PATCH 1/2] USB: musb-new: omap2430: Prep driver for Peripheral support.

The omap2430 driver only currently supports host only. In preparation for supporting peripheral mode, this patch makes the driver support only the host by creating a ofdata_to_platdata function host/peripheral agnostic with a host helper version. Signed-off-by: Adam Ford diff --git

[U-Boot] [PATCH 2/2] USB: musb-new: omap2430: Add hooks for Peripheral support.

Borrowing from the updates to ti-musb.c, this glue layer checks to see if the MUSB controller is gadget or host. Going under the assumpution there is only one MUSB controller, this only builds either the host probe or the gadget probe. OTG would be preferred, but it doesn't appear to be working

Re: [U-Boot] [PATCH v4 0/7] Add support for the SoCs found in Microsemi switches

Am 14.12.18 um 16:16 schrieb Gregory CLEMENT: > Hello, > > For the record this the fourth version of the series adding the > support of 2 SoCs: Ocelot and Luton from Microsemi. Both of them > belongs to the same family Vcore III. > > We found them on various advanced switches product. > > The

Re: [U-Boot] [PATCH] omap3: beagle: Enable DM_MMC and BLK for u-boot only, not SPL

On Mon, Dec 17, 2018 at 01:34:53PM -0600, Adam Ford wrote: > On Mon, Dec 17, 2018 at 11:04 AM Guillaume Gardet > wrote: > > > > > > Le 21/11/2018 à 18:06, Tom Rini a écrit : > > > On Wed, Nov 21, 2018 at 04:13:20PM +0100, Guillaume GARDET wrote: > > > > > >> Also disable USB_STORAGE as it is not

[U-Boot] [PATCH v4 1/2] riscv: configs: Rename ax25-ae350 defconfig

From: Rick Chen Remove cpu name from the defconfig naming. Because other cpus maybe run on AE350 platform. So only use platfrom name in defconfig naming will be better. Also sync MAINTAINERS: Rename a25-ae350_32_defconfig as ae350_rv32_defconfig ax25-ae350_64_defconfig as ae350_rv64_defconfig

[U-Boot] [PATCH v4 2/2] doc: README.ae350: Sync for ax25-ae350 rename

From: Rick Chen Rename ax25-ae350 as ae350_rv[32|64] for 32 or 64 bit. Signed-off-by: Rick Chen Cc: Greentime Hu Reviewed-by: Bin Meng --- doc/README.ae350 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/README.ae350 b/doc/README.ae350 index fe75b80..189a6b7 100644

Re: [U-Boot] Unable to saveenv to MMC

The output I'm getting is: => ls mmc 0:0 ** Unrecognized filesystem type ** On Sun, Dec 9, 2018 at 1:43 AM wrote: > just try the ls-command i wrote in uboot-console ;) > > > Gesendet: Sonntag, 09. Dezember 2018 um 04:20 Uhr > Von: "Robin Polak" > An: fran...@public-files.de > Cc:

[U-Boot] [PATCH v3 0/3] Rename ax25-ae350 defconfig

From: Rick Chen Remove cpu name from the defconfig naming. Because other cpus maybe run on AE350 platform. So only use platfrom name in defconfig naming will be better. Changes since v2: - Fix travis failure case 6.51 Checkfor configs without MAINTAINERS entry.

[U-Boot] [PATCH v3 2/3] MAINTAINERS: Sync for ax25-ae350 rename

From: Rick Chen Rename a25-ae350_32_defconfig as ae350_rv32_defconfig ax25-ae350_64_defconfig as ae350_rv64_defconfig Signed-off-by: Rick Chen Cc: Greentime Hu --- board/AndesTech/ax25-ae350/MAINTAINERS | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

[U-Boot] [PATCH v3 1/3] riscv: configs: Rename ax25-ae350 defconfig

From: Rick Chen Remove cpu name from the defconfig naming. Because other cpus maybe run on AE350 platform. So only use platfrom name in defconfig naming will be better. Signed-off-by: Rick Chen Cc: Greentime Hu Reviewed-by: Bin Meng --- configs/a25-ae350_32_defconfig | 36

Re: [U-Boot] [PATCH v3 2/3] MAINTAINERS: Sync for ax25-ae350 rename

Hi Rick, On Tue, Dec 18, 2018 at 9:51 AM Andes wrote: > > From: Rick Chen > > Rename > a25-ae350_32_defconfig as ae350_rv32_defconfig > ax25-ae350_64_defconfig as ae350_rv64_defconfig > > Signed-off-by: Rick Chen > Cc: Greentime Hu > --- > board/AndesTech/ax25-ae350/MAINTAINERS | 5 ++--- >

Re: [U-Boot] [PATCH v3 2/3] MAINTAINERS: Sync for ax25-ae350 rename

Hi Bin Bin Meng 於 2018年12月18日 週二 上午10:50寫道： > > Hi Rick, > > On Tue, Dec 18, 2018 at 10:23 AM Rick Chen wrote: > > > > Hi Bin > > > > Bin Meng 於 2018年12月18日 週二 上午10:12寫道： > > > > > > Hi Rick, > > > > > > On Tue, Dec 18, 2018 at 9:51 AM Andes wrote: > > > > > > > > From: Rick Chen > > > > > >

[U-Boot] [PATCH v3 3/3] doc: README.ae350: Sync for ax25-ae350 rename

From: Rick Chen Rename ax25-ae350 as ae350_rv[32|64] for 32 or 64 bit. Signed-off-by: Rick Chen Cc: Greentime Hu --- doc/README.ae350 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/README.ae350 b/doc/README.ae350 index fe75b80..189a6b7 100644 --- a/doc/README.ae350

[U-Boot] i.MX8M layout, rephrased

I'm looking at U-Boot master tree and u-boot-imx repository. What we have now is quite a mess for i.MX8M. In master we have the following directories: arch/arm/mach-imx/imx8 arch/arm/mach-imx/mx8m arch/arm/include/asm/arch-imx8 arch/arm/include/asm/arch-mx8m In

Re: [U-Boot] [PATCH v3 2/3] MAINTAINERS: Sync for ax25-ae350 rename

Hi Rick, On Tue, Dec 18, 2018 at 10:23 AM Rick Chen wrote: > > Hi Bin > > Bin Meng 於 2018年12月18日 週二 上午10:12寫道： > > > > Hi Rick, > > > > On Tue, Dec 18, 2018 at 9:51 AM Andes wrote: > > > > > > From: Rick Chen > > > > > > Rename > > > a25-ae350_32_defconfig as ae350_rv32_defconfig > > >

[U-Boot] [PATCH] poplar: save environment at a different offset

From: Alex Elder Change CONFIG_ENV_OFFSET for Poplar to be 1MB further into the eMMC than before. This puts it immediately prior to the space we are reserving offset 0x20-0x40 for UEFI to save its persistent data. Define CONFIG_ENV_SIZE as a product of env_mmc_nblks and the sector

Re: [U-Boot] [PATCH 1/1] efi_loader: efi_guid_t must be 64-bit aligned

On 12/16/18 10:32 AM, Ard Biesheuvel wrote: > On Sat, 15 Dec 2018 at 22:40, Heinrich Schuchardt wrote: >> >> The UEFI Specification Version 2.7 Errata A defines: >> >> "EFI_GUID >> 128-bit buffer containing a unique identifier value. >> Unless otherwise specified, aligned on a 64-bit boundary."

[U-Boot] [PATCH 1/1] efi_loader: struct efi_configuration_table

Commit 393fccdf6c73 ("efi_loader: efi_guid_t must be 64-bit aligned") has changed the alignment of efi_guid_t. This changed the size of struct efi_configuration_table on 32-bit systems form 20 to 24 bytes. As an array of this type is pointed to by the system table this breaks compatibility with

[U-Boot] [ANN] U-Boot v2019.01-rc2 released

Hey all, So it's release day and I've put up v2019.01-rc2, I've updated git and the tarballs are also up now. Thanks again to having signed tags, between -rc1 and -rc2 we have (including but not limited to): - Various important DT syncs with Linux - Risc-V S-Mode - Important NAND/MTD fixups -

Re: [U-Boot] [PATCH v3 0/5] Add support for MIPS Creator CI20

Am 16.12.18 um 23:25 schrieb Ezequiel Garcia: > A new round, addressing feedback from Daniel. > > Daniel: do you think this is acceptable as a first submission? > > v3: > * Cleanup SoC reset logic. > * Move gpio driver to SoC specific code, to be used by SPL. >A proper dm gpio driver

Re: [U-Boot] [PATCH v3 3/3] doc: README.ae350: Sync for ax25-ae350 rename

On Tue, Dec 18, 2018 at 9:51 AM Andes wrote: > > From: Rick Chen > > Rename > ax25-ae350 as ae350_rv[32|64] for 32 or 64 bit. > > Signed-off-by: Rick Chen > Cc: Greentime Hu > --- > doc/README.ae350 | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > Reviewed-by: Bin Meng

Re: [U-Boot] [PATCH v3 2/3] MAINTAINERS: Sync for ax25-ae350 rename

Hi Bin Bin Meng 於 2018年12月18日 週二 上午10:12寫道： > > Hi Rick, > > On Tue, Dec 18, 2018 at 9:51 AM Andes wrote: > > > > From: Rick Chen > > > > Rename > > a25-ae350_32_defconfig as ae350_rv32_defconfig > > ax25-ae350_64_defconfig as ae350_rv64_defconfig > > > > Signed-off-by: Rick Chen > > Cc:

Re: [U-Boot] i.MX8M layout, rephrased

On Mon, 17 Dec 2018, Sergey Kubushyn wrote: Yet another thought -- maybe it's time to move all 64-bit ARM stuff to its own arch/arm64 as it is in Linux kernel since I don't remember when? There are quite a few SoCs out there to justify such a move... I'm looking at U-Boot master tree and

[U-Boot] [PATCH v7 8/9] lmb: remove unused extern declaration

lmb.h includes an extern declaration of "struct lmb lmb;" which is not used anywhere, so remove it. Signed-off-by: Simon Goldschmidt --- Changes in v7: None Changes in v6: None Changes in v5: None Changes in v4: None Changes in v2: - this patch is new in v2 include/lmb.h | 2 -- 1 file

[U-Boot] [PATCH v7 5/9] lib: lmb: extend lmb for checks at load time

This adds two new functions, lmb_alloc_addr and lmb_get_unreserved_size. lmb_alloc_addr behaves like lmb_alloc, but it tries to allocate a pre-specified address range. Unlike lmb_reserve, this address range must be inside one of the memory ranges that has been set up with lmb_add.

Re: [U-Boot] [PATCH v7 0/9] Fix CVE-2018-18440 and CVE-2018-18439

Am 17.12.2018 um 20:06 schrieb Simon Goldschmidt: This series fixes CVE-2018-18440 ("insufficient boundary checks in filesystem image load") by adding restrictions to the 'load' command and fixes CVE-2018-18439 ("insufficient boundary checks in network image boot") by adding restrictions to the

[U-Boot] [PATCH v8 01/10] test: add test for lib/lmb.c

Add basic tests for the lmb memory allocation code used to reserve and allocate memory during boot. Signed-off-by: Simon Goldschmidt --- Changes in v8: None Changes in v7: None Changes in v6: None Changes in v5: - this patch is new in v5 Changes in v4: None Changes in v2: None

[U-Boot] [PATCH v8 02/10] lmb: fix allocation at end of address range

The lmb code fails if base + size of RAM overflows to zero. Fix this by calculating end as 'base + size - 1' instead of 'base + size' where appropriate. Added tests to assert this is fixed. Signed-off-by: Simon Goldschmidt --- Changes in v8: None Changes in v7: None Changes in v6: None

[U-Boot] [PATCH v2] image: fix compiling without CMD_FDT

From: Simon Goldschmidt Booting an image currently sets the environment variable "fdtaddr" by calling into 'cmd/fdt.c'. As a result, linking U-Boot fails if CMD_FDT is not enabled. Fix this by adding 'if (CONFIG_IS_ENABLED(CMD_FDT))' to the two places where 'set_working_fdt_addr()' is called.

[U-Boot] [PATCH v7 0/9] Fix CVE-2018-18440 and CVE-2018-18439

This series fixes CVE-2018-18440 ("insufficient boundary checks in filesystem image load") by adding restrictions to the 'load' command and fixes CVE-2018-18439 ("insufficient boundary checks in network image boot") by adding restrictions to the tftp code. The functions from lmb.c are used to

[U-Boot] [PATCH v7 9/9] tftp: prevent overwriting reserved memory

This fixes CVE-2018-18439 ("insufficient boundary checks in network image boot") by using lmb to check for a valid range to store received blocks. Signed-off-by: Simon Goldschmidt --- Changes in v7: - fix compiling without CONFIG_LMB Changes in v6: None Changes in v5: None Changes in v4: -

[U-Boot] [PATCH v7 7/9] bootm: use new common function lmb_init_and_reserve

This reduces duplicate code only. Signed-off-by: Simon Goldschmidt --- Changes in v7: None Changes in v6: None Changes in v5: None Changes in v4: None Changes in v2: None common/bootm.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/common/bootm.c b/common/bootm.c

[U-Boot] [PATCH v7 4/9] fdt: parse "reserved-memory" for memory reservation

boot_fdt_add_mem_rsv_regions() adds reserved memory sections to an lmb struct. Currently, it only parses regions described by /memreserve/ entries. Extend this to the more commonly used scheme of the "reserved-memory" node. Signed-off-by: Simon Goldschmidt --- Changes in v7: - fix compiling

Re: [U-Boot] [PATCH] omap3: beagle: Enable DM_MMC and BLK for u-boot only, not SPL

On Mon, Dec 17, 2018 at 11:04 AM Guillaume Gardet wrote: > > > Le 21/11/2018 à 18:06, Tom Rini a écrit : > > On Wed, Nov 21, 2018 at 04:13:20PM +0100, Guillaume GARDET wrote: > > > >> Also disable USB_STORAGE as it is not ready for the switch. > >> Tested on a Beagleboard xM rev. B. > >> > >>

Re: [U-Boot] [PATCH v8 10/10] arm: bootm: fix sp detection at end of address range

On 12/17/18 1:08 PM, Simon Goldschmidt wrote: This fixes 'arch_lmb_reserve()' for ARM that tries to detect in which DRAM bank 'sp' is in. This code failed if a bank was at the end of physical address range (i.e. size + length overflowed to 0). To fix this, calculate 'bank_end' as 'size +

[U-Boot] [PATCH v8 05/10] lib: lmb: extend lmb for checks at load time

This adds two new functions, lmb_alloc_addr and lmb_get_unreserved_size. lmb_alloc_addr behaves like lmb_alloc, but it tries to allocate a pre-specified address range. Unlike lmb_reserve, this address range must be inside one of the memory ranges that has been set up with lmb_add.

[U-Boot] [PATCH v7 3/9] lib: lmb: reserving overlapping regions should fail

lmb_add_region handles overlapping regions wrong: instead of merging or rejecting to add a new reserved region that overlaps an existing one, it just adds the new region. Since internally the same function is used for lmb_alloc, change lmb_add_region to reject overlapping regions. Also, to keep

[U-Boot] [PATCH v7 1/9] test: add test for lib/lmb.c

Add basic tests for the lmb memory allocation code used to reserve and allocate memory during boot. Signed-off-by: Simon Goldschmidt --- Changes in v7: None Changes in v6: None Changes in v5: - this patch is new in v5 Changes in v4: None Changes in v2: None test/lib/Makefile | 1 +

[U-Boot] [PATCH v8 03/10] lib: lmb: reserving overlapping regions should fail

lmb_add_region handles overlapping regions wrong: instead of merging or rejecting to add a new reserved region that overlaps an existing one, it just adds the new region. Since internally the same function is used for lmb_alloc, change lmb_add_region to reject overlapping regions. Also, to keep

[U-Boot] [PATCH v8 04/10] fdt: parse "reserved-memory" for memory reservation

boot_fdt_add_mem_rsv_regions() adds reserved memory sections to an lmb struct. Currently, it only parses regions described by /memreserve/ entries. Extend this to the more commonly used scheme of the "reserved-memory" node. Signed-off-by: Simon Goldschmidt --- Changes in v8: None Changes in

[U-Boot] [PATCH v7 6/9] fs: prevent overwriting reserved memory

This fixes CVE-2018-18440 ("insufficient boundary checks in filesystem image load") by using lmb to check the load size of a file against reserved memory addresses. Signed-off-by: Simon Goldschmidt --- Changes in v7: None Changes in v6: - fixed NULL pointer access in 'fdt_blob' passed to

[U-Boot] [PATCH v7 2/9] lmb: fix allocation at end of address range

The lmb code fails if base + size of RAM overflows to zero. Fix this by calculating end as 'base + size - 1' instead of 'base + size' where appropriate. Added tests to assert this is fixed. Signed-off-by: Simon Goldschmidt --- Changes in v7: None Changes in v6: None Changes in v5: - this

[U-Boot] [PATCH v8 09/10] tftp: prevent overwriting reserved memory

This fixes CVE-2018-18439 ("insufficient boundary checks in network image boot") by using lmb to check for a valid range to store received blocks. Signed-off-by: Simon Goldschmidt --- Changes in v8: None Changes in v7: - fix compiling without CONFIG_LMB Changes in v6: None Changes in v5: None

[U-Boot] [PATCH v8 10/10] arm: bootm: fix sp detection at end of address range

This fixes 'arch_lmb_reserve()' for ARM that tries to detect in which DRAM bank 'sp' is in. This code failed if a bank was at the end of physical address range (i.e. size + length overflowed to 0). To fix this, calculate 'bank_end' as 'size + length - 1' so that such banks end at 0x,

[U-Boot] [PATCH v8 08/10] lmb: remove unused extern declaration

lmb.h includes an extern declaration of "struct lmb lmb;" which is not used anywhere, so remove it. Signed-off-by: Simon Goldschmidt --- Changes in v8: None Changes in v7: None Changes in v6: None Changes in v5: None Changes in v4: None Changes in v2: - this patch is new in v2 include/lmb.h |

[U-Boot] [PATCH v8 06/10] fs: prevent overwriting reserved memory

This fixes CVE-2018-18440 ("insufficient boundary checks in filesystem image load") by using lmb to check the load size of a file against reserved memory addresses. Signed-off-by: Simon Goldschmidt --- Changes in v8: None Changes in v7: None Changes in v6: - fixed NULL pointer access in

[U-Boot] [PATCH v2] image: fix compiling without CMD_FDT

Booting an image currently sets the environment variable "fdtaddr" by calling into 'cmd/fdt.c'. As a result, linking U-Boot fails if CMD_FDT is not enabled. Fix this by adding 'if (CONFIG_IS_ENABLED(CMD_FDT))' to the two places where 'set_working_fdt_addr()' is called. Signed-off-by: Simon

Re: [U-Boot] [PATCH] omap3: beagle: Enable DM_MMC and BLK for u-boot only, not SPL

On Mon, Dec 17, 2018 at 1:34 PM Adam Ford wrote: > > On Mon, Dec 17, 2018 at 11:04 AM Guillaume Gardet > wrote: > > > > > > Le 21/11/2018 à 18:06, Tom Rini a écrit : > > > On Wed, Nov 21, 2018 at 04:13:20PM +0100, Guillaume GARDET wrote: > > > > > >> Also disable USB_STORAGE as it is not ready

[U-Boot] [PATCH 1/5] efi_loader: bootmgr: support BootNext and BootCurrent variable behavior

See UEFI v2.7, section 3.1.2 for details of the specification. With my efishell command[1], you can try as the following: => efi boot add 1 SHELL ... => efi boot add 2 HELLO ... => efi boot order 1 2 => efi bootmgr (starting SHELL ...) => efi setvar BootNext =H0200 => efi bootmgr

[U-Boot] [PATCH 3/5] cmd: bootefi: carve out fdt parameter handling

The current way how command parameters, particularly "fdt addr," are handled makes it a bit complicated to add a subcommand-specific parameter. So just refactor the code and extract efi_handle_fdt(). This commit is a preparatory change for enhancing bootmgr sub-command. Signed-off-by: AKASHI

[U-Boot] [PATCH 4/5] cmd: bootefi: run an EFI application of a specific load option

With this patch applied, we will be able to selectively execute an EFI application by specifying a load option, say "1" for Boot0001, "2" for Boot0002 and so on. => bootefi bootmgr 1, or bootefi bootmgr - 1 Please note that Boot need not be included in "BootOrder". Signed-off-by:

[U-Boot] [PATCH 5/5] cmd: run: add "-e" option to run an EFI application

"run -e" allows for executing EFI application with a specific "Boot" variable. If no "Boot" is specified or "BootOrder" is specified, it tries to run an EFI application specified in the order of "bootOrder." Signed-off-by: AKASHI Takahiro --- cmd/bootefi.c | 2 +- cmd/nvedit.c

[U-Boot] [PATCH 0/5] efi_loader: run a specific efi application more easily

This patch is a result from re-organizing my previous patches; a combination of [1] and part of [2] so as solely to provide several ways of executing a specific efi application explicitly. * bootmanager via BootNext variable * bootefi with boot id * run -e [1]

[U-Boot] [PATCH v3 1/8] cmd: add efishell command

Currently, there is no easy way to add or modify UEFI variables. In particular, bootmgr supports BootOrder/Boot variables, it is quite hard to define them as u-boot variables because they are represented in a complicated and encoded format. The new command, efishell, helps address these

[U-Boot] [PATCH v3 5/8] cmd: efishell: add memmap command

"memmap" command prints uefi-specific memory map information. => efi memmap Type StartEnd Attributes == CONVENTIONAL 4000-7de27000 WB RUNTIME DATA

[U-Boot] [PATCH v3 4/8] cmd: efishell: add images command

"images" command prints loaded images-related information. Signed-off-by: AKASHI Takahiro --- cmd/efishell.c | 13 - 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/cmd/efishell.c b/cmd/efishell.c index ed8de9e0355d..010870df63c8 100644 --- a/cmd/efishell.c +++

[U-Boot] [PATCH v3 2/8] cmd: efishell: add devices command

"devices" command prints all the uefi variables on the system. => efishell devices Device Name /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b) /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)

[U-Boot] [PATCH v3 0/8] cmd: add efishell for efi environment

# This patch set contains only efishell-specific part of my original patch[1]. See also the other patch[2]. This patch set is a collection of patches to enhance efi user interfaces /commands. It will help improve user experience on efi boot and make it more usable *without* edk2's shell

[U-Boot] [PATCH v3 8/8] cmd: env: add "-e" option for handling UEFI variables

"env [print|set] -e" allows for handling uefi variables without knowing details about mapping to corresponding u-boot variables. Signed-off-by: AKASHI Takahiro --- cmd/nvedit.c | 61 ++-- 1 file changed, 59 insertions(+), 2 deletions(-) diff

[U-Boot] [PATCH v3 3/8] cmd: efishell: add drivers command

"drivers" command prints all the uefi drivers on the system. => efi drivers Driver Name Image Path (unknown) +(not found) guid: 18a031ab-b443-4d1a-a5c0-0c09261e9f71 Currently, no useful information can be printed. Signed-off-by: AKASHI

[U-Boot] [PATCH v3 7/8] cmd: efishell: export uefi variable helper functions

Those function will be used for integration with 'env' command so as to handle uefi variables. Signed-off-by: AKASHI Takahiro --- cmd/efishell.c| 38 ++ include/command.h | 4 2 files changed, 38 insertions(+), 4 deletions(-) diff --git

[U-Boot] [PATCH v3 6/8] cmd: efishell: add dh command

"dh" command prints all the uefi handles used in the system. => efishell dh (T.B.D.) 0: (protocol info not available) 1: (protocol info not available) 2: (protocol info not available) 3: (protocol info not available) 4: (protocol info not available) 5: (protocol info not available) 6: (protocol

Re: [U-Boot] Unable to saveenv to MMC

Hi, On Thu, 6 Dec 2018 10:12:11 -0800 Robin Polak wrote: > Hello. > > I'm having trouble persisting my environment variables to the SD Card > onto which I have FAT formatted and then written U-Boot to using the > following command: > > sudo dd if=u-boot-sunxi-with-spl.bin of=/dev/disk2

[U-Boot] [PATCH 2/5] efi_loader: bootmgr: allow for running a given load option

With an extra argument, efi_bootmgr_load() can now load an efi binary based on a "Boot" variable specified. Signed-off-by: AKASHI Takahiro --- cmd/bootefi.c| 2 +- include/efi_loader.h | 3 ++- lib/efi_loader/efi_bootmgr.c | 9 - 3 files changed, 11

Re: [U-Boot] [PATCH] am57xx_evm_defconfig: Enable YMODEM support

+Tom On 17/12/18 7:57 PM, yan-...@ti.com wrote: From: Yan Liu Enable CONFIG_SPL_YMODEM_SUPPORT to support UART boot Signed-off-by: Yan Liu Reviewed-by: Lokesh Vutla Thanks and regards, Lokesh --- configs/am57xx_evm_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [U-Boot] [PATCH v3 8/8] cmd: env: add "-e" option for handling UEFI variables

On 12/18/18 6:05 AM, AKASHI Takahiro wrote: > "env [print|set] -e" allows for handling uefi variables without > knowing details about mapping to corresponding u-boot variables. > > Signed-off-by: AKASHI Takahiro Hello Takahiro, in several patch series you are implementing multiple interactive

[U-Boot] [PATCH] efi_loader: move efi_init_obj_list() to a new efi_setup.c

The function, efi_init_obj_list(), can be shared in different pseudo efi applications, like bootefi/bootmgr as well as my efishell. Moreover, it will be utilized to extend efi initialization, for example, my "removable disk support" patch and "capsule-on-disk support" patch in the future. So with

Re: [U-Boot] [PATCH v4 1/2] riscv: configs: Rename ax25-ae350 defconfig

On Tue, Dec 18, 2018 at 11:17 AM Andes wrote: > > From: Rick Chen > > Remove cpu name from the defconfig naming. > Because other cpus maybe run on AE350 platform. > So only use platfrom name in defconfig naming > will be better. > > Also sync MAINTAINERS: > Rename > a25-ae350_32_defconfig as

Re: [U-Boot] [PATCH] omap3: beagle: Enable DM_MMC and BLK for u-boot only, not SPL

Le 21/11/2018 à 18:06, Tom Rini a écrit : On Wed, Nov 21, 2018 at 04:13:20PM +0100, Guillaume GARDET wrote: Also disable USB_STORAGE as it is not ready for the switch. Tested on a Beagleboard xM rev. B. Signed-off-by: Guillaume GARDET Cc: Tom Rini Cc: Simon Glass In the case of

Re: [U-Boot] [PATCH] tools: zynqmpimage: round up partition size

On Mon, 17 Dec 2018 14:27:38 +0100, Michal Simek wrote: > On 03. 12. 18 14:42, Alexander Graf wrote: > > On 03.12.18 14:14, Michal Simek wrote: > >> +Alex > >> > >> On 28. 11. 18 11:47, Michael Tretter wrote: > >>> The FSBL copies "Total Partition Word Length" * 4 bytes from the boot.bin, >

Re: [U-Boot] [PATCH v2 07/11] spring: Update flashmap details

On Sun, 16 Dec 2018 19:36:34 -0700 Simon Glass wrote: > Update the flashmap so that this board can be started over USB A-A. It > is slightly different from snow. > > Signed-off-by: Simon Glass > --- > > Changes in v2: None > > arch/arm/dts/exynos5250-spring.dts | 41 >

Re: [U-Boot] [PATCH v4] zynq-gem: Use appropriate cache flush/invalidate for RX and TX

> -Ursprüngliche Nachricht- > Von: Bin Meng [mailto:bmeng...@gmail.com] > Gesendet: Montag, 17. Dezember 2018 09:05 > An: Stefan Theil > Cc: U-Boot Mailing List; Michal Simek > Betreff: Re: [PATCH v4] zynq-gem: Use appropriate cache flush/invalidate for > RX and TX > > Hi Stefan, > > On

[U-Boot] [RFC PATCH v1 0/7] ARM: kirkwood: migration to DM_USB

This is my initial series to convert the kirkwood platforms to DM_USB. I've been testing on an old kirkwood eval board which patch 2 adds. I've got some problems related to DMA which I think are probably due to caching or have something to do with the Z0 rev of the CPU. I'd really appreciate

Re: [U-Boot] MIPS (mt7688): EBase change in U-Boot breaks Linux

Hi Paul. On 14.12.18 22:28, Paul Burton wrote: On Fri, Dec 14, 2018 at 07:56:59AM +0100, Stefan Roese wrote: Does this Linux patch help by any chance? https://git.linux-mips.org/cgit/linux-mti.git/commit/?h=eng-v4.20=39e4d339a4540b66e9d9a8ea0da9ee41a21473b4 I'm not sure I remember why I

Re: [U-Boot] [PATCH V2] MAINTAINERS: update NXP i.MX mail list address

On Sat, Dec 15, 2018 at 8:07 PM Peng Fan wrote: > > Update NXP i.MX mail list address > > Signed-off-by: Peng Fan > --- > > V2: Update name of the mail list > > MAINTAINERS | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > Reviewed-by: Bin Meng

[U-Boot] [RFC PATCH v1 2/7] ARM: kirkwood: add db-88f6281-bp board

This is Marvell's Kirkwood development board. It has the following features - 512M DDR2 - 2 PCI connectors - 1 x1 PCI-e interface - 1 Gigabit Ethernet Port - 2 SATA Ports - USB 2.0 Interface - SDIO - 128M NAND Flash - 16M SPI Flash It can be strapped to boot from SPI or NAND.

[U-Boot] [RFC PATCH v1 5/7] ARM: kirkwood: switch to using mvebu mbus

The mvebu mbus code already had most of the support required for kirkwood. The only difference is that unlike the other mvebu targets kirkwood doesn't have a bridge control block so the code related to managing that needs to be compiled out. Signed-off-by: Chris Packham ---

[U-Boot] [RFC PATCH v1 1/7] net: mvgbe: fallback phy-mode to GMII

Some existing device trees don't specify a phy-mode so fallback to GMII when a phy-mode is not provided. Signed-off-by: Chris Packham Reviewed-by: Stefan Roese --- This is similar to what the Linux mv643xx_eth.c network driver does to handle the same case. drivers/net/mvgbe.c | 6 ++ 1

[U-Boot] [PATCH 1/1] tools: imx8image: use correct printf escape sequence

core is of type uint64_t. So for printing we need "%"PRIu64 (not "%lu"). Without the patch a warning is issued when building on a 32bit system. Signed-off-by: Heinrich Schuchardt --- tools/imx8image.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/tools/imx8image.c

[U-Boot] [PATCH] mmc: hi6220_dw_mmc: add driver model support

As requested by driver model migration plan, it adds driver model support, i.e. CONFIG_DM_MMC, for hi6220_dw_mmc driver. Signed-off-by: Shawn Guo --- drivers/mmc/hi6220_dw_mmc.c | 83 + 1 file changed, 83 insertions(+) diff --git

Re: [U-Boot] [PATCH v2 05/11] sound: Add a driver for max98088

On Sun, 16 Dec 2018 19:36:32 -0700 Simon Glass wrote: > This chip is used by spring. Add a driver for it and update the > samsung_sound driver to pick it up. > > Signed-off-by: Simon Glass > --- > > Changes in v2: None > > drivers/sound/Kconfig | 8 + > drivers/sound/Makefile

Re: [U-Boot] [PATCH v2 06/11] spring: Update sound to use max98088 codec

On Sun, 16 Dec 2018 19:36:33 -0700 Simon Glass wrote: > Update the spring settings to use this codec, which is what it > actually shipped with. > > Signed-off-by: Simon Glass > --- > > Changes in v2: None > > arch/arm/dts/exynos5250-spring.dts | 36 > +++---

[U-Boot] [RFC PATCH v1 7/7] ARM: kirkwood: enable CONFIG_DM_USB on db-88f6281-bp

Switch to the driver model for USB on the db-88f6281-bp board. CONFIG_BLK can't be enabled yet because mvebu_mmc.c needs converting. Signed-off-by: Chris Packham --- configs/db-88f6281-bp-spi_defconfig | 1 + configs/db-88f6281-bp_defconfig | 1 + 2 files changed, 2 insertions(+) diff

[U-Boot] [RFC PATCH v1 4/7] ARM: kirkwood: remove KW_DEFADR_PCI_IO_REMAP

KW_DEFADR_PCI_IO_REMAP has the same value as KW_DEFADR_PCI_IO and is only used to set up a 1:1 mapping. Remove it and update the mapping to use KW_DEFADR_PCI_IO. Signed-off-by: Chris Packham --- arch/arm/mach-kirkwood/cpu.c | 2 +- arch/arm/mach-kirkwood/include/mach/cpu.h | 1 -

Re: [U-Boot] MIPS (mt7688): EBase change in U-Boot breaks Linux

Hi Paul, On 14.12.18 22:31, Paul Burton wrote: On Fri, Dec 14, 2018 at 07:56:59AM +0100, Stefan Roese wrote: So how to proceed? Should I enable CONFIG_CPU_MIPSR2_IRQ_VI or #define "cpu_has_veic" to 1 as Lantiq does? ...and on that point in particular, it really depends on your hardware. You

[U-Boot] [PATCH u-boot] arm: dts: s400: Fix status for eMMC and SDIO ports

Under U-boot, the WiFi SDIO Module should be disabled and the eMMC modules should be enabled, so this patch adds an s400-u-boot.dtsi include file specific for U-Boot that will be included by the build system. Signed-off-by: Neil Armstrong --- arch/arm/dts/meson-axg-s400-u-boot.dtsi | 14

Re: [U-Boot] [PATCH v4] zynq-gem: Use appropriate cache flush/invalidate for RX and TX

Hi Stefan, On Mon, Dec 17, 2018 at 3:57 PM Stefan Theil wrote: > > > -Ursprüngliche Nachricht- > > Von: Bin Meng [mailto:bmeng...@gmail.com] > > Gesendet: Montag, 17. Dezember 2018 08:52 > > An: Stefan Theil > > Cc: U-Boot Mailing List; Michal Simek > > Betreff: Re: [PATCH v4] zynq-gem:

[U-Boot] [PATCH v5] zynq-gem: Use appropriate cache flush/invalidate for RX and TX

The cache was only flushed before *transmitting* packets, but not when receiving them, leading to an issue where new packets were handed to the receive handler with old contents in cache. This only happens when a lot of packets are received without sending packages every now and then. Also

Re: [U-Boot] [PATCH v5] zynq-gem: Use appropriate cache flush/invalidate for RX and TX

On Mon, Dec 17, 2018 at 4:12 PM Stefan Theil wrote: > > The cache was only flushed before *transmitting* packets, but not > when receiving them, leading to an issue where new packets were > handed to the receive handler with old contents in cache. This > only happens when a lot of packets are

[U-Boot] [RFC PATCH v1 6/7] ARM: kirkwood: remove kw_config_adr_windows

Now that kirkwood is using the mvebu mbus this function is no longer needed. Signed-off-by: Chris Packham --- arch/arm/mach-kirkwood/cpu.c | 64 --- arch/arm/mach-kirkwood/include/mach/cpu.h | 1 - 2 files changed, 65 deletions(-) diff --git

[U-Boot] [RFC PATCH v1 3/7] ARM: kirkwood: rename KW_CPU_WIN_BASE to MVEBU_CPU_WIN_BASE

This will allow the kirkwood platforms to use more common code with the other mvebu SoCs. Signed-off-by: Chris Packham --- arch/arm/mach-kirkwood/cpu.c | 2 +- arch/arm/mach-kirkwood/include/mach/soc.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [U-Boot] [PATCH] sunxi: Allow booting from 128KB SD/eMMC offset

On Sun, Dec 16, 2018 at 02:04:58AM +, Andre Przywara wrote: > On modern Allwinner SoCs (tested: H2+, A64, H5, H6) the BootROM can > actually load the SPL also from sector 256 (128KB) of an SD card or eMMC > chip. For more details, see [1]. > In this case the boot source indicator (written at

Re: [U-Boot] [PULL] Please pull u-boot-imx: u-boot-imx-20181214

On 16/12/18 22:12, Lukasz Majewski wrote: > Dear Stefano, > >> On Fri, Dec 14, 2018 at 02:39:04PM +0100, Stefano Babic wrote: >> >>> Hi Tom, >>> >>> please pull from u-boot-imx, thanks ! >>> >>> >>> The following changes since commit >>> c49aff3e66b930aa06936afee401cf5e19377958: >>> >>> Merge

[U-Boot] [PATCH 0/3] Ethernet support for QEMU sifive_u machine

This patchset enables Cadance MACB ethernet driver for QEMU sifive_u machine. The Cadance MACB ethernet driver works fine for QEMU sifive_u machince in both M-mode and S-mode with some minor fixes. The patches are based upon latest RISC-V U-Boot tree (git://git.denx.de/u-boot-riscv.git) at commit

Re: [U-Boot] poplar: fix boot failure caused by serial driver change

On Wed, Dec 12, 2018 at 03:24:44PM +0800, Shawn Guo wrote: > Commit 4687919684e0 ("serial: Remove DM_FLAG_PRE_RELOC flag in various > drivers") essentially drops flag DM_FLAG_PRE_RELOC from serial_pl01x > driver for Poplar platform, because the platform falls into the > following strategy

Re: [U-Boot] poplar: add a co-maintainer for poplar board

On Thu, Dec 13, 2018 at 05:10:43PM +0800, Shawn Guo wrote: > Add myself as co-maintainer for poplar board, as I'm actively working > on the board. > > Signed-off-by: Shawn Guo Applied to u-boot/master, thanks! -- Tom signature.asc Description: PGP signature

Re: [U-Boot] [U-Boot, v1] tools: mtk_image: replace strncpy(d, s, sizeof(d)) with snprintf()

On Tue, Dec 11, 2018 at 04:41:43PM +0200, Andy Shevchenko wrote: > Starting from version 8 the GCC, i.e. C compiler, starts complaining about > possible '\0' terminator loss or, as in this case, garbage copy. > > In function ‘mtk_image_set_gen_header’, > inlined from ‘mtk_image_set_header’

[U-Boot] [PATCH 0/2] mmc: Fix partition table init regression

Commit d0851c893706 ("blk: Call part_init() in the post_probe() method") in the 2019.01-rc1 merge window moved the partition init call to the generic DM layer, leaving every non-DM driver behind. As the result all Allwinner boards now don't read the partition table automatically anymore: => fatls

  1   2   >