> -Original Message-
> From: Marek Vasut
> Sent: Friday, June 5, 2020 8:52 PM
> To: Tan, Ley Foon ; u-boot@lists.denx.de
> Cc: Ley Foon Tan ; See, Chin Liang
> ; Simon Goldschmidt
> ; Ang, Chee Hong
>
> Subject: Re: [PATCH] arm: dts: socfpga: cyclone5: Update i2c-scl-falling-
> time-ns
On 6/7/20 9:26 PM, Sean Anderson wrote:
> dm_gpio_ops.get_value can be called when the gpio is either input or
> output. The current dw code always returns the input value, which is
> invalid if the direction is set to out.
>
> Signed-off-by: Sean Anderson
> ---
> This patch was previously submit
In this commit, efi_signature_verify(with_sigdb) will be re-implemented
using pcks7_verify_one() in order to support certificates chain, where
the signer's certificate will be signed by an intermediate CA (certificate
authority) and the latter's certificate will also be signed by another CA
and so
In this test case, an image may have a signature with additional
intermediate certificates. A chain of trust will be followed and all
the certificates in the middle of chain must be verified before loading.
Signed-off-by: AKASHI Takahiro
---
test/py/tests/test_efi_secboot/conftest.py| 138 ++
The function, pkcs7_verify_one(), will be utilized to rework signature
verification logic aiming to support intermediate certificates in
"chain of trust."
To do that, its function interface is expanded, adding an extra argument
which is expected to return the last certificate in trusted chain.
The
The file, pkcs7_verify.c, will now be imported from linux code and
modified to fit into U-Boot environment.
In particular, pkcs7_verify_one() function will be used in a later patch
to rework signature verification logic aiming to support intermediate
certificates in "chain of trust."
Signed-off-b
This function will be called from x509_check_for_self_signed() and
pkcs7_verify_one(), which will be imported from linux in a later patch.
While it does exist in linux code and has a similar functionality of
rsa_verify(), it calls further linux-specific interfaces inside.
That could lead to more f
When the file, x509_public_key.c, was imported from linux code in
commit b4adf627d5b7 ("lib: crypto: add x509 parser"),
x509_check_for_self_signed() was commented out for simplicity.
Now it need be enabled in order to make pkcs7_verify_one(), which will be
imported in a later patch, functional
This function will be used to implement public_key_verify_signature()
in a later patch. rsa_verify() is not suitable here because calculation
of message digest is not necessary.
Signed-off-by: AKASHI Takahiro
---
include/u-boot/rsa.h | 3 +++
lib/rsa/rsa-verify.c | 8
2 files changed, 7
This function was nullified when the file, pkcs7_verify.c, was imported
because it calls further linux-specific interfaces inside, hence that
could lead to more files being imported from linux.
We need this function in pkcs7_verify_one() and so simply re-implement it
here instead of re-using the c
Summary
===
under the current implementation of secure boot merged in v2020.07-rc1,
UEFI subsystem verifies a signature using certificates that are coming
from signature dtabase, i.e. "db."
In real world, an image is signed by a signer, but its certificate
can also be signed by another CA and,
Signature database (db or dbx) may have not only certificates that contain
a public key for RSA decryption, but also digests of signed images.
In this test case, if database has an image's digest (EFI_CERT_SHA256_GUID)
and if the value matches to a hash value calculated from image's binary,
authen
Revocation database (dbx) may have not only certificates, but also
message digests of certificates with revocation time
(EFI_CERT_X509_SHA256_GUILD).
In this test case, if the database has such a digest and if the value
matches to a certificate that created a given image's signature,
authenticatio
In this test case, an image is signed multiple times with different
keys. If any of signatures contained is not verified, the whole
authentication check should fail.
Signed-off-by: AKASHI Takahiro
---
test/py/tests/test_efi_secboot/conftest.py| 7 +++
test/py/tests/test_efi_secboot/test_sig
Split the existing test case-1 into case1 and a new case-2:
case-1 for non-SecureBoot mode; case-2 for SecureBoot mode.
In addition, one corner case is added to case-2; a image is signed
but a corresponding certificate is not yet installed in "db."
Signed-off-by: AKASHI Takahiro
---
test/py/tes
In the test case (1g) of test_authvar, "db" is mistakenly used,
and it ends up being the exact same as (1f).
So correct it as "dbx" test case.
Signed-off-by: AKASHI Takahiro
---
test/py/tests/test_efi_secboot/test_authvar.py | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
dif
A signed image may have multiple signatures in
- each WIN_CERTIFICATE in authenticode, and/or
- each SignerInfo in pkcs7 SignedData (of WIN_CERTIFICATE)
In the initial implementation of efi_image_authenticate(), the criteria
of verification check for multiple signatures case is a bit ambiguous
In case that a type of certificate in "db" or "dbx" is
EFI_CERT_X509_SHA256_GUID, it is actually not a certificate which contains
a public key for RSA decryption, but a digest of image to be loaded.
If the value matches to a value calculated from a given binary image, it is
granted for loading.
Wi
Currently, we don't use any regular expression in matching outputs from
U-Boot. Since its use is just redundant, we can remove all.
Signed-off-by: AKASHI Takahiro
---
.../py/tests/test_efi_secboot/test_authvar.py | 73 +--
test/py/tests/test_efi_secboot/test_signed.py | 34 --
There are a couple of occurrences of hash calculations in which a new
efi_hash_regions will be commonly used.
Signed-off-by: AKASHI Takahiro
---
lib/efi_loader/efi_signature.c | 44 +-
1 file changed, 16 insertions(+), 28 deletions(-)
diff --git a/lib/efi_loader/
Since the size check against an entry in efi_search_siglist() is
incorrect, this function will never find out a to-be-matched certificate
and its associated revocation time in the signature list.
Signed-off-by: AKASHI Takahiro
---
lib/efi_loader/efi_signature.c | 5 +++--
1 file changed, 3 inser
UEFI specification requires that we shall support three type of
certificates of authenticode in PE image:
WIN_CERT_TYPE_EFI_GUID with the guid, EFI_CERT_TYPE_PCKS7_GUID
WIN_CERT_TYPE_PKCS_SIGNED_DATA
WIN_CERT_TYPE_EFI_PKCS1_15
As EDK2 does, we will support the first two that are pkcs7 Signed
Since the certificate table, which is indexed by
IMAGE_DIRECTORY_ENTRY_SECURITY and contains authenticode in PE image,
doesn't always exist, we should make sure that we will retrieve its pointer
only if it exists.
Signed-off-by: AKASHI Takahiro
---
lib/efi_loader/efi_image_loader.c | 29
Just for style consistency, replace all the uses of debug() to
EFI_PRINT() in efi_image_loader.c.
Signed-off-by: AKASHI Takahiro
---
lib/efi_loader/efi_image_loader.c | 64 ---
1 file changed, 33 insertions(+), 31 deletions(-)
diff --git a/lib/efi_loader/efi_image_lo
Just for style consistency, replace all the uses of debug() to
EFI_PRINT in efi_variable.c.
Signed-off-by: AKASHI Takahiro
---
lib/efi_loader/efi_variable.c | 27 ++-
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/lib/efi_loader/efi_variable.c b/lib/efi_l
Just for style consistency, replace all the uses of debug to
EFI_PRINT in efi_signature.c
Signed-off-by: AKASHI Takahiro
---
lib/efi_loader/efi_signature.c | 121 +
1 file changed, 62 insertions(+), 59 deletions(-)
diff --git a/lib/efi_loader/efi_signature.c b/li
This reverts commit 5827c2545849441dd60467565aac11964259972f.
Signed-off-by: AKASHI Takahiro
---
test/py/tests/test_efi_secboot/test_authvar.py | 8
test/py/tests/test_efi_secboot/test_signed.py | 4 ++--
test/py/tests/test_efi_secboot/test_unsigned.py | 6 +++---
3 files changed, 9
Summary
===
I'm currently working on reworking UEFI secure boot, aiming to add
"intermediate certificates" support. In this effort, I found a couple
of issues that should immediately be fixed or useful improvements even
without intermediate certificates support.
Each commit in this patch serie
The simplest solution to revert the commit b32ac16f9a32 ("test/py: fix
test_efi_secboot/conftest.py") is to move efi_console_register()
forward before efi_disk_register().
Signed-off-by: AKASHI Takahiro
---
lib/efi_loader/efi_setup.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
On Sun, Jun 7, 2020 at 3:26 AM Sean Anderson wrote:
>
> Signed-off-by: Sean Anderson
>
> ---
>
> common/spl/spl_opensbi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Bin Meng
Hi André,
On Mon, Jun 8, 2020 at 9:52 PM André Przywara wrote:
>
> On 07/06/2020 12:22, Jagan Teki wrote:
>
> Hi,
>
> (CC: ing Mark)
>
> Without looking to deep, I think invalidating the cache might be the
> right thing to do, but the rationale or at least the wording of it seems
> somehow flawed
Hi Sébastien,
> -Original Message-
> From: U-Boot On Behalf Of
> sba...@denx.de
> Sent: 2020年6月9日 1:22
> To: Sébastien Szymanski ; u-
> b...@lists.denx.de
> Subject: [EXT] [PATCH v2 1/1] imx: rom api: fix image offset computation
>
> Caution: EXT Email
>
> > When not booting from FlexSP
Am June 9, 2020 1:42:14 AM UTC schrieb AKASHI Takahiro
:
>Heinrich,
>
>On Mon, Jun 08, 2020 at 11:08:53PM +0200, Heinrich Schuchardt wrote:
>> Hello Takahiro,
>>
>> when trying to execute command
>>
>> ut lib lib_rsa_verify_valid
>>
>> on qemu_arm_defconfig with CONFIG_UNIT_TEST=y and
>> CONFIG
From: Bin Meng
Signed-off-by: Bin Meng
---
arch/riscv/dts/fu540-c000-u-boot.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/riscv/dts/fu540-c000-u-boot.dtsi
b/arch/riscv/dts/fu540-c000-u-boot.dtsi
index 0d3f710..35c153d 100644
--- a/arch/riscv/dts/fu540-c000-
From: Bin Meng
Signed-off-by: Bin Meng
---
arch/riscv/dts/fu540-c000-u-boot.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/riscv/dts/fu540-c000-u-boot.dtsi
b/arch/riscv/dts/fu540-c000-u-boot.dtsi
index 9bba554..0d3f710 100644
--- a/arch/riscv/dts/fu540-c000-u-bo
On 6/9/20 12:57 AM, Tom Rini wrote:
> On Mon, Jun 08, 2020 at 11:45:18PM +0200, Marek Vasut wrote:
>> On 6/6/20 6:24 PM, Tom Rini wrote:
>>> On Sat, Jun 06, 2020 at 04:54:52PM +0200, Marek Vasut wrote:
On 6/5/20 11:11 PM, Tom Rini wrote:
> On Fri, Jun 05, 2020 at 10:47:24PM +0200, Marek Va
Heinrich,
On Mon, Jun 08, 2020 at 11:08:53PM +0200, Heinrich Schuchardt wrote:
> Hello Takahiro,
>
> when trying to execute command
>
> ut lib lib_rsa_verify_valid
>
> on qemu_arm_defconfig with CONFIG_UNIT_TEST=y and
> CONFIG_RSA_VERIFY_WITH_PKEY=y it crashes in
>
> free((void *)prop->modulus
> -Original Message-
> From: Sean Anderson
> Sent: Monday, June 8, 2020 9:27 AM
> To: u-boot@lists.denx.de
> Cc: Tom Rini ; Bin Meng ;
> Rick Chen ; Simon Glass ;
> Sean Anderson ; Anatolij Gustschin ;
> Tan, Ley Foon ; Marek Vasut ;
> Simon Goldschmidt
> Subject: [PATCH v2 07/10] gpio
> -Original Message-
> From: Sean Anderson
> Sent: Monday, June 8, 2020 9:27 AM
> To: u-boot@lists.denx.de
> Cc: Tom Rini ; Bin Meng ;
> Rick Chen ; Simon Glass ;
> Sean Anderson ; Anatolij Gustschin ;
> Tan, Ley Foon ; Marek Vasut ;
> Simon Goldschmidt
> Subject: [PATCH v2 05/10] gpio
On Sun, Jun 07, 2020 at 08:33:00PM -0600, Simon Glass wrote:
> This displays incorrect data at present due to a missing header file
> in display_options. Fix it.
>
> Fixes: 09140113108 ("command: Remove the cmd_tbl_t typedef")
>
> Signed-off-by: Simon Glass
Applied to u-boot/master, thanks!
-
Hey all,
It's release day and I've tagged v2020.07-rc4. We continue to move
along at a good pace. But at this point, we need to take in just bug
fixes and Kconfig migrations. To help with any sort of contention on
this, I'm also opening up -next at this point.
Once again, for a changelog,
git
On Mon, Jun 08, 2020 at 11:45:18PM +0200, Marek Vasut wrote:
> On 6/6/20 6:24 PM, Tom Rini wrote:
> > On Sat, Jun 06, 2020 at 04:54:52PM +0200, Marek Vasut wrote:
> >> On 6/5/20 11:11 PM, Tom Rini wrote:
> >>> On Fri, Jun 05, 2020 at 10:47:24PM +0200, Marek Vasut wrote:
> On 6/5/20 9:07 PM, To
Enable the rng so UEFI can provide entropy for KASLR
Signed-off-by: Peter Robinson
---
arch/arm/dts/rk3399-pinebook-pro-u-boot.dtsi | 4
arch/arm/dts/rk3399-rockpro64-u-boot.dtsi| 4
configs/pinebook-pro-rk3399_defconfig| 2 ++
3 files changed, 10 insertions(+)
diff --git
Some minor fixes for SPI flash on the Pinebook Pro and also
default to saving environment to the SPI flash as it's
guaranteed to be on board.
Signed-off-by: Peter Robinson
---
arch/arm/dts/rk3399-pinebook-pro-u-boot.dtsi | 6 +-
configs/pinebook-pro-rk3399_defconfig| 3 +++
include/c
The built in keyboard on the Pinebook Pro is attached via USB so
fix this up to ensure USB works as expected.
Signed-off-by: Peter Robinson
---
configs/pinebook-pro-rk3399_defconfig | 5 +
include/configs/pinebook-pro-rk3399.h | 3 +++
2 files changed, 8 insertions(+)
diff --git a/configs/p
On 6/6/20 6:24 PM, Tom Rini wrote:
> On Sat, Jun 06, 2020 at 04:54:52PM +0200, Marek Vasut wrote:
>> On 6/5/20 11:11 PM, Tom Rini wrote:
>>> On Fri, Jun 05, 2020 at 10:47:24PM +0200, Marek Vasut wrote:
On 6/5/20 9:07 PM, Tom Rini wrote:
> On Wed, Jun 03, 2020 at 02:01:08AM +0200, Marek Vas
Hello Takahiro,
when trying to execute command
ut lib lib_rsa_verify_valid
on qemu_arm_defconfig with CONFIG_UNIT_TEST=y and
CONFIG_RSA_VERIFY_WITH_PKEY=y it crashes in
free((void *)prop->modulus) called from
rsa_free_key_prop() called from
rsa_verify_key() called from
rsa_verify_with_pkey().
On Mon, Jun 08, 2020 at 01:05:21PM -0400, Sean Anderson wrote:
> On 6/8/20 2:24 AM, Michal Simek wrote:
> > It is in u-boot mainline from February. Then we had to fix it in April.
>
> Do you have a link/commit hash for said fix?
>
> > In the middle of this I have seen IIC one patchset which impro
Some non-x86 devices can use SPI flash to boot and need to produce images
of a fixed size to program the flash.
Add a way to handle this for non-x86 boards.
Signed-off-by: Simon Glass
---
Makefile | 13 +
1 file changed, 13 insertions(+)
diff --git a/Makefile b/Makefile
index d463
Add a simple binman config and enable CONFIG_HAS_ROM so that U-Boot
produces a ROM for jerry.
Change the binman image definition to support multiple images, since it
may be used to build both u-boot-rockchip.bin and u-boot.rom
Signed-off-by: Simon Glass
---
arch/arm/dts/rk3288-u-boot.dtsi
Add a simple binman config and enable CONFIG_HAS_ROM so that U-Boot
produces a ROM for bob.
Signed-off-by: Simon Glass
---
arch/arm/dts/rk3399-gru-u-boot.dtsi | 4
arch/arm/dts/rk3399-gru.dtsi | 2 +-
arch/arm/dts/rk3399-u-boot.dtsi | 27 +++
arch
This option allows the serial console to work correctly. Add it.
Signed-off-by: Simon Glass
---
configs/chromebook_jerry_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/chromebook_jerry_defconfig
b/configs/chromebook_jerry_defconfig
index 443e3cdace..7f772b828f 100644
---
At present this file supports only 64-bit machines. Add an #ifdef so that
it can be included without problems on 32-bit machines also.
Signed-off-by: Simon Glass
---
arch/arm/dts/rockchip-u-boot.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/dts/rockchip-u-boot.dtsi
b/arch
Update the config for chromebook_bob to support booting from SPI flash.
The existing SPL size is too small since ATF is needed, so double it.
Signed-off-by: Simon Glass
---
configs/chromebook_bob_defconfig | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/configs/chromebook
If the pylibfdt shared-object file is detected, then Python assumes that
the libfdt.py file exists also.
Sometimes when an incremental build aborts, the shared-object file is
built but the libfdt.py is not. The only way out at this point is to use
'make mkproper', or similar.
Fix this by removing
Bob is a Chromebook and can boot from SPI flash. Add it to the condition
check for this.
Signed-off-by: Simon Glass
---
arch/arm/mach-rockchip/spl.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-rockchip/spl.c b/arch/arm/mach-rockchip/spl.c
index cddf4fd3d5
Most x86 boards build a u-boot.rom which is programmed into SPI flash. But
this is not unique to x86. For example some rockchip boards can also boot
from SPI flash.
Also, at least on x86, binary blobs are sadly quite common. It is not
possible to build a functional image without them, and U-Boot n
Some typos have been fixed in the code but the entry docs were not
regenerated. Fix this.
Signed-off-by: Simon Glass
---
tools/binman/README.entries | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/binman/README.entries b/tools/binman/README.entries
index 4f2c48fdc2
As a first step to integrating mkimage into binman, add a new entry type
that feeds data into mkimage for processing and incorporates that output
into the image.
Signed-off-by: Simon Glass
---
tools/binman/README.entries | 23
tools/binman/etype/_testing.py| 5 +++
tools
These can appear when moving between branches that have different tools
in the tree. Ignore them.
Signed-off-by: Simon Glass
---
.gitignore | 3 +++
1 file changed, 3 insertions(+)
diff --git a/.gitignore b/.gitignore
index 2e1c8bf2bf..e66aa864da 100644
--- a/.gitignore
+++ b/.gitignore
@@ -92
This comment references the wrong thing. Fix it.
Signed-off-by: Simon Glass
---
tools/binman/etype/cbfs.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/binman/etype/cbfs.py b/tools/binman/etype/cbfs.py
index e9aed8310c..744a32fa0c 100644
--- a/tools/binman/etype/cbf
Fix an over-length line in this function.
Signed-off-by: Simon Glass
---
drivers/core/device.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/core/device.c b/drivers/core/device.c
index a7408d9c76..2e3d555ea4 100644
--- a/drivers/core/device.c
+++ b/drivers/core/d
Now that binman uses tools/ as its base directory for importing modules,
the path to the pylibfdt build by U-Boot is incorrect. Fix it.
Signed-off-by: Simon Glass
---
tools/binman/main.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/binman/main.py b/tools/binman/mai
Rockchip-based Chromebooks support booting from SPI flash. It is annoying
to have to manually build the SPI image when the SD image is built
automatically.
This feature is already available for x86 devices, so the existing
mechanism is reused. Briefly, this allows a BUILD_ROM environment variable
On Mon, Jun 08, 2020 at 07:32:47AM +, Priyanka Jain wrote:
> Dear Tom,
> Please find my pull-request for u-boot-mpc85xx
> https://travis-ci.org/github/p-priyanka-jain/u-boot/builds/694639674
>
> Summary
> DM_ETH support for P2041RDB, T1024RDB, P5040DS, P3041DS, P4080DS, bug fixes
> Add TBI Ph
On Mon, Jun 08, 2020 at 03:23:33PM +0800, Kever Yang wrote:
> Hi Tom,
>
> Please pull the rockchip updates/fixes:
> - revive rk3399 puma board to adapt mainline dts;
> - Fix rk3399-evb stdout path;
> - Enable PCIe for rk3399: Rockpro64, firefly, pinebookpro;
> - Add rk3328 Rock-pi-e board;
> - En
On Wed, May 20, 2020 at 2:35 PM Tom Rini wrote:
>
> On Wed, May 20, 2020 at 01:38:01PM +0200, Robert Marko wrote:
>
> > Tom,
> > I have tried various things but CONFIG_IS_ENABLED won't work inside of
> > switch case.
> > It works fine outside of if though.
>
> OK, thanks, I'll poke things more to
ROC-RK3399-PC has specific set of configurations for
on-board led setup.
Due to easiness for user to know the state of the board
roc-rk339-pc board code will setup the low power led
on/off, and waiting for user to press power key and then
glow full power led.
All this needs to happen only during
roc-rk3399-pc has some specific requirements to support LEDS,
environment. board detection and etc prior to U-Boot proper.
So as of now SPL would be a better stage for these custom board
requirements to support unlike TPL. Adding few of these custom
requirements like LEDS in TPL would require extr
reset cause is a generic functionality based on the soc
cru registers in rockchip. This can be used for printing
the cause of reset in cpuinfo or some other place where
reset cause is needed.
Other than cpuinfo, reset cause can also be using during
bootcount for checking the specific reset cause
Usually printing the SPL banner varies between architecture
or board codes.
- Some would print before relocation at the end board_init_f
for making sure all initialization prior to this would happen
properly. if at all there is a requirement for serial init,
that happens properly since it pri
This series supports custom initialization code required for
roc-rk3399-pc board on SPL stage. I have marked it as v3, since
we have tried this before on this series[1].
Now this series is well mature code handling to add custom
spl_board_init code parts.
roc-rk3399-pc would require custom le
Current spl_board_init is mostly specific to puma-rk3399
target and in other words it cannot be required or useful
for other rk3399 boards.
Some boards require their custom initialization to be part
of spl_board_init like roc-rk3399-pc require leds setup,
environments.
So, this patch handles all
Document SPI flash program steps for rockchip platforms.
Suggested-by: Hugh Cole-Baker
Signed-off-by: Jagan Teki
Reviewed-by: Kever Yang
---
Changes for v4:
- none
doc/board/rockchip/rockchip.rst | 26 +-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/do
Mark the default U-Boot environment as SPI flash since
this is an on board flash device.
Updated env offset, size in contrast with default since
the U-Boot proper has starting from 384K.
Signed-off-by: Jagan Teki
---
Changes for v4:
- adjust env offset, size
configs/roc-pc-mezzanine-rk3399_def
On rockchip platforms, SPI boot image creation is not
straightforward like MMC boot image creation where former
requires to specify tpl, spl in multimage format in mkimage,
and later simply do a concatenate mkimaged-tpl with spl.
On this note, let drop rkspi image type creation via kbuild
and let
U-Boot TPL 2020.07-rc3-00090-gd4e919f927-dirty (Jun 01 2020 - 23:45:53)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
256B stride
lpddr4_set_rate: ch
Now, nvme scan seems stable with environment.
This series v4 version for SPI boot support on rk3399.
Changes for v4:
- adjust env offset, size
changes for v3:
- SPI env offset, size changes based on roc-rk3399-pc
Changes for v2:
- same defconfig to support both MMC, SPI boot
- add spi flash progr
Hi Simon,
On 01/06/20 08:45AM, Simon Glass wrote:
> Hi Pratyush,
>
> On Mon, 1 Jun 2020 at 05:22, Pratyush Yadav wrote:
> >
> > On 31/05/20 08:08AM, Simon Glass wrote:
> > > Hi Pratyush,
> > >
> > > On Fri, 29 May 2020 at 15:39, Pratyush Yadav wrote:
> > > >
> > > > Hi,
> > > >
> > > > This is
On 6/8/20 11:12 AM, Simon Glass wrote:
> Hi Stephen,
>
> On Mon, 8 Jun 2020 at 10:43, Stephen Warren wrote:
>>
>> On 6/7/20 7:45 AM, Simon Glass wrote:
>>> On Thu, 4 Jun 2020 at 09:24, Heiko Schocher wrote:
make the sleep time and the margin configurable.
Signed-off-by: Heiko
> The iMX7D RM 9.2.4.9.3 Power removal flow Table 9-11. Re-enabling power
> explicitly says both the DDR controller and the PHY must be reset in the
> correct sequence. Currently the code only resets the controller. This
> leads to a misbehavior where the system brings the DRAM up after reboot,
> b
> Currently the watchdog driver is not selected, which causes the following
> warnings in both SPL and U-Boot proper:
> U-Boot SPL 2020.07-rc1-00387-g67887903af (May 07 2020 - 23:49:27 -0300)
> Normal Boot
> WDT: Started without servicing (60s timeout)
> Trying to boot from MMC1
> U-Boot 2020.07-
> i.MX8M could use imx bootaux to boot m4/m7 core, so let's add it
> to the dependency list.
> Signed-off-by: Peng Fan
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
=
DENX Software Engineering GmbH,
> Currently watchdog driver is not selected, which causes system to reboot
> after staying 60s in the U-Boot prompt.
> Fix this problem by enabling CONFIG_WATCHDOG so that watchdog can be
> properly serviced.
> Signed-off-by: Fabio Estevam
> Reviewed-by: Adam Ford
Applied to u-boot-imx, master,
> None of these splash screen loading errors are so critical as to
> justify complete failure to boot, so just print error message as
> needed and return 0, the boot can very likely continue without
> the splash.
> Fix a couple of missing free(dst) instances as well.
> Signed-off-by: Marek Vasut
>
> From: Peng Fan
> timer_init has been invoked in arch_cpu_init, no need to invoke
> it again in board code.
> Signed-off-by: Peng Fan
> Signed-off-by: Fabio Estevam
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
> From: Peng Fan
> The u-boot-spl.bin pad with ddr firmware conflicts with the
> CONFIG_MALLOC_F_ADDR area, the ddr firmware will be overwritten
> by malloc in SPL stage and cause ddr initialization not able
> to finish. So update the related addresses to fix the issue.
> Reported-by: Fabio Esteva
On Mon, Jun 8, 2020 at 10:43 PM Simon Glass wrote:
>
> Hi Rayagonda,
>
> On Mon, 8 Jun 2020 at 11:03, Rayagonda Kokatanur
> wrote:
> >
> > Hi Simon,
> >
> > On Thu, Jun 4, 2020 at 8:30 AM Simon Glass wrote:
> > >
> > > Hi Rayagonda,
> > >
> > > On Wed, 3 Jun 2020 at 03:10, Rayagonda Kokatanur
>
> Currently watchdog driver is not selected, which causes system to reboot
> after staying 60s in the U-Boot prompt.
> Fix this problem by enabling CONFIG_WATCHDOG so that watchdog can be
> properly serviced.
> Signed-off-by: Fabio Estevam
Applied to u-boot-imx, master, thanks !
Best regards,
St
> Currently watchdog driver is not selected, which causes system to reboot
> after staying 60s in the U-Boot prompt.
> Fix this problem by enabling CONFIG_WATCHDOG so that watchdog can be
> properly serviced.
> Signed-off-by: Fabio Estevam
Applied to u-boot-imx, master, thanks !
Best regards,
St
> Add a README file explaining the U-Boot build and SD card flash procedures.
> Signed-off-by: Fabio Estevam
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
=
DENX Software Engineering GmbH, Managing
> From: Peng Fan
> Drop useless getting ccm device, there is no need to explicted do this
> in board code, and we not enable SPL CLK currently.
> Signed-off-by: Peng Fan
> Signed-off-by: Fabio Estevam
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
=
> From: Peng Fan
> We no need invoke the code, since spl framework could help
> us do that.
> Signed-off-by: Peng Fan
> Signed-off-by: Fabio Estevam
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
=
DEN
> With yModem the FIT Image is only supplied once, so we can only
> seek forward in the yModem supplied image and never backwards.
> With the recent changes to the SPL mechanism, including loading
> U-Boot first, FDT after, then the loadables, we must also reorder
> the FIT image script to make sur
> Convert the board to DM_ETH instead of legacy networking. This requires
> a minor addition to the DT to satisfy the requirement for specifying a
> PHY node. No functional change from board user perspective.
> Signed-off-by: Marek Vasut
> Cc: Fabio Estevam
> Cc: NXP i.MX U-Boot Team
> Cc: Peng
> This change updates the MTD partition layout on SPI-NOR memory for display5
> board.
> Signed-off-by: Lukasz Majewski
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
=
DENX Software Engineering GmbH,
> Accidentally submitted a patch with indentation not correct, let's fix it
> by indenting wrong lines.
> Signed-off-by: Giulio Benetti
> Acked-by: Peng Fan
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
==
> Add Kconfig entry for the PFUZE PMIC, SPL variant.
> Signed-off-by: Marek Vasut
> Cc: Fabio Estevam
> Cc: Jaehoon Chung
> Cc: Peng Fan
> Cc: Stefano Babic
> Reviewed-by: Jaehoon Chung
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
=
> From: Peng Fan
> Use spl_early_init to replace spl_init, spl_init will be invoked
> in board_init_r, we only need use spl_early_init to setup malloc
> and scan early dt.
> Signed-off-by: Peng Fan
> Signed-off-by: Fabio Estevam
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babi
> When not booting from FlexSPI, the offset computation is:
> offset = image_offset + CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR * 512 -
> 0x8000;
> When booting from SD card or eMMC user partition, image_offset is
> 0x8000. It is useless to add and remove 0x8000.
> When booting from other device, im
1 - 100 of 156 matches
Mail list logo
