Hi Heinrich,
On Mon, 25 Oct 2021 at 12:41, Heinrich Schuchardt
wrote:
>
>
>
> On 10/25/21 19:29, Simon Glass wrote:
> > Hi Heinrich,
> >
> > On Mon, 25 Oct 2021 at 09:44, Heinrich Schuchardt
> > wrote:
> >>
> >> On 10/25/21 17:18, Simon Glass wrote:
> >>> Hi Heinrich,
> >>>
> >>> On Mon, 25 Oct
On Mon, Oct 25, 2021 at 09:18:56AM -0600, Simon Glass wrote:
> On Mon, 25 Oct 2021 at 01:34, Andy Shevchenko
> wrote:
> > On Sun, Oct 24, 2021 at 11:00 PM Simon Glass wrote:
> > > On Wed, 20 Oct 2021 at 06:37, Andy Shevchenko
> > > wrote:
> > > >
> > > > The dsdt.asl is usually combined out of
On 9/25/21 02:30, Simon Glass wrote:
It is quite complicating to run U-Boot on qemu since we have four
different builds and they must use different versions of qemu and the
UEFI binaries.
Add a script to help.
Signed-off-by: Simon Glass
This patch seems not to work:
$
On Mon, Oct 25, 2021 at 10:46:32AM -0700, Alistair Delva wrote:
> -Scott's ancient non-functioning email address
>
> Hi Tom,
>
> On Mon, Oct 25, 2021 at 6:30 AM Tom Rini wrote:
> >
> > On Wed, Oct 20, 2021 at 09:31:32PM +, Alistair Delva wrote:
> >
> > > Cap end of relocations by the binary
On 10/25/21 19:29, Simon Glass wrote:
Hi Heinrich,
On Mon, 25 Oct 2021 at 09:44, Heinrich Schuchardt
wrote:
On 10/25/21 17:18, Simon Glass wrote:
Hi Heinrich,
On Mon, 25 Oct 2021 at 02:00, Heinrich Schuchardt
wrote:
On 10/25/21 09:54, Heinrich Schuchardt wrote:
On 10/24/21 21:54,
On 10/25/21 8:46 PM, Heinrich Schuchardt wrote:
On 10/24/21 01:03, Marek Vasut wrote:
On 10/11/21 1:36 PM, Heinrich Schuchardt wrote:
Hi,
In case U-Boot starts with GD_FLG_SKIP_RELOC, the efi loader
relocation code breaks down because it assumes gd->relocaddr
points to relocated U-Boot
From: Rayagonda Kokatanur
IPROC qspi driver supports both BSPI and MSPI modes.
Signed-off-by: Rayagonda Kokatanur
Signed-off-by: Bharat Gooty
Acked-by: Rayagonda Kokatanur
Signed-off-by: Roman Bacik
---
Changes in v4:
- move iproc_qspi.c from spi to mtd/spi
- remove iproc_qspi.h
- rename
Hi Heinrich,
On Mon, 25 Oct 2021 at 13:37, Heinrich Schuchardt
wrote:
>
>
>
> On 10/25/21 21:03, Simon Glass wrote:
> > Hi Heinrich,
> >
> > On Mon, 25 Oct 2021 at 12:41, Heinrich Schuchardt
> > wrote:
> >>
> >>
> >>
> >> On 10/25/21 19:29, Simon Glass wrote:
> >>> Hi Heinrich,
> >>>
> >>> On
On 18/10/21 02:24PM, JaimeLiao wrote:
> Adding Macronix Octal flash for Octal DTR support.
>
> The octaflash series can be divided into the following types:
>
> MX25 series : Serial NOR Flash.
> MX66 series : Serial NOR Flash with stacked die.(Size larger than 1Gb)
> LM/UM series : Up to 250MHz
On 25/10/2021 17.18, Simon Glass wrote:
> Hi Rasmus,
>
> On Mon, 25 Oct 2021 at 01:06, Rasmus Villemoes
> wrote:
>> Exactly, there's really never any case where that would be sensible. But
>> I would probably go a bit further and simply restrict varnames to the
>> usual alphanumerics plus
> Gesendet: Sonntag, 24. Oktober 2021 um 21:53 Uhr
> Von: "Simon Glass"
> An: "Frank Wunderlich"
> Cc: "Philipp Tomsich" , "Kever Yang"
> , "U-Boot Mailing List"
> Betreff: Re: uboot FIT signature difference
>
> Hi Frank,
>
> On Sun, 10 Oct 2021 at 11:51, Frank Wunderlich
> wrote:
> >
> >
On Fri, Oct 15, 2021 at 05:48:56PM +0200, marek.va...@gmail.com wrote:
> From: Marek Vasut
>
> In case U-Boot starts with GD_FLG_SKIP_RELOC, the U-Boot code is
> not relocated, however the stack and heap is at the end of DRAM
> after relocation. Reserve a LMB area for the non-relocated U-Boot
>
On 10/24/21 01:03, Marek Vasut wrote:
On 10/11/21 1:36 PM, Heinrich Schuchardt wrote:
Hi,
In case U-Boot starts with GD_FLG_SKIP_RELOC, the efi loader
relocation code breaks down because it assumes gd->relocaddr
points to relocated U-Boot code, which is not the case. Add
special case for
On 10/25/21 21:03, Simon Glass wrote:
Hi Heinrich,
On Mon, 25 Oct 2021 at 12:41, Heinrich Schuchardt
wrote:
On 10/25/21 19:29, Simon Glass wrote:
Hi Heinrich,
On Mon, 25 Oct 2021 at 09:44, Heinrich Schuchardt
wrote:
On 10/25/21 17:18, Simon Glass wrote:
Hi Heinrich,
On Mon, 25
On 18/10/21 02:24PM, JaimeLiao wrote:
> Following linux kernel to check address width and 4byte flag to enable
> 4byte opcode setting.
>
> Signed-off-by: JaimeLiao
> ---
> drivers/mtd/spi/spi-nor-core.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/mtd/spi/spi-nor-core.c
On 08/10/21 06:06PM, Jagan Teki wrote:
> On Wed, Sep 15, 2021 at 2:05 PM Marek Vasut wrote:
> >
> > On 9/15/21 10:28 AM, Pratyush Yadav wrote:
> > > On 14/09/21 08:22PM, Marek Vasut wrote:
> > >> On 9/14/21 7:42 PM, Pratyush Yadav wrote:
> > >>> On 14/09/21 05:22AM, Marek Vasut wrote:
> >
On 10/26/21 12:12 AM, Tom Rini wrote:
On Tue, Sep 14, 2021 at 05:27:51AM +0200, Marek Vasut wrote:
Add dfu_alt_info option which allows specifying multiple SPI flashes
as an alt info. The syntax is as follows:
altname sf bus:cs[:speed[:mode]]
Example:
dfu_alt_info=qspi0 sf 0:0;qspi1 sf 0:1
On 10/25/21 9:53 PM, Pratyush Yadav wrote:
On 08/10/21 06:06PM, Jagan Teki wrote:
On Wed, Sep 15, 2021 at 2:05 PM Marek Vasut wrote:
On 9/15/21 10:28 AM, Pratyush Yadav wrote:
On 14/09/21 08:22PM, Marek Vasut wrote:
On 9/14/21 7:42 PM, Pratyush Yadav wrote:
On 14/09/21 05:22AM, Marek
Include dm/device_compat.h to fix compilation.
Signed-off-by: Roman Bacik
---
drivers/usb/host/xhci-brcm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/host/xhci-brcm.c b/drivers/usb/host/xhci-brcm.c
index 27c4bbfcba72..fe17924028cd 100644
--- a/drivers/usb/host/xhci-brcm.c
Hi,
On Sun, Oct 24, 2021 at 9:53 PM Simon Glass wrote:
> Hi Alex,
>
> On Wed, 6 Oct 2021 at 10:00, Alex G. wrote:
> >
> > + Simon
> >
> > On 10/6/21 10:47 AM, Angelo Dureghello wrote:
> > > Fix final error message from
> > >
> > > Verification failed for '' hash node in 'conf@1' config node
>
On Tue, Oct 19, 2021 at 04:07:21PM +0300, Ilias Apalodimas wrote:
> OF_HOSTFILE is used on sandbox configs only. Although it's pretty
> unique and not causing any confusions, we are better of having simpler
> config options for the DTB.
>
> So let's replace that with the existing OF_BOARD.
On Tue, Oct 26, 2021 at 12:18:55AM +0200, Marek Vasut wrote:
> On 10/26/21 12:12 AM, Tom Rini wrote:
> > On Tue, Sep 14, 2021 at 05:27:51AM +0200, Marek Vasut wrote:
> >
> > > Add dfu_alt_info option which allows specifying multiple SPI flashes
> > > as an alt info. The syntax is as follows:
> >
On Tue, Oct 26, 2021 at 12:18:55AM +0200, Marek Vasut wrote:
> On 10/26/21 12:12 AM, Tom Rini wrote:
> > On Tue, Sep 14, 2021 at 05:27:51AM +0200, Marek Vasut wrote:
> >
> > > Add dfu_alt_info option which allows specifying multiple SPI flashes
> > > as an alt info. The syntax is as follows:
> >
On Mon, 25 Oct 2021 14:35:20 -0700
Roman Bacik wrote:
> > - you are introducing custom mechanism for setting / getting PHY
> > parameters, via custom specific env variables, for example in the
> > set_phy_speed() and set_phy_link() functions, i.e.:
> > sprintf(name1,
The DFU_MTD Kconfig entry is in the wrong position, move it into the
correct alphabetically sorted position. No functional change.
Signed-off-by: Marek Vasut
Cc: Lukasz Majewski
Cc: Patrice Chotard
Cc: Patrick Delaunay
---
drivers/dfu/Kconfig | 14 +++---
1 file changed, 7
On Mon, Oct 25, 2021 at 6:58 AM Marek Behún wrote:
>
> NAK for this driver.
>
> - display_banner() spams the output unnecessarily, the information
> should be printed with debug()
We will make the change as requested.
>
> - you are introducing custom mechanism for setting / getting PHY
>
On Tue, Sep 14, 2021 at 05:27:51AM +0200, Marek Vasut wrote:
> Add dfu_alt_info option which allows specifying multiple SPI flashes
> as an alt info. The syntax is as follows:
>
> altname sf bus:cs[:speed[:mode]]
>
> Example:
> dfu_alt_info=qspi0 sf 0:0;qspi1 sf 0:1
>
> Signed-off-by: Marek
On Mon, Oct 25, 2021 at 3:22 PM Marek Behún wrote:
>
> On Mon, 25 Oct 2021 14:35:20 -0700
> Roman Bacik wrote:
>
> > > - you are introducing custom mechanism for setting / getting PHY
> > > parameters, via custom specific env variables, for example in the
> > > set_phy_speed() and
On 10/26/21 12:21 AM, Tom Rini wrote:
On Tue, Oct 26, 2021 at 12:18:55AM +0200, Marek Vasut wrote:
On 10/26/21 12:12 AM, Tom Rini wrote:
On Tue, Sep 14, 2021 at 05:27:51AM +0200, Marek Vasut wrote:
Add dfu_alt_info option which allows specifying multiple SPI flashes
as an alt info. The
Free() checks if its argument in NULL. There is no need for the caller to
do the same.
Signed-off-by: Heinrich Schuchardt
---
env/flash.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/env/flash.c b/env/flash.c
index ebee9069e4..473e82454d 100644
--- a/env/flash.c
+++
On 10/25/21 11:18 AM, Simon Glass wrote:
Hi Sean,
On Sun, 24 Oct 2021 at 18:13, Sean Anderson wrote:
On 10/14/21 10:19 PM, Simon Glass wrote:
Hi Peng, Sean,
On Thu, 14 Oct 2021 at 19:17, Peng Fan wrote:
Subject: Re: [PATCH] clk: introduce u-boot,ignore-clk-defaults
On 10/13/21 5:37
Hi Rasmus,
On Tue, 28 Sept 2021 at 02:57, Rasmus Villemoes
wrote:
>
> The build system already automatically looks for and includes an
> in-tree *-u-boot.dtsi when building the control .dtb. However, there
> are some things that are awkward to maintain in such an in-tree file,
> most notably the
Hi Ramon,
On Thu, 14 Oct 2021 at 12:48, Simon Glass wrote:
>
> This collects together the patches previously sent relating to PXE.
>
> Firstly, it moves the boot code out of common/ and into a new boot/
> directory. This helps to collect these related files in one place, as
> common/ is quite
On 10/25/21 9:23 PM, Sean Anderson wrote:
On 10/25/21 11:18 AM, Simon Glass wrote:
Hi Sean,
On Sun, 24 Oct 2021 at 18:13, Sean Anderson wrote:
On 10/14/21 10:19 PM, Simon Glass wrote:
Hi Peng, Sean,
On Thu, 14 Oct 2021 at 19:17, Peng Fan wrote:
Subject: Re: [PATCH] clk: introduce
Enable SPL support in Kconfig and add some related option in
rk3568_common.h
Signed-off-by: Nico Cheng
Signed-off-by: Jason Zhu
---
(no changes since v1)
arch/arm/mach-rockchip/Kconfig | 2 ++
configs/evb-rk3568_defconfig| 25 -
include/configs/rk3568_common.h |
This series adds support for the rk3568 SOC, SPL load next-stage image from
eMMC will be supported after this series of patches.
Changes in v3:
Replace configuration parameters of SGRF_SOC_CON4 with macro
definitions.
Changes in v2:
We use the rk_clrreg function instead of the writel to set
We configured the drive strength and security of EMMC in
arch_cpu_init().
Signed-off-by: Nico Cheng
---
Changes in v3:
Replace configuration parameters of SGRF_SOC_CON4 with macro
definitions.
Changes in v2:
We use the rk_clrreg function instead of the writel to set eMMC sdmmc0 to
secure.
Enable sdhci and sdmmc0 node in rk3568-u-boot.dtsi
Signed-off-by: Nico Cheng
---
(no changes since v1)
arch/arm/dts/rk3568-u-boot.dtsi | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm/dts/rk3568-u-boot.dtsi b/arch/arm/dts/rk3568-u-boot.dtsi
index
Hi Heinrich,
On Sat, 23 Oct 2021 at 05:42, Heinrich Schuchardt wrote:
>
>
>
> On 9/25/21 02:30, Simon Glass wrote:
> > For the EFI app, we must embed the devicetree in the ELF file since that
> > is the only thing that is run by UEFI. Drop the warning to avoid
> > confusion.
> >
> >
Hi Heinrich,
On Mon, 25 Oct 2021 at 13:40, Heinrich Schuchardt wrote:
>
>
>
> On 9/25/21 02:30, Simon Glass wrote:
> > It is quite complicating to run U-Boot on qemu since we have four
> > different builds and they must use different versions of qemu and the
> > UEFI binaries.
> >
> > Add a
Hi Heinrich,
On Mon, 18 Oct 2021 at 11:15, Heinrich Schuchardt wrote:
>
> On 9/25/21 2:30 AM, Simon Glass wrote:
> > Add an extern declaration so that it is possible to use this macro in
> > files other than the one that defines it.
> >
> > Signed-off-by: Simon Glass
> > Reviewed-by: Heinrich
At present U-Boot can be built as an EFI app, but it is really just for
testing, with very few features. Instead, the payload build is used for
booting on top of UEFI, where U-Boot takes over the machine immediately
and supplies its own drivers.
But the app could be made more useful.
This series
Hi Heinrich,
On Sat, 23 Oct 2021 at 06:31, Heinrich Schuchardt wrote:
>
>
>
> On 9/25/21 02:30, Simon Glass wrote:
> > At present UCLASS_EFI is used to represent an EFI filesystem among other
>
> UCLASS_EFI is for UEFI drivers that provide the driver binding protocol.
>
> Your new UCLASS seems
Hi Heinrich,
On Mon, 18 Oct 2021 at 11:15, Heinrich Schuchardt wrote:
>
> On 9/25/21 2:30 AM, Simon Glass wrote:
> > It is useful to see some basic EFI info with the command as it forms part
> > of the information about a board.
> >
> > Add a hook for this and show the table address as a start.
Hi Heinrich,
On Mon, 18 Oct 2021 at 11:00, Heinrich Schuchardt wrote:
>
> On 9/25/21 2:30 AM, Simon Glass wrote:
> > At present only the backspace key is supported in U-Boot, when running as
> > an EFI app. Add support for arrows, home and end as well, to make the CLI
> > more friendly.
> >
> >
Hi Patrick,
On Fri, 22 Oct 2021 at 11:13, Patrick DELAUNAY
wrote:
>
> Hi Simon
>
> On 10/14/21 5:09 PM, Simon Glass wrote:
> > Hi Patrick,
> >
> > On Mon, 4 Oct 2021 at 04:00, Patrick Delaunay
> > wrote:
> >> Redefine the macro CONFIG_IS_ENABLED is not allowed,
> >> so this entry can be removed
Most modern platforms use 64-bit EFI so it is useful to have a U-Boot app
that runs under that. Add a (non-functional) build for this.
Note that --whole-archive causes the gcc 9.2 linker to crash, so disable
this for now. Once this is resolved, things should work.
For now, avoid mentioning the
It is quite complicated to run U-Boot on QEMU since we have four
different builds and they must use different versions of qemu and the
UEFI binaries.
Add a script to help.
Signed-off-by: Simon Glass
---
Changes in v3:
- Fix 'complicating' typo
- s/qemu/QEMU/
Changes in v2:
- Add MAINTAINERS
For the EFI app, we must embed the devicetree in the ELF file since that
is the only thing that is run by UEFI. Drop the warning to avoid
confusion.
Signed-off-by: Simon Glass
---
(no changes since v2)
Changes in v2:
- Add new patch to drop the OF_EMBED warning for EFI
Makefile | 2 +-
1
Most EFI implementations use 64-bit but U-Boot only supports running as
a 32-bit app at present. While efi-x86_payload64 does boot from 64-bit
UEFI it immediately changes back to 32-bit before starting U-Boot.
In order to support a 64-bit U-Boot app, update the Kconfig to add an
option for 32/64
There is no need to avoid driver model for networking. Drop this.
Signed-off-by: Simon Glass
---
(no changes since v2)
Changes in v2:
- Add new patch to enable DM_ETH for the app
configs/efi-x86_app_defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/configs/efi-x86_app_defconfig
When starting the app, locate all block devices and make them available
to U-Boot. This allows listing partitions and accessing files in
filesystems.
EFI also has the concept of 'disks', meaning boot media. For now, this
is not obviously useful in U-Boot, but add code to at least locate these.
Add a block driver which handles read/write for EFI block devices. This
driver actually already exists ('efi_block') but is not really suitable
for use as a real U-Boot driver:
- The operations do not provide a udevice
- The code is designed for running as part of EFI loader, so uses
The current EFI video driver only works when running in the stub. In that
case the stub calls boot services (before jumping to U-Boot proper) and
copies the graphics info over to the efi table. This is necessary because
the stub exits boot services before jumping to U-Boot.
The app maintains
At present UCLASS_EFI is used to represent an EFI filesystem among other
things. The description of this uclass is "EFI managed devices" which is
pretty vague. The only driver that uses this uclass is in fact not a real
U-Boot driver, since its operations do not include a struct udevice.
Rather
This variable is already defined by the EFI code. Drop the duplicate
definition when building a 64-bit EFI app.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/cpu/x86_64/cpu.c | 15 +--
arch/x86/cpu/x86_64/misc.c | 16
lib/efi/efi.c |
Add a function to return this information along with a stub for the
efi_info_get() function, since calling it otherwise hangs U-Boot.
Signed-off-by: Simon Glass
---
(no changes since v1)
include/efi.h | 8 +++-
lib/efi/efi_app.c | 10 ++
2 files changed, 17 insertions(+), 1
The Exception base class is a very vague and could be confusing to the
test system. Use the more specific ValueError exception instead.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/patman/tools.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Binman needs to be able to update the contents of an ELF file after it has
been build. To support this, add a function to locate the position of a
symbol's contents within the file.
Fix the comments on bss_data.c and Symbol while we are here.
Signed-off-by: Simon Glass
---
(no changes since
WIth EFI we must embed the devicetree in an ELF image so that it is loaded
as part of the executable file. We want it to include the binman
definition in there also, which in some cases cannot be created until the
ELF (u-boot) is built. Add an option to binman to support writing the
updated dtb to
At present any error from the 'make' command is silently swallowed by the
test system. Fix this by showing it when detected.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/binman/elf_test.py | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git
Typically the bloblist is positioned at a fixed address in memory until
relocation. This is convenient when it is set up in SPL or before
relocation.
But for EFI we want to set it up only when U-Boot proper is running. Add
a way to allocate it using malloc() and update the documentation to cover
At present this is disabled, but it should work so long as the kernel does
not need EFI services. Enable it and add a note about remaining work.
Signed-off-by: Simon Glass
---
(no changes since v2)
Changes in v2:
- Update documentation
arch/x86/lib/bootm.c | 11 +++
At present only the backspace key is supported in U-Boot, when running as
an EFI app. Add support for arrows, home and end as well, to make the CLI
more friendly.
Signed-off-by: Simon Glass
---
(no changes since v1)
drivers/serial/serial_efi.c | 11 +--
1 file changed, 9
At present testThreadTimeout() assumes that the expected timeout happens
first when building the section, but it can just as easily happen at the
top-level image. Update the test to cope with both.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/binman/ftest.py | 3 +--
1 file
The comment for this function is missing an argument and the return value.
Fix it.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/binman/ftest.py | 5 +
1 file changed, 5 insertions(+)
diff --git a/tools/binman/ftest.py b/tools/binman/ftest.py
index 8199a4fc7e0..39a4b94cd0b
At present each of these has its own static variable and helper functions.
Move them into a shared file.
Signed-off-by: Simon Glass
---
(no changes since v1)
include/efi.h | 21 +
lib/efi/efi.c | 29 +
lib/efi/efi_app.c | 21
This structure is uncommented. Fix it.
Signed-off-by: Simon Glass
---
Changes in v3:
- Drop comments that confuse sphinx
- Move device_path path change to its own patch
include/efi.h | 23 +++
1 file changed, 23 insertions(+)
diff --git a/include/efi.h b/include/efi.h
Comment some functions that need more information.
Signed-off-by: Simon Glass
---
(no changes since v1)
lib/efi/efi_stub.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/lib/efi/efi_stub.c b/lib/efi/efi_stub.c
index b3393e47fae..156cbf0b928 100644
---
If the 'bootm' command is not enabled then this code is not available and
this causes a link error. Fix it.
Note that for the EFI app, there is no indication of missing code. It just
hangs!
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/lib/zimage.c | 13 -
1 file
At present only 4KB of spare space is left in the DTB when building the
EFI app. Increase this to 32KB so there is plenty of space to insert the
binman definition. This cannot be expanded later (as with OF_SEPARATE)
because the ELF image has already been built.
Signed-off-by: Simon Glass
---
This is not used anywhere drop it.
Signed-off-by: Simon Glass
---
Changes in v3:
- Move device_path path change to its own patch
include/efi.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/efi.h b/include/efi.h
index 908c5dc6ebd..77e599c256e 100644
--- a/include/efi.h
+++
This should return false when the EFI app is running, since UEFI has done
the required low-level init. Fix it.
Signed-off-by: Simon Glass
---
(no changes since v1)
include/init.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/init.h b/include/init.h
index
At present this code is inline in the app and stub. But they do the same
thing. The difference is that the stub does it immediately and the app
doesn't want to do it until the end (when it boots a kernel) or not at
all, if returning to UEFI.
Move it into a function so it can be called as needed.
At present this function requires a pointer to struct efi_entry_memmap
but the only field used in there is the desc_size. We want to be able
to use it from the app, so update it to use desc_size directly.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/cpu/efi/payload.c | 8
The stub checks for failure with efi_init(). Add this for the app as well.
It is unlikely that anything can be done, but we may as well stop.
Signed-off-by: Simon Glass
---
(no changes since v1)
lib/efi/efi_app.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
At present the 'efi' command only works in the EFI payload. Update it to
work in the app too, so the memory map can be examined.
Signed-off-by: Simon Glass
---
(no changes since v2)
Changes in v2:
- Add new patch to support the efi command in the app
cmd/Makefile | 2 +-
cmd/efi.c
Add info about how to select vidconsole or serial.
Also set up a demo boot command.
Signed-off-by: Simon Glass
---
(no changes since v2)
Changes in v2:
- Add a better boot command too
include/configs/efi-x86_app.h | 25 +
1 file changed, 25 insertions(+)
diff --git
Show the revision of this table this is can be important.
Alo update the 'efi table' entry to show the actual address of the EFI
table rather than our table that points to it. This saves a step and the
intermediate table has nothing else in it.
Signed-off-by: Simon Glass
---
Changes in v3:
-
Add a message here so that both paths of memory allocation are reported.
Signed-off-by: Simon Glass
---
(no changes since v2)
Changes in v2:
- Use log_info() instead of printf()
lib/efi/efi_app.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/efi/efi_app.c
This provides access to EFI tables after U-Boot has exited boot services.
It is not needed in the app since boot services remain alive and we can
just call them whenever needed.
Add a comment to explain this.
Signed-off-by: Simon Glass
---
(no changes since v2)
Changes in v2:
- Fix 'as' typo
On 22.10.21 12:37, Pali Rohár wrote:
kwbimage v1 has also nandpagesize field. So set it to zero for both image
versions when image is not signed.
Signed-off-by: Pali Rohár
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
tools/kwboot.c | 13 ++---
1 file changed, 6 insertions(+),
On 22.10.21 12:37, Pali Rohár wrote:
The NAND_PAGE_SIZE command is already supported by mkimage for v0 images,
but not for v1 images.
A38x and A39x BootROM supports reading NAND flash page size from v1 image
in the same way as Kirkwood BootROM from v0 image. It it documented in A38x
and A39x
On 22.10.21 12:37, Pali Rohár wrote:
At this offset is stored nand page size.
Signed-off-by: Pali Rohár
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
arch/arm/mach-mvebu/spl.c | 2 +-
cmd/mvebu/bubt.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
On 22.10.21 12:41, Pali Rohár wrote:
kwbimage v1 is used on more SoCs.
Signed-off-by: Pali Rohár
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
arch/arm/mach-mvebu/spl.c | 2 +-
cmd/mvebu/bubt.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
On 23.10.21 13:14, Heinrich Schuchardt wrote:
Support for PPC4XX processors has been removed. So we should not mention it
in the documentation.
Signed-off-by: Heinrich Schuchardt
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
doc/README.bedbug | 22 --
1 file
On 25.10.21 08:56, Thomas Huth wrote:
Support for the PPC74xx processors has been removed in commit
d928664f41 ("powerpc: 74xx_7xx: remove 74xx_7xx cpu support")
more than 6 years ago already. So the corresponding README file
can now be removed, too.
Signed-off-by: Thomas Huth
Reviewed-by:
On 25.10.21 15:12, Marek Behún wrote:
From: Pali Rohár
Explicitly zero out the rfds fd_set with FD_ZERO() before using it.
Signed-off-by: Pali Rohár
Reviewed-by: Marek Behún
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
tools/kwboot.c | 1 +
1 file changed, 1 insertion(+)
diff
On 25.10.21 15:12, Marek Behún wrote:
From: Pali Rohár
Explicitly disable 2 stop bits by clearing CSTOPB flag, disable modem
control flow by clearing CRTSCTS flag and do not send hangup after closing
device by clearing HUPCL flag.
Signed-off-by: Pali Rohár
Reviewed-by: Marek Behún
On 25.10.21 15:12, Marek Behún wrote:
From: Pali Rohár
Data part of the image contains 4-byte checksum. Validate it when
processing the image.
Signed-off-by: Pali Rohár
[ refactored ]
Signed-off-by: Marek Behún
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
tools/kwboot.c | 34
On 25.10.21 15:12, Marek Behún wrote:
From: Pali Rohár
SPI image header and data parts do not have to be aligned to 128 byte
xmodem block size. So reserve additional memory for aligning header part
and additional memory for aligning data part.
Signed-off-by: Pali Rohár
Reviewed-by: Marek
On 25.10.21 15:12, Marek Behún wrote:
From: Pali Rohár
Some vendor U-Boot kwbimage binaries (e.g. those for A375) have load
address set to zero. Therefore it is not possible to inject code which
changes baudrate back to 115200 Bd before the data part.
So instead inject it after the data part
On 25.10.21 15:12, Marek Behún wrote:
From: Pali Rohár
If data part of image is modified, update 4-byte data checksum.
It looks like A385 BootROM does not verify this checksum for image
loaded via UART, but we do not know if other BootROMs are also ignoring
it. It is always better to provide
On 25.10.21 15:13, Marek Behún wrote:
From: Pali Rohár
Expression (hdrsz % KWBOOT_XM_BLKSZ) is non-zero therefore expression
(KWBOOT_XM_BLKSZ - hdrsz % KWBOOT_XM_BLKSZ) is always less than value
KWBOOT_XM_BLKSZ. So there is no need to add another modulo. Also rename
variable `offset` to `grow`
On 25.10.21 15:12, Marek Behún wrote:
From: Pali Rohár
For kwbimage v1, tell BootROM to send BootROM messages to UART port number
0 (used also for UART booting) with default baudrate (which should be
115200) and do not touch UART MPP configuration.
Signed-off-by: Pali Rohár
Reviewed-by:
On 25.10.21 15:12, Marek Behún wrote:
From: Pali Rohár
It is hard to debug why kwboot is failing when the last message is
'Finishing transfer' and no additional output. So show verbose message when
kwboot finished transfer and is waiting for baudrate change magic sequence.
Signed-off-by: Pali
On 25.10.21 15:13, Marek Behún wrote:
From: Pali Rohár
Size of the header stored in kwbimage may be larger than real used size in
the kwbimage header. If there is unused space in kwbimage header then use
it for growing it. So update code to calculate used space of kwbimage
header.
On 25.10.21 15:13, Marek Behún wrote:
From: Pali Rohár
This ensures that kwboot_img_grow_hdr() function still sees valid kwbimage
header.
Signed-off-by: Pali Rohár
Reviewed-by: Marek Behún
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
tools/kwboot.c | 9 ++---
1 file changed, 6
On 25.10.21 15:13, Marek Behún wrote:
From: Pali Rohár
This patch does not change behavior of the code, just allows to implement
new changes more easily.
Signed-off-by: Pali Rohár
Reviewed-by: Marek Behún
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
tools/kwboot.c | 8
1
On 25.10.21 15:13, Marek Behún wrote:
From: Pali Rohár
Currently when kwboot receive some garbage reply which does not understand,
it waits 1s before it tries to resend packet again.
The most common error on UART is that receiver sees some bit flipped which
results in invalid reply.
This
101 - 200 of 228 matches
Mail list logo