Hi Weijie,
On 08.01.20 03:59, Weijie Gao wrote:
This patch series are divided into two parts:
The main part is to rewrite the whole architecture code of mt7628:
1. Lock parts of the d-cache for initial stack so the rest of the code can
be reimplemented in C.
2. Memory controller & DDR
On 07.01.20 15:30, Mauro Condarelli wrote:
On 1/7/20 2:21 PM, Stefan Roese wrote:
Hi Mauro,
On 27.12.19 14:25, Mauro Condarelli wrote:
Small patch series to add support for VoCore/VoCore2 board.
VoCore is open hardware and runs OpenWrt/LEDE.
It has WIFI, USB, UART, 20+ GPIOs but is only
Record note about reducing number of BDs.
Signed-off-by: Michal Simek
---
drivers/net/zynq_gem.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/zynq_gem.c b/drivers/net/zynq_gem.c
index 78f94148b411..c3fe8e3c563f 100644
--- a/drivers/net/zynq_gem.c
+++ b/drivers/net/zynq_gem.c
On 1/8/2020 9:39 AM, Simon Glass wrote:
> Hi T,
>
> On Tue, 7 Jan 2020 at 20:24, Thirupathaiah Annapureddy
> wrote:
>>
>> Subnodes under "/firmware" node are scanned twice in dm_scan_fdt_node
>> and dm_extended_scan_fdt. This patch removes the double scanning.
>>
>> This reverts commit
Hi Tom,
A small PR with MC8309 fixes from Rasmus.
CI: https://travis-ci.com/si-gdsys/u-boot-mpc83xx/builds/143550229
The following changes since commit d8a3f5259a36e76d1de127f65714c40918e8ee4c:
Merge tag 'u-boot-imx-20200107' of
https://gitlab.denx.de/u-boot/custodians/u-boot-imx (2020-01-07
If make the ref clock optional, no need refer to fixed-clock when
the ref clock is always on or comes from oscillator directly.
Signed-off-by: Chunfeng Yun
Reviewed-by: Simon Glass
Reviewed-by: Ryder Lee
---
v2: add reviewed-by Simon & Ryder
---
drivers/phy/phy-mtk-tphy.c | 3 ++-
1 file
This is used to avoid clk_enable() return -ENOSYS.
Signed-off-by: Chunfeng Yun
Reviewed-by: Simon Glass
Reviewed-by: Ryder Lee
---
v2: add reviewed-by Simon & Ryder
---
drivers/clk/clk_fixed_rate.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/clk/clk_fixed_rate.c
The SSUSB IP's clocks come from ssusbsys module on mt7629,
so add its driver
Signed-off-by: Chunfeng Yun
Reviewed-by: Simon Glass
Reviewed-by: Ryder Lee
---
v2: add reviewed-by Simon & Ryder
---
drivers/clk/mediatek/clk-mt7629.c | 42 +++
1 file changed, 42
If skip all return error number, it may skip some real error cases,
so only skip the error when the clock is not provided in DTS
Signed-off-by: Chunfeng Yun
Reviewed-by: Simon Glass
Reviewed-by: Ryder Lee
---
v2: add reviewed-by Simon & Ryder
---
drivers/clk/clk-uclass.c | 2 +-
1 file
Sometimes we may need get (optional) clock without a device,
that means use ofnode.
e.g. when the phy node has subnode, and there is no device created
for subnode, in this case, we need these new APIs to get subnode's
clock.
Signed-off-by: Chunfeng Yun
Reviewed-by: Simon Glass
Reviewed-by:
No need check -ENOSYS anymore after add dummy_enable() for
fixed-clock.
Signed-off-by: Chunfeng Yun
Reviewed-by: Simon Glass
Reviewed-by: Ryder Lee
---
v2: add reviewed-by Simon & Ryder
---
drivers/phy/phy-mtk-tphy.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
Add valid check for clk->dev, it's useful when get optional
clock even when the clk point is valid, but its dev will be
NULL.
Signed-off-by: Chunfeng Yun
Reviewed-by: Simon Glass
Reviewed-by: Ryder Lee
---
v2: add reviewed-by Simon & Ryder
---
drivers/clk/clk-uclass.c | 16
1
>-Original Message-
>From: Tom Rini
>Sent: 2020年1月9日 4:12
>To: Peng Ma
>Cc: s...@chromium.org; Priyanka Jain ; Marcel
>Ziswiler ; Andy Tang ;
>u-boot@lists.denx.de
>Subject: [EXT] Re: [PATCH 1/3] ata: sata_sil: Continue probing other sata port
>when failed current port.
>
>On Wed, Dec
> Subject: Re: [PATCH] imx: imx8qxp_mek: update README
>
> Hi Peng,
>
> On Wed, Jan 8, 2020 at 10:44 PM Peng Fan wrote:
>
> > U-Boot 2020.01-00243-g21aede21b0 (Jan 09 2020 - 10:01:31 +0800)
> >
> > CPU: NXP i.MX8QXP RevB A35 at 1200 MHz at 20C
> >
> > Model: Freescale i.MX8QXP MEK
> > Board:
Hi Peng,
On Wed, Jan 8, 2020 at 10:44 PM Peng Fan wrote:
> U-Boot 2020.01-00243-g21aede21b0 (Jan 09 2020 - 10:01:31 +0800)
>
> CPU: NXP i.MX8QXP RevB A35 at 1200 MHz at 20C
>
> Model: Freescale i.MX8QXP MEK
> Board: iMX8QXP MEK
> Build: SCFW 550f3079, SECO-FW d7523fe8, ATF f900faa
I see a
> Subject: Re: [PATCH] imx: imx8qxp_mek: update README
>
> Hi Peng,
>
> On Wed, Jan 8, 2020 at 10:33 PM Peng Fan wrote:
>
> > The ipg clk patch needs to be reverted for now. Anyway the log as below:
>
> Which commit are you referring to? Can you send a revert? Is this revert
> needed for
Hi Peng,
On Wed, Jan 8, 2020 at 10:33 PM Peng Fan wrote:
> The ipg clk patch needs to be reverted for now. Anyway the log as below:
Which commit are you referring to? Can you send a revert? Is this
revert needed for booting this board?
> U-Boot SPL 2020.01-00025-gedb89b239c-dirty (Jan 08 2020
> Subject: RE: [PATCH] imx: imx8qxp_mek: update README
>
> > Subject: Re: [PATCH] imx: imx8qxp_mek: update README
> >
> > Hi Peng
> >
> > On Tue, Jan 7, 2020 at 10:33 PM Peng Fan wrote:
> > >
> > > Update README to use 4.19.35_1.1.0 released firmware images.
> >
> > I have tried the same here
Only the wandboard revD1 boards have PMIC, so when running on a wandboard
of different revision the following error is always shown on every boot:
pmic_get() ret -19
Instead of printing this error message, move it to debug level instead.
Signed-off-by: Fabio Estevam
---
On 12/18/19 1:44 AM, AKASHI Takahiro wrote:
One of major missing features in current UEFI implementation is "secure boot."
The ultimate goal of my attempt is to implement image authentication based
on signature and provide UEFI secure boot support which would be fully
compliant with UEFI
On Thu, Jan 09, 2020 at 02:24:04AM +0900, Masahiro Yamada wrote:
> Hi Tom,
>
> Here is a small change set for v2020.04
> Please pull. Thanks.
>
>
>
> The following changes since commit d8a3f5259a36e76d1de127f65714c40918e8ee4c:
>
> Merge tag 'u-boot-imx-20200107' of
>
c: make early_delay more robust (2020-01-07
> 10:26:57 +0100)
>
> are available in the Git repository at:
>
> https://gitlab.denx.de/u-boot/custodians/u-boot-imx.git
> tags/u-boot-imx-20200108
>
> for you to fetch changes up to 028c8c411976c30758ddb5f5ffeef792e4595d8d:
>
&
On Wed, Jan 08, 2020 at 04:31:55PM +0100, Marek Vasut wrote:
> The following changes since commit 5a8fa095cb848c60c630a83edf30d4fc46101e90:
>
> Merge branch 'next' (2020-01-06 17:07:49 -0500)
>
> are available in the Git repository at:
>
> git://git.denx.de/u-boot-socfpga.git master
>
>
t/custodians/u-boot-amlogic.git
> tags/u-boot-amlogic-20200108
>
> for you to fetch changes up to 262d34363373c10a00279036c1561283c30495c2:
>
> board: amlogic: select PWRSEQ for all amlogic platform (2020-01-07 14:50:41
> +0100)
>
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
On 12/18/19 1:45 AM, AKASHI Takahiro wrote:
With this commit, image validation can be enforced, as UEFI specification
section 32.5 describes, if CONFIG_EFI_SECURE_BOOT is enabled.
Currently we support
* authentication based on db and dbx,
so dbx-validated image will always be rejected.
*
On 12/18/19 1:44 AM, AKASHI Takahiro wrote:
One of major missing features in current UEFI implementation is "secure boot."
The ultimate goal of my attempt is to implement image authentication based
on signature and provide UEFI secure boot support which would be fully
compliant with UEFI
On 12/18/19 1:45 AM, AKASHI Takahiro wrote:
With this commit, EFI_VARIABLE_TIME_BASED_AUTHENTICATED_WRITE_ACCESS
is supported for authenticated variables and the system secure state
will transfer between setup mode and user mode as UEFI specification
section 32.3 describes.
Internally,
On 1/8/20 6:43 PM, Heinrich Schuchardt wrote:
On 11/21/19 1:11 AM, AKASHI Takahiro wrote:
In this patch, a very simple test is added to verify that rsa_verify()
using rsa_verify_with_pkey() work correctly.
To keep the code simple, all the test data, either public key and
verified binary
On Wed, Jan 08, 2020 at 10:49:44PM +0100, Anatolij Gustschin wrote:
> On Wed, 8 Jan 2020 15:12:44 -0500
> Tom Rini tr...@konsulko.com wrote:
> ...
> > This is a correct bug fix, yes. It also causes size growth on tbs2910
> > that is in turn fatal on CI. For the moment I'm setting this patch
> >
On Wed, Jan 08, 2020 at 10:38:32PM +0100, Anatolij Gustschin wrote:
> This can be used for device tree size reduction similar as
> CONFIG_OF_SPL_REMOVE_PROPS option. For tbs2910 board this
> shrinks the image size: all -2304.0 bss -16.0 text -2288.0
>
> Signed-off-by: Anatolij Gustschin
On Wed, 8 Jan 2020 15:12:44 -0500
Tom Rini tr...@konsulko.com wrote:
...
> This is a correct bug fix, yes. It also causes size growth on tbs2910
> that is in turn fatal on CI. For the moment I'm setting this patch
> aside so that I can take the rest of the series and figure out what to
> do with
On Fri, 6 Dec 2019 13:43:05 -0500
Tom Rini tr...@konsulko.com wrote:
...
> This gets an important conversation started. Perhaps we should expand
> OF_SPL_REMOVE_PROPS for full U-Boot, with some gating symbol for the
> platforms that do want to pass through the full DT to the OS?
I've sent
This shrinks the image size: all -1536.0 bss +16.0 text -1552.0
Signed-off-by: Anatolij Gustschin
---
NOTE: building with this patch only works when patch [1] is applied.
[1] http://patchwork.ozlabs.org/patch/1219944
configs/tbs2910_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
This can be used for device tree size reduction similar as
CONFIG_OF_SPL_REMOVE_PROPS option. For tbs2910 board this
shrinks the image size: all -2304.0 bss -16.0 text -2288.0
Signed-off-by: Anatolij Gustschin
---
dts/Kconfig | 8
scripts/Makefile.lib | 3 ++-
2 files changed,
Hi Heiko,
On Wed, Jan 8, 2020 at 8:45 AM Heiko Schocher wrote:
> diff --git a/configs/wandboard_defconfig b/configs/wandboard_defconfig
> index ca564c5..62b013c 100644
> --- a/configs/wandboard_defconfig
> +++ b/configs/wandboard_defconfig
> @@ -42,8 +42,8 @@ CONFIG_CMD_BMP=y
>
With some device trees (i.e. i.MX6 SoC) and longer REMOVE_PROPS list
the fdtgrep tool stops with "Internal error with fdtgrep_find_regions()".
Increase 'max_regions' count to avoid such errors.
Signed-off-by: Anatolij Gustschin
---
tools/fdtgrep.c | 2 +-
1 file changed, 1 insertion(+), 1
Fix function name and parenthesis.
Signed-off-by: Anatolij Gustschin
---
tools/fdtgrep.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/fdtgrep.c b/tools/fdtgrep.c
index 8f44f599c1..052d419692 100644
--- a/tools/fdtgrep.c
+++ b/tools/fdtgrep.c
@@ -824,7 +824,7 @@
Hi Heiko,
On Wed, Jan 8, 2020 at 4:52 PM Fabio Estevam wrote:
> The support for imx6q-wandboard-revd1 and imx6dl-wandboard-revd1 still
> needs to be added (it used to work prior to the DM conversion as you
> noticed), but unfortunately I don't have access to these variants.
Could you please
On Tue, Jan 7, 2020 at 5:43 AM Adam Ford wrote:
>
> On Sun, Oct 27, 2019 at 10:55 AM Simon Glass wrote:
> >
> > Bring over the fdt from this commit:
> >
> > 430419c (origin/master) tests: fix some python warnings
> >
> > adding in the 'assumptions' series designed to reduce code size.
> >
> >
Hi list,
I think there's a bug in kwboot.
I have a faulty board that stops acking xmodem frames after a certain number of packets and kwboot
instead of exiting continues to send frames up to 100%.
With the one second retry timer it's very long! More than 2 hours :-(
The bug is in the
Hi folks,
I would like to run the memory tests implemented in
drivers/post/memory.c. I'm interested in the CONFIG_SPL_POST_MEM_SUPPORT
configuration (common/spl/Kconfig), but enabling it just seems to
compile everything under post/drivers folder, it does not run the memory
tests. Should I
On Fri, Dec 06, 2019 at 03:01:48PM +0100, Patrice Chotard wrote:
> This patches restores boot on boards which rely on
> CONFIG_SYS_UBOOT_START equal to CONFIG_SYS_TEXT_BASE when using SPL
>
> Fixes: d3e97b53c1f2 ("spl: fix entry_point equal to load_addr")
>
> Signed-off-by: Patrice Chotard
>
On Tue, Dec 17, 2019 at 07:07:04PM +0100, Philippe Reynes wrote:
> There is black magic in the file conftest.py that list
> all the test unit. Then, all those test unit are called
> in pytest. This call is done with the end of the name
> (for example checksum if the full name is
On Thu, Dec 05, 2019 at 06:46:11PM -0500, Tom Rini wrote:
> Per Enea OSE documentation, it supports some classes of ARM, PowerPC and
> X86. Limit the option to those platforms.
>
> Signed-off-by: Tom Rini
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
On Fri, Dec 06, 2019 at 03:01:49PM +0100, Patrice Chotard wrote:
> As previous CONFIG_SYS_UBOOT_START is now set by default to
> CONFIG_SYS_TEXT_BASE when not defined, CONFIG_SYS_UBOOT_START
> can be removed from include/configs board files.
>
> Signed-off-by: Patrice Chotard
> Acked-by: Lukasz
On Sat, Nov 09, 2019 at 04:56:10AM +0100, Heiko Schocher wrote:
> if MULTI_DTB_FIT is enabled it is helpful to display
> the value of gd->multi_dtb_fit in bdinfo.
>
> Signed-off-by: Heiko Schocher
> Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
--
Tom
signature.asc
On Wed, Dec 04, 2019 at 10:36:47AM +, Peng Ma wrote:
> If we didn't unbind the sata from block device, the same devices would
> be added after sata remove,
> This patch is to resolve this issue as below:
>
> => sata info
> SATA#0:
> (3.0 Gbps)
> SATA#1:
> (3.0 Gbps)
> Device 0:
On Wed, Dec 04, 2019 at 10:36:45AM +, Peng Ma wrote:
> In the initialization of sata driver, we want to initialize all port
> probes, Therefore, any detection failure between of them should continue
> initialization by skipping the current port instead of exit.
>
> Signed-off-by: Peng Ma
On Wed, Dec 04, 2019 at 10:36:42AM +, Peng Ma wrote:
> In the initialization of sata driver, we want to initialize all port
> probes, Therefore, any detection failure between of them should continue
> initialization by skipping the current port instead of exit.
>
> Signed-off-by: Peng Ma
On Mon, Nov 04, 2019 at 09:27:23AM +, Peng Fan wrote:
> off-on-delay-us has been supported by Linux, so let's use it.
>
> Signed-off-by: Peng Fan
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
On Wed, Oct 30, 2019 at 02:38:33PM +0100, Fabien Dessenne wrote:
> Load the optional resource table from the firmware, and write its
> address in the dedicated backup register.
>
> Signed-off-by: Fabien Dessenne
> Acked-by: Patrick Delaunay
Applied to u-boot/master, thanks!
--
Tom
On Wed, Oct 30, 2019 at 02:38:32PM +0100, Fabien Dessenne wrote:
> Since the coprocessor state is tracked in a backup register, there is
> no more need for tracking it in an environment variable : remove it.
>
> Signed-off-by: Fabien Dessenne
> Acked-by: Patrick Delaunay
Applied to
On Wed, Oct 30, 2019 at 02:38:28PM +0100, Fabien Dessenne wrote:
> Add rproc_elf_load_rsc_table(), which searches for a resource table in
> an elf64/elf32 image, and if found, copies it to device memory.
> Add also the elf32 and elf64 variants of this API.
> Add a test for this.
>
>
On Wed, Oct 30, 2019 at 02:38:31PM +0100, Fabien Dessenne wrote:
> Update the dedicated backup register to track the coprocessor state and
> rely on that register to compute the .is_running() value (which expects
> a return value of 0 -not 1- if the processor is running).
>
> Signed-off-by:
On Tue, Oct 22, 2019 at 04:39:22PM +0200, Jean-Jacques Hiblot wrote:
> spl_fit_get_image_name() is used to get the names of the images that the
> SPL must load from the FIT. It relies on the content of a property present
> in the FIT. The list of images is thus statically defined in the FIT.
>
On Wed, Oct 30, 2019 at 02:38:30PM +0100, Fabien Dessenne wrote:
> Reset ResourceTableAddress and CoprocessorState at cold boot, preserve
> these values at standby wakeup.
>
> Signed-off-by: Fabien Dessenne
> Acked-by: Patrick Delaunay
Applied to u-boot/master, thanks!
--
Tom
On Wed, Oct 30, 2019 at 02:38:29PM +0100, Fabien Dessenne wrote:
> Use the backup register #17 as coprocessor resource table address and
> backup register #18 as coprocessor state.
>
> Signed-off-by: Fabien Dessenne
> Acked-by: Patrick Delaunay
Applied to u-boot/master, thanks!
--
Tom
On Tue, Oct 22, 2019 at 04:39:20PM +0200, Jean-Jacques Hiblot wrote:
> Useful to avoid #ifdef throughout the code that uses the board driver API.
>
> Signed-off-by: Jean-Jacques Hiblot
> Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP
On Tue, Oct 22, 2019 at 04:39:18PM +0200, Jean-Jacques Hiblot wrote:
> Make the board driver available in the SPL too. The board driver is a way
> to provide useful information about the board and that can be useful in
> the SPL too.
>
> Signed-off-by: Jean-Jacques Hiblot
> Reviewed-by: Simon
On Tue, Oct 22, 2019 at 04:39:17PM +0200, Jean-Jacques Hiblot wrote:
> There is no need for it to be non-constant. Making it constant, allows to
> return constant string without warning.
>
> Signed-off-by: Jean-Jacques Hiblot
> Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
--
On Tue, Oct 22, 2019 at 04:39:19PM +0200, Jean-Jacques Hiblot wrote:
> This function will be used by the SPL to get the names of images to load
> from the FIT. This allows to load different images based on runtime HW
> detection.
>
> Signed-off-by: Jean-Jacques Hiblot
> Reviewed-by: Simon Glass
On Tue, Oct 22, 2019 at 04:39:21PM +0200, Jean-Jacques Hiblot wrote:
> If u-boot.img is a FIT image, CONFIG_OF_OVERLAY_LIST can be used to add
> DT overlays to u-boot.img.
>
> Signed-off-by: Jean-Jacques Hiblot
> Reviewed-by: Simon Glass
With Simon's nits corrected:
Applied to u-boot/master,
On Tue, Oct 22, 2019 at 04:39:13PM +0200, Jean-Jacques Hiblot wrote:
> If the node describing an overlay does not specify a load address, it will
> be loaded at the address previously used.
> Fixing it by allocating a temporary buffer that will be used as a
> default load address. By default, the
On Tue, Oct 22, 2019 at 04:39:15PM +0200, Jean-Jacques Hiblot wrote:
> There are many ways the overlay application can fail.
> 2 of them are probably the most common:
> - the application itself failed. Usually this is comes from an unresolved
> reference
> - DTBO not available in FIT (could be
On Tue, Oct 22, 2019 at 04:39:14PM +0200, Jean-Jacques Hiblot wrote:
> If one overlay that must be applied cannot be found in the FIT, the current
> implementation stops applying the overlays. Let's make it skip only the
> failing overlay instead.
>
> Signed-off-by: Jean-Jacques Hiblot
>
On Tue, Oct 22, 2019 at 04:39:12PM +0200, Jean-Jacques Hiblot wrote:
> Make room in the FDT before applying the overlay, otherwise it may fail if
> the overlay is big. As the exact added size is not known in advance, just
> add the size of the overlay.
> Move after the end of the application of
On Tue, Oct 22, 2019 at 04:39:16PM +0200, Jean-Jacques Hiblot wrote:
> In order to apply an overlay to a DTB. The DTB must have been generated
> with the option '-@'.
>
> Signed-off-by: Jean-Jacques Hiblot
> Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
--
Tom
signature.asc
On Tue, Oct 22, 2019 at 04:39:10PM +0200, Jean-Jacques Hiblot wrote:
> When u-boot.img is a FIT image generated automatically by mkimage, the
> configuration node has the following structure:
> conf-1 {
>description = "k3-am654-base-board";
>firmware = "firmware-1";
>loadables =
On Tue, Sep 17, 2019 at 05:09:34PM -0400, Andrew F. Davis wrote:
> This is very similar to fit_image_get_data but has the benefit of working
> on FIT images with external data unlike fit_image_get_data. This is
> useful for extracting sub-images from type of FIT image as this would
> previously
On Tue, Sep 17, 2019 at 05:09:35PM -0400, Andrew F. Davis wrote:
> This has the same result but some compilers will warn about this
> fall-through if there are statements as part of the label block.
>
> Signed-off-by: Andrew F. Davis
> Reviewed-by: Lokesh Vutla
Applied to u-boot/master,
On Tue, Oct 22, 2019 at 04:39:11PM +0200, Jean-Jacques Hiblot wrote:
> From: Michal Simek
>
> doc/uImage.FIT/overlay-fdt-boot.txt is describing how to create FIT
> image with DT overlays in it.
> Add support for this feature to SPL.
>
> Here is the ZynqMP fragment where dtb points to full DT
On Tue, Sep 17, 2019 at 05:09:33PM -0400, Andrew F. Davis wrote:
> The dumpimage utility errors out in a number of places without providing
> sufficient feedback to allow the user to easily determine what has gone
> wrong. Add additional error messages to make the cause of the failure
> more
Hi Heiko,
On Wed, Jan 8, 2020 at 2:41 AM Heiko Schocher wrote:
> Looking into git history, there is a commit from you:
>
> commit 5b858582512883b8a85d74e108873f9beed1e954
> Author: Fabio Estevam
> Date: Wed Jun 12 12:34:40 2019 -0300
>
> wandboard: Add FIT image support
>
> After
The command tpm (and tpm2) search the tpm and use it.
On sandbox, there are two tpm (tpm 1.x and tpm 2.0).
So the command tpm and tpm2 are always executed with
the first tpm (tpm 1.x), and the command tpm2 always
fails.
This add a subcommand device to command tpm and
command tpm2. Then the
On 1/8/20 7:07 PM, Heinrich Schuchardt wrote:
On 11/21/19 1:11 AM, AKASHI Takahiro wrote:
In the current implementation of FIT_SIGNATURE, five parameters for
a RSA public key are required while only two of them are essential.
(See rsa-mod-exp.h and uImage.FIT/signature.txt)
This is a
Hi Simon,
On Wed, Jan 08, 2020 at 10:39:34AM -0700, Simon Glass wrote:
> On Tue, 24 Dec 2019 at 09:52, Eugeniu Rosca wrote:
> > [5] New usage
> > adtimg addr - Set image location to
> > adtimg dump - Print out image contents
> > adtimg get dt
On 11/21/19 1:11 AM, AKASHI Takahiro wrote:
In the current implementation of FIT_SIGNATURE, five parameters for
a RSA public key are required while only two of them are essential.
(See rsa-mod-exp.h and uImage.FIT/signature.txt)
This is a result of considering relatively limited computer
Hi Tom,
This series has the potential for breakage due to badly written
drivers, so I'd like to get it in early in the merge window.
Tests here:
https://gitlab.denx.de/u-boot/custodians/u-boot-dm/pipelines/1790
The following changes since commit d8a3f5259a36e76d1de127f65714c40918e8ee4c:
Hi Simon,
On 1/8/20 6:39 PM, Simon Glass wrote:
Hi Giulio,
On Tue, 7 Jan 2020 at 10:23, Giulio Benetti
wrote:
Hi Stefano, Simon, All,
On 1/3/20 12:39 PM, Stefano Babic wrote:
Hi Giulio,
On 04/12/19 18:44, Giulio Benetti wrote:
This patchset add support for i.MXRT family starting from
On 11/21/19 1:11 AM, AKASHI Takahiro wrote:
In this patch, a very simple test is added to verify that rsa_verify()
using rsa_verify_with_pkey() work correctly.
To keep the code simple, all the test data, either public key and
verified binary data, are embedded in the source.
Signed-off-by:
Hi T,
On Tue, 7 Jan 2020 at 20:24, Thirupathaiah Annapureddy
wrote:
>
> Subnodes under "/firmware" node are scanned twice in dm_scan_fdt_node
> and dm_extended_scan_fdt. This patch removes the double scanning.
>
> This reverts commit 1712ca21924bff678f19fd3141f435408d23bdbf.
>
> Signed-off-by:
Hi Giulio,
On Tue, 7 Jan 2020 at 10:23, Giulio Benetti
wrote:
>
> Hi Stefano, Simon, All,
>
> On 1/3/20 12:39 PM, Stefano Babic wrote:
> > Hi Giulio,
> >
> > On 04/12/19 18:44, Giulio Benetti wrote:
> >> This patchset add support for i.MXRT family starting from i.MXRT1050 SoC.
> >> It provides:
Hi Sam,
On Tue, 24 Dec 2019 at 12:55, Sam Protsenko wrote:
>
> Android Boot Image v1 adds "Recovery DTB" field in image header and
> associate payload in boot image itself [1]. Payload should be in
> Android DTB/DTBO format [2]. That "Recovery DTB" area should be only
> populated for non-A/B
Hi Sam,
On Tue, 24 Dec 2019 at 12:55, Sam Protsenko wrote:
>
> Android Boot Image v2 adds "DTB" payload (and corresponding field in the
> image header). Provide functions for its handling:
>
> - android_image_get_dtb_by_index(): Obtain DTB blob from "DTB" part of
> boot image, by blob's
On Tue, 24 Dec 2019 at 09:51, Eugeniu Rosca wrote:
>
> With 'dtimg.c' renamed to 'adtimg.c', now ensure the naming
> consistency in the internal implementation of 'adtimg.c'.
>
> No functional change intended.
>
> Cc: Sam Protsenko
> Signed-off-by: Eugeniu Rosca
> ---
> cmd/adtimg.c | 51
Hi Eugeniu,
On Tue, 24 Dec 2019 at 09:52, Eugeniu Rosca wrote:
>
> Trying to extend 'adtimg' functionality [1], we've been severely hit
> by a major limitation in the command's usage scheme. Specifically, the
> command's user interface appears to be too centric to getting the
> DTB/DTBO entry
On Tue, 24 Dec 2019 at 12:55, Sam Protsenko wrote:
>
> This command can be used to extract fields and image payloads from
> Android Boot Image. It can be used for example to implement boot flow
> where dtb is taken from boot.img (as v2 incorporated dtb inside of
> boot.img). Using this command,
Hi Tom,
Here is a small change set for v2020.04
Please pull. Thanks.
The following changes since commit d8a3f5259a36e76d1de127f65714c40918e8ee4c:
Merge tag 'u-boot-imx-20200107' of
https://gitlab.denx.de/u-boot/custodians/u-boot-imx (2020-01-07
08:45:43 -0500)
are available in the Git
://gitlab.denx.de/u-boot/custodians/u-boot-imx.git
tags/u-boot-imx-20200108
for you to fetch changes up to 028c8c411976c30758ddb5f5ffeef792e4595d8d:
imx: imx8mn: enable CONFIG_CMD_ERASEENV (2020-01-08 13:20:09 +0100
Simon,
On 24/12/2019 16:58, Simon Glass wrote:
Hi Jean-Jacques,
On Mon, 16 Dec 2019 at 03:10, Jean-Jacques Hiblot wrote:
Hi Simon,
On 10/12/2019 16:18, Simon Glass wrote:
Hi Jean-Jacques,
On Tue, 5 Nov 2019 at 04:47, Jean-Jacques Hiblot wrote:
Some linux drivers provide their own
Am 08.01.20 um 04:01 schrieb Weijie Gao:
> u_boot_list is not only used by DM, but also by some SPL image load methods
> such as spl_nor.c.
>
> This patch removes CONFIG_SPL_DM surrounding the u_boot_list section to
> make sure SPL image load methods can be correctly built into u-boot without
Am 08.01.20 um 04:01 schrieb Weijie Gao:
> This patch rewrites the mtmips architecture with the following changes:
>
> 1. Move MT7628 soc parts into a subfolder.
> 2. Lock parts of D-Cache as temporary stack.
> 3. Reimplement DDR initialization in C language.
> 4. Reimplement DDR calibration
The following changes since commit 5a8fa095cb848c60c630a83edf30d4fc46101e90:
Merge branch 'next' (2020-01-06 17:07:49 -0500)
are available in the Git repository at:
git://git.denx.de/u-boot-usb.git master
for you to fetch changes up to 3a117e721cc5b4a366dbd5fbbf8df0a80cbb0fa2:
x86:
The following changes since commit 5a8fa095cb848c60c630a83edf30d4fc46101e90:
Merge branch 'next' (2020-01-06 17:07:49 -0500)
are available in the Git repository at:
git://git.denx.de/u-boot-socfpga.git master
for you to fetch changes up to 8097aee3abc3b773aceea01f756a38b34b274e1e:
ddr:
Am 08.01.20 um 04:01 schrieb Weijie Gao:
> When setting up initial stack, global data will also be put in the stack,
> and being cleared.
>
> The assembler instructions for clearing gd is as follows:
>
> movet0, k0
> 1:
> PTR_S zero, 0(t0)
> blt t0, t1, 1b
>
Am 08.01.20 um 04:01 schrieb Weijie Gao:
> Currently CONFIG_MIPS_INIT_STACK_IN_SRAM assumes the memory space for the
> initial stack can be used directly. However on some platform the SRAM needs
> initialization, e.g. lock cache.
>
> This patch adds an option to allow a new function
Am 08.01.20 um 04:01 schrieb Weijie Gao:
> Some systems boot up at a very low CPU frequency and set up a higher CPU
> frequency in lowlevel initialization.
>
> Currently get_tbclk() uses a fixed value (CONFIG_SYS_MIPS_TIMER_FREQ)
> for MIPS architercture, and CONFIG_SYS_MIPS_TIMER_FREQ is
Am 08.01.20 um 04:00 schrieb Weijie Gao:
> In U-Boot the exception vector base will be moved to top of memory, to be
> used to display register dump when exception occurs.
>
> But some old linux kernel does not honor the base set in CP0_EBASE. A
> modified exception vector base will cause
Am 01.01.20 um 08:34 schrieb Heinrich Schuchardt:
> Code sections should be syntax highlighted as bash.
> Comment lines in code should start with a hash sign ('#') but code lines
> should not.
> Most commands can be executed as normal users. Prepend those commands
> requiring elevated
Am 23.12.19 um 21:53 schrieb Alex Nemirovsky:
> Allow SoC or board layers with reconfigurable cpu clocks
> capabilties to do implementation specific lookups and service
> get_tbclk() requests.
>
> Signed-off-by: Alex Nemirovsky
> ---
>
> arch/mips/cpu/time.c | 2 +-
> 1 file changed, 1
1 - 100 of 141 matches
Mail list logo
