On Mon, Sep 27, 2021 at 8:43 PM Stefan Agner wrote:
>
> There are devices which cause a USB stall when trying to read strings.
> Specifically Arduino Mega R3 stalls when trying to read the product
> string.
>
> The stall currently remains unhandled, and subsequent retries submit new
> transfers
Ensure the ASPEED related options are grouped together under the RAM
option when enabling support.
This also makes some minor grammar corrections and renames options so
they present cleanly in menuconfig.
There should be no functional change to the configuration or binary.
Signed-off-by: Joel
On Thu, Feb 3, 2022 at 7:09 AM Angus Ainslie wrote:
>
> If u-boot doesn't stop the core when it's finished with it then
> linux can't find it.
>
> Signed-off-by: Angus Ainslie
> ---
> drivers/usb/dwc3/core.c | 9 +
> 1 file changed, 9 insertions(+)
>
Reviewed-by: Bin Meng
On Thu, Feb 3, 2022 at 7:09 AM Angus Ainslie wrote:
>
> The kernel devicetree has definitions for port and hub nodes as subnodes
> to the USB devices. These subnodes don't contain all of the data required
> to properly configure the dwc3. Check the parent nodes if the data is not
> in the
Add a cold reset soon after processing capsule update on disk.
This is required in UEFI specification 2.9 Section 8.5.5
"Delivery of Capsules via file on Mass Storage device" as;
In all cases that a capsule is identified for processing the system is
restarted after capsule processing is
Add expected_reset optional argument to ConsoleBase::ensure_spawned(),
ConsoleBase::restart_uboot() and ConsoleSandbox::restart_uboot_with_flags()
so that it can handle a reset while the 1st boot process after main
boot logo before prompt correctly.
Signed-off-by: Masami Hiramatsu
---
Changes
Add wait_for_reboot optional argument to ConsoleBase::run_command()
so that it can handle an expected reset by command execution.
This is useful if a command will reset the sandbox while testing
such commands, e.g. run_command("reset", wait_for_reboot = True)
Signed-off-by: Masami Hiramatsu
---
Since the efi_update_capsule() represents the UpdateCapsule() runtime
service, it has to handle the capsule flags and update ESRT. However
the capsule-on-disk doesn't need to care about such things.
Thus, the capsule-on-disk should use the efi_capsule_update_firmware()
directly instead of calling
Hi,
Here is the 5th version of the reset after capsule-on-disk. This version
includes the test updates for this new behavior. I finally split the test
update patches into 3 parts. ConsoleBase::run_command() update [2/4],
ConsoleBase::ensure_spawned() update [3/4] and the test code update.
The
Enable config for setting mmc speed mode from U-Boot command line.
Signed-off-by: Aswath Govindraju
---
configs/j721e_evm_a72_defconfig| 1 +
configs/j721e_hs_evm_a72_defconfig | 1 +
2 files changed, 2 insertions(+)
diff --git a/configs/j721e_evm_a72_defconfig
Hello Tim, Patrice,
On 15.02.22 19:28, Tim Harvey wrote:
> On Tue, Feb 15, 2022 at 9:36 AM Patrice CHOTARD
> wrote:
>>
>> Hi Tim
>>
>> On 2/15/22 17:09, Tim Harvey wrote:
>>> On Tue, Feb 15, 2022 at 5:29 AM Patrice CHOTARD
>>> wrote:
Hi Tim
On 2/10/22 18:04, Tim Harvey
Hello Nikita,
On 15.02.22 19:10, Nikita Yushchenko wrote:
> Per documentation, dm_i2c_ops.probe_chip() shall return -EREMOTEIO if
> probe fails.
>
> Currently, omap_i2c_probe_chip() returns 1 instead. Fix that.
>
> Signed-off-by: Nikita Yushchenko
> ---
> drivers/i2c/omap24xx_i2c.c | 2 +-
>
Heinrich,
We (I and Ilias) are still discussing on this patch.
I don't think it appropriate to merge it (in -rc2) at this point.
-Takahiro Akashi
On Fri, Feb 11, 2022 at 09:37:50AM +0200, Ilias Apalodimas wrote:
> The previous patch is changing U-Boot's behavior wrt certificate based
> binary
Ilias,
On Tue, Feb 15, 2022 at 08:50:08AM +0200, Ilias Apalodimas wrote:
> Akashi-san,
>
> > > > > > >
> > > > > > > +# Try rejection in reverse order.
> > > > > >
> > > > > > "Reverse order" of what?
> > > > >
> > > > > Of the test right above
> > > >
> > > > Please specify the
That code is mistakenly duplicated due to copy-and-paste error.
Just remove it.
Fixes: CID 348360
Signed-off-by: AKASHI Takahiro
---
tools/mkeficapsule.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/tools/mkeficapsule.c b/tools/mkeficapsule.c
index f7590e482f10..c118335b93bd 100644
---
Hi Takahiro,
2022年2月16日(水) 10:35 AKASHI Takahiro :
>
> On Tue, Feb 15, 2022 at 06:05:50PM +0900, Masami Hiramatsu wrote:
> > Since now the capsule_on_disk will restart the u-boot sandbox right
> > after the capsule update, if CONFIG_EFI_CAPSULE_ON_DISK_EARLY=y, the
> > boot with a new capsule
On Tue, Feb 15, 2022 at 06:05:50PM +0900, Masami Hiramatsu wrote:
> Since now the capsule_on_disk will restart the u-boot sandbox right
> after the capsule update, if CONFIG_EFI_CAPSULE_ON_DISK_EARLY=y, the
> boot with a new capsule file will repeat reboot sequence. On the
> other hand, if
Build in the driver for the Aspeed GPIO controller and turn on the
`gpio` shell command.
Signed-off-by: Andrew Jeffery
---
configs/evb-ast2500_defconfig | 3 +++
configs/evb-ast2600_defconfig | 3 +++
2 files changed, 6 insertions(+)
diff --git a/configs/evb-ast2500_defconfig
The Aspeed GPIO driver supports the GPIO controllers found in the
AST2400, AST2500 and AST2600 BMC SoCs. The implementation is a cut-down
copy of the upstream Linux kernel driver, adapted for u-boot.
Signed-off-by: Andrew Jeffery
---
drivers/gpio/Kconfig | 7 +
drivers/gpio/Makefile
Populate gpio_count in the gpio subsystem for the AST2500.
Signed-off-by: Andrew Jeffery
---
arch/arm/dts/ast2500.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/dts/ast2500.dtsi b/arch/arm/dts/ast2500.dtsi
index 98359bf92425..ee66ef67042b 100644
---
Hello,
This series adds support for the GPIO controller found in Aspeed's
AST2400, AST2500 and AST2600 BMC SoCs.
By and large I've just extracted the work from Aspeed's SDK and
submitted it. However, the driver as found in the SDK was in-turn
extracted from Linux, cut down and adapted to u-boot.
Hi
2022年2月15日(火) 23:15 Heinrich Schuchardt :
>
> On 2/15/22 10:05, Masami Hiramatsu wrote:
> > Since now the capsule_on_disk will restart the u-boot sandbox right
> > after the capsule update, if CONFIG_EFI_CAPSULE_ON_DISK_EARLY=y, the
> > boot with a new capsule file will repeat reboot sequence.
Hello!
On Wednesday 22 December 2021 20:08:56 Tony Dinh wrote:
> *** With jumper inserted, serial console connected, start serial console
>
> # picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0
> Terminal ready
>
> *** Hit here to get to the prompt and execute "x 0x0E"
>
> Bootstrap 2.33>
>
Hi Matthias,
On 15.02.2022 19:19, Matthias Brugger wrote:
>
> On 15/02/2022 15:55, Matthias Brugger wrote:
>>
>> On 18/02/2022 03:44, Jaehoon Chung wrote:
>>> On 22. 2. 14. 20:25, Marek Szyprowski wrote:
The fdt_addr env have meaning only for the current runtime and it
depends
on
On Fri, Feb 11, 2022 at 5:25 AM Marek Behún wrote:
>
> From: Marek Behún
>
> In commit 3fc92a215b69 ("ddr: marvell: a38x: fix SPLIT_OUT_MIX state
> decision") I ported a cleaned up and changed version of patch
> mv_ddr: a380: fix SPLIT_OUT_MIX state decision
>
> In the port we removed checking
Hi Pali,
On Tue, Feb 15, 2022 at 11:11 AM Pali Rohár wrote:
>
> On Monday 14 February 2022 14:00:19 Tony Dinh wrote:
> > Hi Pali,
> >
> > On Mon, Feb 14, 2022 at 1:58 AM Pali Rohár wrote:
> > >
> > > On Sunday 13 February 2022 17:10:26 Tony Dinh wrote:
> > > > Hi Pali,
> > > >
> > > > Please
On 15.02.22 14:49, Jan Kiszka wrote:
> On 15.02.22 14:34, Patrice CHOTARD wrote:
>> Hi Jan
>>
>> On 2/15/22 14:00, Jan Kiszka wrote:
>>> On 15.02.22 12:56, Patrice CHOTARD wrote:
Hi Jan
On 2/14/22 16:21, Jan Kiszka wrote:
> On 04.01.22 08:42, Patrice Chotard wrote:
>> When
On 2/15/22 18:58, Angus Ainslie wrote:
On 2022-02-15 08:45, Marek Vasut wrote:
On 2/15/22 15:55, Angus Ainslie wrote:
On 2022-02-15 00:01, Marek Vasut wrote:
On 2/15/22 01:51, Angus Ainslie wrote:
On 2022-02-14 16:25, Marek Vasut wrote:
On 2/14/22 21:51, Angus Ainslie wrote:
Enable the
It is a valid setup to have no resets, e.g. TI J721E uses such setup.
Accept it without error messages.
And, error out if there is a real issue with getting resets.
Signed-off-by: Nikita Yushchenko
---
drivers/spi/cadence_qspi.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
This is a version of reset_get_bulk() that does not treat no resets
definition as an error.
Signed-off-by: Nikita Yushchenko
---
drivers/reset/reset-uclass.c | 10 ++
include/reset.h | 21 +
2 files changed, 31 insertions(+)
diff --git
Nikita Yushchenko (2):
reset: introduce reset_get_bulk_optional()
spi: cadence_qspi: use reset_get_bulk_optional()
drivers/reset/reset-uclass.c | 10 ++
drivers/spi/cadence_qspi.c | 11 ++-
include/reset.h | 21 +
3 files changed, 37
On Wednesday 02 February 2022 09:06:30 Priyanka Jain wrote:
> >-Original Message-
> >From: Tom Rini
> >Sent: Saturday, January 22, 2022 10:05 PM
> >To: Pali Rohár ; Alison Wang ;
> >Priyanka Jain ; Mingkai Hu ;
> >Rajesh Bhagat
> >Cc: Simon Glass ; Alexandru Gagniuc
> >; Yann Dirson ;
On Tue, Feb 15, 2022 at 03:27:23PM +0100, Felix Brack wrote:
> The changes from commit 0dba45864b2a ("arm: Init the debug UART")
> prevent the early debug UART from being initialized correctly.
> To fix this we not just configure the pin multiplexer but add setting up
> early clocks.
>
>
Hey all,
Here's the latest report.
- Forwarded message from scan-ad...@coverity.com -
Date: Mon, 14 Feb 2022 22:13:51 + (UTC)
From: scan-ad...@coverity.com
To: tom.r...@gmail.com
Subject: New Defects reported by Coverity Scan for Das U-Boot
Hi,
Please find the latest report on new
On Monday 14 February 2022 14:00:19 Tony Dinh wrote:
> Hi Pali,
>
> On Mon, Feb 14, 2022 at 1:58 AM Pali Rohár wrote:
> >
> > On Sunday 13 February 2022 17:10:26 Tony Dinh wrote:
> > > Hi Pali,
> > >
> > > Please see below.
> > >
> > > On Sun, Feb 13, 2022 at 4:21 PM Pali Rohár wrote:
> > > >
>
U-Boot SPL is executed by the BootROM. And BootROM expects that U-Boot SPL
code returns back to the BootROM. Reset vectors during execution of
U-Boot SPL should not be changed as BootROM does not expect it and uses its
own reset vectors.
Add ifdefs which disable overwriting reset vectors for
Signed-off-by: Pali Rohár
---
tools/kwbimage.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/kwbimage.c b/tools/kwbimage.c
index d82f04bea7c3..a3c1592b8140 100644
--- a/tools/kwbimage.c
+++ b/tools/kwbimage.c
@@ -6,6 +6,8 @@
*
* (C) Copyright 2013 Thomas Petazzoni
*
+ *
+ *
First binary executable header is extracted by '-p 1' argument.
Signed-off-by: Pali Rohár
---
tools/kwbimage.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/kwbimage.c b/tools/kwbimage.c
index e455c10dc744..d82f04bea7c3 100644
--- a/tools/kwbimage.c
+++
These two commands are currently not processed when generating v0 images.
Signed-off-by: Pali Rohár
---
tools/kwbimage.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/tools/kwbimage.c b/tools/kwbimage.c
index 8fd30516c9d4..e455c10dc744 100644
--- a/tools/kwbimage.c
+++
Extended and binary headers are optional and are part of the image header.
Fixes kwboot to determinate correct length of Dove images.
Signed-off-by: Pali Rohár
---
tools/kwbimage.h | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/tools/kwbimage.h
When pflag is set then kwbimage was invoked by dumpimage and not mkimage.
So do not show mkimage error message in this case.
Signed-off-by: Pali Rohár
---
tools/kwbimage.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/kwbimage.c b/tools/kwbimage.c
index
dumpimage is now able to successfully parse and dump content of the Dove
bootloader image.
Note that support for generating these extended parts of v0 images is not
included yet.
Signed-off-by: Pali Rohár
---
tools/kwbimage.c | 127 ++-
This patch series extends kwbimage v0 format support by providing
ability to dump content of Dove boot images (extension of v0 format).
It also fixes recognition of these images in kwboot utility (as it uses
macros and inline functions from kwbimage.h header file).
Implementation is based on
They are used by Marvell Dove 88AP510 BootROM.
After the main header is a list of optional extended headers and after that
is a list of optional binary executable headers. Between each two extended
headers is additional 0x20 byte long padding.
Original Kirkwood SoCs support only one extended
On Tue, Feb 15, 2022 at 9:36 AM Patrice CHOTARD
wrote:
>
> Hi Tim
>
> On 2/15/22 17:09, Tim Harvey wrote:
> > On Tue, Feb 15, 2022 at 5:29 AM Patrice CHOTARD
> > wrote:
> >>
> >> Hi Tim
> >>
> >> On 2/10/22 18:04, Tim Harvey wrote:
> >>> Greetings,
> >>>
> >>> I'm trying to understand how to use
Indeed fallback to generic implementation if driver's exec_op()
returns -ENOTSUPP.
Signed-off-by: Nikita Yushchenko
---
drivers/spi/spi-mem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/spi-mem.c b/drivers/spi/spi-mem.c
index 9c1ede1b61..7f9e65e870 100644
---
On 15/02/2022 15:55, Matthias Brugger wrote:
On 18/02/2022 03:44, Jaehoon Chung wrote:
On 22. 2. 14. 20:25, Marek Szyprowski wrote:
The fdt_addr env have meaning only for the current runtime and it depends
on the dtb size or firmware version. If one save the environment to disk
and the
Per documentation, dm_i2c_ops.probe_chip() shall return -EREMOTEIO if
probe fails.
Currently, omap_i2c_probe_chip() returns 1 instead. Fix that.
Signed-off-by: Nikita Yushchenko
---
drivers/i2c/omap24xx_i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Per dm_i2c_ops.probe_chip documentation, i2c_probe_chip() shall fallback
to default probe method when .probe_chip() returns -ENOSYS.
Signed-off-by: Nikita Yushchenko
---
drivers/i2c/i2c-uclass.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/i2c-uclass.c
On 2022-02-15 08:45, Marek Vasut wrote:
On 2/15/22 15:55, Angus Ainslie wrote:
On 2022-02-15 00:01, Marek Vasut wrote:
On 2/15/22 01:51, Angus Ainslie wrote:
On 2022-02-14 16:25, Marek Vasut wrote:
On 2/14/22 21:51, Angus Ainslie wrote:
Enable the clocks for spi buses 1 through 3
Hi Tim
On 2/15/22 17:09, Tim Harvey wrote:
> On Tue, Feb 15, 2022 at 5:29 AM Patrice CHOTARD
> wrote:
>>
>> Hi Tim
>>
>> On 2/10/22 18:04, Tim Harvey wrote:
>>> Greetings,
>>>
>>> I'm trying to understand how to use the U-Boot bind command to bind
>>> the usb_ether driver to the usb class to
hi Ilias,
On Tue, 15 Feb 2022 at 20:10, Ilias Apalodimas
wrote:
>
> Hi,
>
> Took me some time to go through the whole thread, but here it goes.
>
> On Tue, Feb 15, 2022 at 12:08:30PM +0530, Sughosh Ganu wrote:
> > On Tue, 15 Feb 2022 at 07:21, AKASHI Takahiro
> > wrote:
> > >
> > > Sughosh,
> >
On 15.02.22 17:50, Jan Kiszka wrote:
> On 15.02.22 13:27, Alper Nebi Yasak wrote:
>> On 14/02/2022 12:09, Jan Kiszka wrote:
>>> On 07.02.22 23:08, Alper Nebi Yasak wrote:
The binman FIT entry type shares some code with the Section entry type.
This shared code is bound to grow, since FIT
On 15.02.22 13:27, Alper Nebi Yasak wrote:
> On 14/02/2022 12:09, Jan Kiszka wrote:
>> On 07.02.22 23:08, Alper Nebi Yasak wrote:
>>> The binman FIT entry type shares some code with the Section entry type.
>>> This shared code is bound to grow, since FIT entries are conceptually a
>>> variation of
From: Niklas Cassel
Hello there,
This series improves the support for the canaan k210 SoC.
Patch 1 renames a few compatible strings so that the k210 compatible
strings are identical to the ones used in Linux.
Patch 2 add missing power bus clocks, which is needed if supplying
the u-boot device
From: Damien Le Moal
Linux kernel fpioa pinctrl driver expects the sysctl phandle and the
power bit offset of the fpioa device to be specified as a single
property "canaan,k210-sysctl-power".
Replace the "canaan,k210-sysctl" and "canaan,k210-power-offset"
properties with
From: Niklas Cassel
Using bias-pull-up would actually cause the pin to have its pull-down
enabled. Fix this.
Original Linux patch by Sean Anderson:
https://lore.kernel.org/linux-gpio/20220209182822.640905-1-sean...@gmail.com/
Fixes: 7224d5ccf8e1 ("pinctrl: Add support for Kendryte K210 FPIOA")
From: Niklas Cassel
The loop exited too early so the k210_pc_drive_strength[0] array element
was never used.
Original Linux patch by Dan Carpenter:
https://lore.kernel.org/linux-gpio/20220209180804.GA18385@kili/
Fixes: 7224d5ccf8e1 ("pinctrl: Add support for Kendryte K210 FPIOA")
From: Damien Le Moal
"kendryte" is the marketing name for the K210 RISC-V SoC produced by
Canaan Inc. Rather than "kendryte,k210", use the usual "canaan,k210"
vendor,SoC compatibility string format in the device tree files and
use the SoC name for file names.
With these changes, the device tree
From: Damien Le Moal
Linux drivers for many of the K210 peripherals depend on the power bus
clock to be specified. Add the missing clocks and their names to avoid
problems when booting Linux using u-boot DT.
Signed-off-by: Damien Le Moal
Signed-off-by: Niklas Cassel
---
From: Damien Le Moal
The Canaan Kendryte K210 SoC DW apb_ssi v4 spi controller is documented
to have a 32 word deep TX and RX FIFO, which spi_hw_init() detects.
However, when the RX FIFO is filled up to 32 entries (RXFLR = 32), an
RX FIFO overrun error occurs. Avoid this problem by force setting
From: Sean Anderson
The designware spi driver unconditionally uses polling.
The comment to spi_hw_init() also states that the function should disable
interrupts.
According to the DesignWare DW_apb_ssi Databook, value 0xff in IMR enables
all interrupts. Since we want to mask all interrupts
Check interrupt status to see if RSA engine is completed. After completion
of the task, write-clear the status to finish operation.
Add missing register base for completion.
Fixes: 89c36cca0b6 ("crypto: aspeed: Add AST2600 ACRY support")
Signed-off-by: Neal Liu
Reviewed-by: Chia-Wei Wang
---
> -Original Message-
> From: ChiaWei Wang
> Sent: Tuesday, February 15, 2022 5:58 PM
> To: Neal Liu ; Ryan Chen
> ; u-boot@lists.denx.de
> Cc: BMC-SW
> Subject: RE: [PATCH] crypto: aspeed: fix polling RSA status wrong issue
>
> > From: Neal Liu
> > Sent: Tuesday, February 15, 2022 4:55
Check interrupt status to see if RSA engine is completed. After completion
of the task, write-clear the status to finish operation.
Add missing register base for completion.
Signed-off-by: Neal Liu
---
drivers/crypto/aspeed/aspeed_acry.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On 2/15/22 15:55, Angus Ainslie wrote:
On 2022-02-15 00:01, Marek Vasut wrote:
On 2/15/22 01:51, Angus Ainslie wrote:
On 2022-02-14 16:25, Marek Vasut wrote:
On 2/14/22 21:51, Angus Ainslie wrote:
Enable the clocks for spi buses 1 through 3
Signed-off-by: Angus Ainslie
---
Changes since
On Tue, Feb 15, 2022 at 5:29 AM Patrice CHOTARD
wrote:
>
> Hi Tim
>
> On 2/10/22 18:04, Tim Harvey wrote:
> > Greetings,
> >
> > I'm trying to understand how to use the U-Boot bind command to bind
> > the usb_ether driver to the usb class to register a USB ethernet
> > gadget network device as
On 2/15/22 16:02, Sean Anderson wrote:
On 2/15/22 8:54 AM, Michal Simek wrote:
Hi,
On 2/15/22 14:27, Jorge Ramirez-Ortiz, Foundries wrote:
On 15/02/22, Michal Simek wrote:
Hi,
On 2/14/22 21:10, Ricardo Salveti wrote:
Hi Michal,
This is a bit similar to the issue raised on iMX8-based
Hi,
Am Di., 15. Feb. 2022 um 15:03 Uhr schrieb Michael Walle :
>
> Hi Heiko,
>
> > Currently the space between kernel_addr_r and the fdt_addr_r is only
> > 32MB. To have enought space to load kernel images bigger than 32MB change
> > the
> > kernel_addr_r to CONFIG_SYS_LOAD_ADDR. Also set the
On eMMC device, the erase_grp_size > 1 so the address and size for the
erase block command in env/mmc.c can be unaligned on erase group size and
some strange trace occurs and the result is not guarantee by MMC devices.
The SD-Card behavior doesn't change as erase_grp_size = 1 for SD-Card.
For
Fix the end address in the message for unaligned erase request in
mmc_berase() when start + blkcnt is aligned to erase_grp_size.
for example:
- start = 0x2000 - 26
- count = 26
- erase_grp_size = 0x400
Caution! Your devices Erase group is 0x400
The erase range would be change to
Add support of the permanent lock support in U-Boot proper
when BSEC is not managed by secure monitor (TF-A SP_MIN or OP-TEE).
This patch avoid issue with stm32key command and fuse command
on basic boot for this missing feature of U-Boot BSEC driver.
Reported-by: Johann Neuhauser
Signed-off-by:
Add the missing @dev reference in some function description.
Fixes: b66bfdf238b9 ("arm: stm32mp: bsec: migrate trace to log macro")
Signed-off-by: Patrick Delaunay
---
arch/arm/mach-stm32mp/bsec.c | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/mach-stm32mp/bsec.c
On 2/15/22 8:54 AM, Michal Simek wrote:
Hi,
On 2/15/22 14:27, Jorge Ramirez-Ortiz, Foundries wrote:
On 15/02/22, Michal Simek wrote:
Hi,
On 2/14/22 21:10, Ricardo Salveti wrote:
Hi Michal,
This is a bit similar to the issue raised on iMX8-based targets a few
days ago, which is forcing the
On 2/15/22 15:57, Sean Anderson wrote:
On 2/15/22 9:02 AM, Michal Simek wrote:
On 2/15/22 14:49, Rafał Miłecki wrote:
From: Rafał Miłecki
U-Boot uses environment variables for storing device setup data on
flash. That data usually needs to be accessed by a bootloader, kernel
and often
On 2/15/22 9:02 AM, Michal Simek wrote:
On 2/15/22 14:49, Rafał Miłecki wrote:
From: Rafał Miłecki
U-Boot uses environment variables for storing device setup data on
flash. That data usually needs to be accessed by a bootloader, kernel
and often user-space.
This binding allows describing
On 18/02/2022 03:44, Jaehoon Chung wrote:
On 22. 2. 14. 20:25, Marek Szyprowski wrote:
The fdt_addr env have meaning only for the current runtime and it depends
on the dtb size or firmware version. If one save the environment to disk
and the loads it on the latter boot, the fdt_addr might
On 2022-02-15 00:01, Marek Vasut wrote:
On 2/15/22 01:51, Angus Ainslie wrote:
On 2022-02-14 16:25, Marek Vasut wrote:
On 2/14/22 21:51, Angus Ainslie wrote:
Enable the clocks for spi buses 1 through 3
Signed-off-by: Angus Ainslie
---
Changes since v1:
added MXC_CSPI_CLK to
Hi,
Took me some time to go through the whole thread, but here it goes.
On Tue, Feb 15, 2022 at 12:08:30PM +0530, Sughosh Ganu wrote:
> On Tue, 15 Feb 2022 at 07:21, AKASHI Takahiro
> wrote:
> >
> > Sughosh,
> >
> > On Mon, Feb 14, 2022 at 11:12:22AM +0530, Sughosh Ganu wrote:
> > > hi
The changes from commit 0dba45864b2a ("arm: Init the debug UART")
prevent the early debug UART from being initialized correctly.
To fix this we not just configure the pin multiplexer but add setting up
early clocks.
Signed-off-by: Felix Brack
---
board/eets/pdu001/Makefile | 6 +-
On 2/15/22 10:05, Masami Hiramatsu wrote:
Since now the capsule_on_disk will restart the u-boot sandbox right
after the capsule update, if CONFIG_EFI_CAPSULE_ON_DISK_EARLY=y, the
boot with a new capsule file will repeat reboot sequence. On the
other hand, if CONFIG_EFI_CAPSULE_ON_DISK_EARLY=n,
Hi Heiko,
> Currently the space between kernel_addr_r and the fdt_addr_r is only
> 32MB. To have enought space to load kernel images bigger than 32MB change the
> kernel_addr_r to CONFIG_SYS_LOAD_ADDR. Also set the scriptaddr to this
> value.
Did you check and align the values with the almost
On 2/15/22 14:49, Rafał Miłecki wrote:
From: Rafał Miłecki
U-Boot uses environment variables for storing device setup data on
flash. That data usually needs to be accessed by a bootloader, kernel
and often user-space.
This binding allows describing environment data location and its format
Hi,
On 2/15/22 14:27, Jorge Ramirez-Ortiz, Foundries wrote:
On 15/02/22, Michal Simek wrote:
Hi,
On 2/14/22 21:10, Ricardo Salveti wrote:
Hi Michal,
This is a bit similar to the issue raised on iMX8-based targets a few
days ago, which is forcing the environment location based on the boot
On 2/15/22 14:51, Heinrich Schuchardt wrote:
On 2/15/22 10:09, Masami Hiramatsu wrote:
Hi Heinrich,
I and Takahiro found that the capsule update test case and test
framework didn't expect that a command can reboot the sandbox and the
sandbox can reboot while booting, which happens when my
On 2/15/22 10:09, Masami Hiramatsu wrote:
Hi Heinrich,
I and Takahiro found that the capsule update test case and test
framework didn't expect that a command can reboot the sandbox and the
sandbox can reboot while booting, which happens when my "Reset system
after CapsuleUpdate on disk"
From: Rafał Miłecki
U-Boot uses environment variables for storing device setup data on
flash. That data usually needs to be accessed by a bootloader, kernel
and often user-space.
This binding allows describing environment data location and its format
clearly. In some/many cases it should be
On 15.02.22 14:34, Patrice CHOTARD wrote:
> Hi Jan
>
> On 2/15/22 14:00, Jan Kiszka wrote:
>> On 15.02.22 12:56, Patrice CHOTARD wrote:
>>> Hi Jan
>>>
>>> On 2/14/22 16:21, Jan Kiszka wrote:
On 04.01.22 08:42, Patrice Chotard wrote:
> When OF_LIVE flag is enabled on a 64 bits platform,
Hi Jan
On 2/15/22 14:00, Jan Kiszka wrote:
> On 15.02.22 12:56, Patrice CHOTARD wrote:
>> Hi Jan
>>
>> On 2/14/22 16:21, Jan Kiszka wrote:
>>> On 04.01.22 08:42, Patrice Chotard wrote:
When OF_LIVE flag is enabled on a 64 bits platform, there is an
issue when dev_read_addr() is called
Hi Tim
On 2/10/22 18:04, Tim Harvey wrote:
> Greetings,
>
> I'm trying to understand how to use the U-Boot bind command to bind
> the usb_ether driver to the usb class to register a USB ethernet
> gadget network device as referenced in:
> commit 02291d83fdaaf ("doc: add bind/unbind command
Hi Tim
On 2/10/22 18:04, Tim Harvey wrote:
> Greetings,
>
> I'm trying to understand how to use the U-Boot bind command to bind
> the usb_ether driver to the usb class to register a USB ethernet
> gadget network device as referenced in:
> commit 02291d83fdaaf ("doc: add bind/unbind command
On 15/02/22, Michal Simek wrote:
> Hi,
>
> On 2/14/22 21:10, Ricardo Salveti wrote:
> > Hi Michal,
> >
> > This is a bit similar to the issue raised on iMX8-based targets a few
> > days ago, which is forcing the environment location based on the boot
> > mode and not allowing the user to use a
On Tue, 15 Feb 2022 14:15:17 +0100
Marek Behún wrote:
> > In _production version_ where is no debug capability and no access to
> > any memory (just ability to boot) is is probably not needed, but none of
> > A3720 board is building this kind of version (by default). And in case
> > BootROM is
On Tue, 15 Feb 2022 00:28:33 +0100
Pali Rohár wrote:
> Function build_mem_map() modifies global variable mem_map. This variable is
> used by the get_page_table_size() function which is called by function
> arm_reserve_mmu() (as aliased macro PGTABLE_SIZE). Function
> arm_reserve_mmu() is called
On Tue, 15 Feb 2022 00:28:35 +0100
Pali Rohár wrote:
> Function is named build_mem_map, not a3700_build_mem_map.
>
> Signed-off-by: Pali Rohár
Reviewed-by: Marek Behún
On Tue, 15 Feb 2022 14:04:47 +0100
Pali Rohár wrote:
> On Tuesday 15 February 2022 13:11:25 Marek Behún wrote:
> > On Tue, 15 Feb 2022 00:28:34 +0100
> > Pali Rohár wrote:
> >
> > > In function build_mem_map() prepares also mapping for CCI-400 and
> > * prepare
On Tuesday 15 February 2022 13:11:25 Marek Behún wrote:
> On Tue, 15 Feb 2022 00:28:34 +0100
> Pali Rohár wrote:
>
> > In function build_mem_map() prepares also mapping for CCI-400 and
> * prepare
> > AP BootROM address space.
> >
> > A53 AP BootROM by default starts
On 15.02.22 12:56, Patrice CHOTARD wrote:
> Hi Jan
>
> On 2/14/22 16:21, Jan Kiszka wrote:
>> On 04.01.22 08:42, Patrice Chotard wrote:
>>> When OF_LIVE flag is enabled on a 64 bits platform, there is an
>>> issue when dev_read_addr() is called and need to perform an address
>>> translation using
On Tue, Feb 15, 2022 at 11:53:41AM +0100, Felix Brack wrote:
> Hello Tom,
>
> On 14.02.22 23:45, Tom Rini wrote:
> > On Mon, Feb 14, 2022 at 05:56:52PM +0100, Felix Brack wrote:
> >> The changes from commit 0dba45864b2a ("arm: Init the debug UART")
> >> prevent the early debug UART from being
On 14/02/2022 12:09, Jan Kiszka wrote:
> On 07.02.22 23:08, Alper Nebi Yasak wrote:
>> The binman FIT entry type shares some code with the Section entry type.
>> This shared code is bound to grow, since FIT entries are conceptually a
>> variation of Section entries.
>>
>> Make FIT entry type a
1 - 100 of 149 matches
Mail list logo
