Hi Bob,
On Wed, Feb 28, 2024 at 7:14 PM Bob Wolff wrote:
>
> Any thoughts on how to proceed with the issue mentioned about tinycrypt
> warnings/checks?
>
> Also, I'd like your advice - I was thinking for the larger patch that I'd
> do it in two commits. The first would be the addition of the
Dear Tom,
The following changes for the *next* branch since commit
d49fa3defa50c6d3f04acbb52fd486c13c14ab6a:
Prepare v2024.04-rc3 (2024-02-26 21:23:36 -0500)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-efi.git
tags/efi-next-2024-02-28
for
On Wed, Feb 28, 2024 at 12:48:04PM +0200, Ilias Apalodimas wrote:
> commit 3d74a0977f514 ("ti: am335x: Remove unused linker script") removed
> the linker script for the TI variant. This linker script doesn't seem to
> do anything special and on top of that, has no definitions for the EFI
>
On Mon, Feb 26, 2024 at 03:19:13PM -0600, Bryan Brattlof wrote:
> Introduce the basic files needed to support the am62px family of SoCs
>
> Co-developed-by: Hari Nagalla
> Signed-off-by: Hari Nagalla
> Signed-off-by: Bryan Brattlof
Reviewed-by: Tom Rini
--
Tom
signature.asc
Description:
On Wed, Feb 28, 2024 at 08:11:52PM +0100, Heinrich Schuchardt wrote:
> Dear Tom,
>
> The following changes for the *next* branch since commit
> d49fa3defa50c6d3f04acbb52fd486c13c14ab6a:
>
> Prepare v2024.04-rc3 (2024-02-26 21:23:36 -0500)
>
> are available in the Git repository at:
>
>
Am 28.02.24 um 06:45 schrieb Dhruva Gole:
Hi,
On Feb 26, 2024 at 13:23:41 +0100, Wadim Egorov wrote:
Add documentation for PHYTEC phyCORE-AM64x SoM.
Signed-off-by: Wadim Egorov
---
doc/board/phytec/index.rst | 1 +
doc/board/phytec/phycore-am64x.rst | 159
Add documentation for PHYTEC phyCORE-AM64x SoM.
Signed-off-by: Wadim Egorov
Reviewed-by: Dhruva Gole
---
doc/board/phytec/index.rst | 1 +
doc/board/phytec/phycore-am64x.rst | 159 +
2 files changed, 160 insertions(+)
create mode 100644
Add basic support for the phyCORE-AM64x.
v1: https://lists.denx.de/pipermail/u-boot/2024-January/544649.html
v2: https://lists.denx.de/pipermail/u-boot/2024-February/546757.html
v3:
- Update doc to use proper binary artifacts for HSFS devices
- Add Dhruva's Reviewed-by
Wadim Egorov (2):
On 27/02/24 7:33 pm, Sean Anderson wrote:
> Hi Danish,
>
> On 2/27/24 05:26, MD Danish Anwar wrote:
>> On 09/02/24 3:38 pm, MD Danish Anwar wrote:
>>> The fs-loader driver reads env storage_interface and uses it to load
>>> firmware file into memory using the medium set by env. Update the
Use proper binary artifact names for HSFS devices.
Do not use the *_unsigned binaries.
Signed-off-by: Wadim Egorov
---
doc/board/phytec/phycore-am62x.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/board/phytec/phycore-am62x.rst
Hi,
+ Tom
On 28/02/24 14:28, Wadim Egorov wrote:
Use proper binary artifact names for HSFS devices.
Do not use the *_unsigned binaries.
Signed-off-by: Wadim Egorov
---
Reviewed-by: Dhruva Gole
doc/board/phytec/phycore-am62x.rst | 6 +++---
1 file changed, 3 insertions(+), 3
On 28/02/2024 12:35, MD Danish Anwar wrote:
>
>
> On 28/02/24 3:30 pm, Roger Quadros wrote:
>>
>>
>> On 17/02/2024 14:26, MD Danish Anwar wrote:
>>> Add APIs to set a firmware_name to a rproc and boot the rproc with the
>>> same firmware.
>>>
>>> Clients can call rproc_set_firmware() API to
__efi_runtime_start/end are defined as c variables for arm7 only in
order to force the compiler emit relative references. However, defining
those within a section definition will do the same thing. On top of that
the v8 linker scripts define it as a symbol.
So let's remove the special sections
image_copy_start/end are defined as c variables in order to force the compiler
emit relative references. However, defining those within a section definition
will do the same thing.
So let's remove the special sections from the linker scripts, the
variable definitions from sections.c and define
commit 47bd65ef057f ("arm: make __rel_dyn_{start, end} compiler-generated")
were moving the __rel_dyn_start/end on c generated variables that were
injected in their own sections. The reason was that we needed relative
relocations for position independent code.
However, the linker documentation
On 17/02/2024 14:26, MD Danish Anwar wrote:
> Add APIs to set a firmware_name to a rproc and boot the rproc with the
> same firmware.
>
> Clients can call rproc_set_firmware() API to set firmware_name for a rproc
> whereas rproc_boot() will load the firmware set by rproc_set_firmware() to
> a
Add a new Kconfig symbol MDIO_TI_CPSW for the CPSW MDIO
driver and build it with proper DM support if enabled.
If MDIO_TI_CPSW is not enabled then we continue to
behave like before.
Clean up MDIO custom handling in am65-cpsw and use
dm_eth_phy_connect() to get the PHY.
Signed-off-by: Roger
Some platforms have bus level Reset controlled
by a GPIO line. If available then handle bus reset
via GPIO.
Signed-off-by: Roger Quadros
---
Changelog:
v2:
- Fix build if DM_GPIO not set
- Fix build on platforms that don't have
by using
---
include/phy.h | 7 +++
net/mdio-uclass.c
Hi,
This converts cpsw-mdio into a proper Driver Model
driver and introduces the new Config symbol CONFIG_MDIO_TI_CPSW.
It also cleans up the am65-cpsw driver so it porperly uses
the DM PHY interface.
It does not convert the legacy cpsw and keystone-net drivers.
Tested on SK-AM62, SK-AM64,
On Wed, 28 Feb 2024 at 13:11, Peter Robinson wrote:
>
> On Wed, 28 Feb 2024 at 10:58, Ilias Apalodimas
> wrote:
> >
> > The arm linker scripts had a mix of symbols and C defined variables in an
> > effort to emit relative references instead of absolute ones e.g [0].
> > This has led to confusion
Separate out the boot binaries built for J721E boards; J721E EVM and
J721E SK by using the common templates in k3-j721e-binman.dtsi.
Only the required boot binaries can be built from the templates in the
boards' respective -u-boot.dtsi file. FDTs and configurations are also
moved to the
Dynamically going through the subnode array and deleting leads to
templates being skipped from deletion when templates are consecutive in
the subnode list. Prevent this from happening by first parsing the DT
and then deleting the nodes.
Signed-off-by: Neha Malcom Francis
---
Add defconfig for J721E SK R5 and A72 configuration.
This includes and modifies the J721E EVM defconfigs:
j721e_evm_r5_defconfig -> j721e_sk_r5_defconfig
j721e_evm_a72_defconfig -> j721e_sk_a72_defconfig
Signed-off-by: Neha Malcom Francis
---
board/ti/j721e/MAINTAINERS | 2 ++
On 28/02/2024 11:02, MD Danish Anwar wrote:
>
> On 27/02/24 7:33 pm, Sean Anderson wrote:
>> Hi Danish,
>>
>> On 2/27/24 05:26, MD Danish Anwar wrote:
>>> On 09/02/24 3:38 pm, MD Danish Anwar wrote:
The fs-loader driver reads env storage_interface and uses it to load
firmware file
On Mon, 26 Feb 2024 at 23:24, Heinrich Schuchardt
wrote:
>
> EFI binaries should not contain sections that are both writable and
> executable. Separate the RX .text section from the RW .data section.
>
> We currently don't created relocation sections (.rel.*) for our EFI
> binaries. Anyway these
On 28/02/24 4:12 pm, Roger Quadros wrote:
>
>
> On 28/02/2024 12:35, MD Danish Anwar wrote:
>>
>>
>> On 28/02/24 3:30 pm, Roger Quadros wrote:
>>>
>>>
>>> On 17/02/2024 14:26, MD Danish Anwar wrote:
Add APIs to set a firmware_name to a rproc and boot the rproc with the
same
On 28/02/24 3:30 pm, Roger Quadros wrote:
>
>
> On 17/02/2024 14:26, MD Danish Anwar wrote:
>> Add APIs to set a firmware_name to a rproc and boot the rproc with the
>> same firmware.
>>
>> Clients can call rproc_set_firmware() API to set firmware_name for a rproc
>> whereas rproc_boot() will
commit 3d74a0977f514 ("ti: am335x: Remove unused linker script") removed
the linker script for the TI variant. This linker script doesn't seem to
do anything special and on top of that, has no definitions for the EFI
runtime sections.
So let's get rid of it and use the generic linker script which
commit 3ebd1cbc49f0 ("arm: make __bss_start and __bss_end__ compiler-generated")
and
commit f84a7b8f54db ("ARM: Fix __bss_start and __bss_end in linker scripts")
were moving the bss_start/end on c generated variables that were
injected in their own sections. The reason was that we needed relative
__efi_runtime_rel_start/end are defined as c variables for arm7 only in
order to force the compiler emit relative references. However, defining
those within a section definition will do the same thing. On top of that
the v8 linker scripts define it as a symbol.
So let's remove the special
The arm linker scripts had a mix of symbols and C defined variables in an
effort to emit relative references instead of absolute ones e.g [0].
This has led to confusion over the years, ending up with mixed section
definitions. Some sections being defined with overlays and different
definitions
From: Yang Xiwen
It is found that when DM is enabled, only generic init function is
called in .probe(). Baudrate is never honored. Add a function call
to .setbrg() when probing so that we can update the baudrate of the
serial device.
Signed-off-by: Yang Xiwen
---
Changes in v2:
- reverse if
On Wed, 28 Feb 2024 at 10:58, Ilias Apalodimas
wrote:
>
> The arm linker scripts had a mix of symbols and C defined variables in an
> effort to emit relative references instead of absolute ones e.g [0].
> This has led to confusion over the years, ending up with mixed section
> definitions. Some
This series does primarily three things:
1. Split out the common J721E defconfig for both EVM and SK
2. Cleanup k3-j721e-binman.dtsi to be SoC specific binman nodes
and -u-boot.dtsi files of the respective boards can pick and
edit according to their board.
On Mon, 26 Feb 2024 at 23:24, Heinrich Schuchardt
wrote:
>
> Change the alignment of the relocation code in EFI binaries to match page
> boundaries.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> v2:
> new patch
> ---
> arch/arm/lib/crt0_arm_efi.S | 4 ++--
> 1 file changed, 2
The FWU Multi Bank Update feature allows the platform to boot the
firmware images from one of the partitions(banks).
On the Developerbox, SCP-firmware running on the SCB(Cortex-M3)
passes the value of the boot index on the NOR flash.
Add a function to read the boot index value from the NOR flash.
On Tue, 27 Feb 2024 at 21:49, Marcel Ziswiler
wrote:
>
> Hi Apurva
>
> On Sat, 2024-02-24 at 01:51 +0530, Apurva Nandan wrote:
> > From: Dasnavis Sabiya
> >
> > Introduce the base dts files needed for u-boot or to augment the linux
> > dtbs for use in the u-boot-spl and u-boot binaries.
> >
> >
Hi Marcel,
On Tue, 27 Feb 2024 at 21:45, Marcel Ziswiler
wrote:
>
> Hi Apurva
>
> On Sat, 2024-02-24 at 01:51 +0530, Apurva Nandan wrote:
> > Hello Everyone!
> >
> > This series will introduce basic support (SD and UART) support for Texas
> > Instruments J784S4 EVM.
> >
> > The J784S4 SoC device
+ Shawn, Krzysztof, Conor
Hi Tom,
On Wed, 28 Feb 2024 at 18:40, Tom Rini wrote:
>
> On Wed, Feb 28, 2024 at 10:09:13AM +0300, Dan Carpenter wrote:
> > On Tue, Feb 27, 2024 at 04:40:01PM +0100, Sébastien Szymanski wrote:
> > > Commit 5d7a95f4 ("imx6ul/imx6ull: synchronise device trees with
>
On 28/02/2024 09:20, Sumit Garg wrote:
> Hi Paul,
>
> On Wed, 28 Feb 2024 at 03:08, Paul Barker
> wrote:
>>
>> Hi Sumit,
>>
>> On 22/02/2024 09:36, Sumit Garg wrote:
>>> Encourage SoC/board maintainers to migrate to using devicetree-rebasing
>>> subtree and maintain a regular sync with Linux
On 2/27/24 9:40 PM, Paul Barker wrote:
The RZ/G2L SMARC module is powered via a Renesas RAA215300 PMIC which
provides several voltage converters, a real time clock (RTC) and reset
control. A basic driver is implemented for this device so that we can
read, write and dump the PMIC registers.
The
On 2/27/24 9:40 PM, Paul Barker wrote:
Enable the appropriate PMIC driver as well as the `pmic` command.
Signed-off-by: Paul Barker
Reviewed-by: Marek Vasut
On 2/28/24 5:20 AM, Neha Malcom Francis wrote:
Add defconfig for J721E SK R5 and A72 configuration.
This includes and modifies the J721E EVM defconfigs:
j721e_evm_r5_defconfig -> j721e_sk_r5_defconfig
j721e_evm_a72_defconfig -> j721e_sk_a72_defconfig
Signed-off-by: Neha Malcom Francis
---
On Wed, Feb 28, 2024 at 07:44:42PM +0530, Sumit Garg wrote:
> + Shawn, Krzysztof, Conor
>
> Hi Tom,
>
> On Wed, 28 Feb 2024 at 18:40, Tom Rini wrote:
> >
> > On Wed, Feb 28, 2024 at 10:09:13AM +0300, Dan Carpenter wrote:
> > > On Tue, Feb 27, 2024 at 04:40:01PM +0100, Sébastien Szymanski wrote:
On Tue, 27 Feb 2024 at 23:53, Masahisa Kojima
wrote:
>
> The FWU Multi Bank Update feature allows the platform to boot the
> firmware images from one of the partitions(banks).
> On the Developerbox, SCP-firmware running on the SCB(Cortex-M3)
> passes the value of the boot index on the NOR flash.
Hi Apurva
On Wed, 2024-02-28 at 16:59 +0530, Apurva Nandan wrote:
> Hi Marcel,
>
> On 27/02/24 21:45, Marcel Ziswiler wrote:
> > Hi Apurva
> >
> > On Sat, 2024-02-24 at 01:51 +0530, Apurva Nandan wrote:
> > > Hello Everyone!
> > >
> > > This series will introduce basic support (SD and UART)
Hi Sumit
On Wed, 2024-02-28 at 11:04 +0530, Sumit Garg wrote:
> Hi Marcel,
>
> On Tue, 27 Feb 2024 at 21:45, Marcel Ziswiler
> wrote:
> >
> > Hi Apurva
> >
> > On Sat, 2024-02-24 at 01:51 +0530, Apurva Nandan wrote:
> > > Hello Everyone!
> > >
> > > This series will introduce basic support
Hi Marcel,
On 27/02/24 21:45, Marcel Ziswiler wrote:
Hi Apurva
On Sat, 2024-02-24 at 01:51 +0530, Apurva Nandan wrote:
Hello Everyone!
This series will introduce basic support (SD and UART) support for Texas
Instruments J784S4 EVM.
The J784S4 SoC device tree patches are taken from kernel
Hi Paul,
On Wed, 28 Feb 2024 at 03:08, Paul Barker wrote:
>
> Hi Sumit,
>
> On 22/02/2024 09:36, Sumit Garg wrote:
> > Encourage SoC/board maintainers to migrate to using devicetree-rebasing
> > subtree and maintain a regular sync with Linux kernel devicetree files
> > and bindings.
> >
> >
Add APIs to set a firmware_name to a rproc and boot the rproc with the
same firmware.
Clients can call rproc_set_firmware() API to set firmware_name for a rproc
whereas rproc_boot() will load the firmware set by rproc_set_firmware() to
a buffer by calling request_firmware_into_buf(). rproc_boot()
On Wed, Feb 28, 2024 at 10:09:13AM +0300, Dan Carpenter wrote:
> On Tue, Feb 27, 2024 at 04:40:01PM +0100, Sébastien Szymanski wrote:
> > Commit 5d7a95f4 ("imx6ul/imx6ull: synchronise device trees with
> > linux") removed the display timings from the board device tree whereas
> > they are
Hi Michal,
Thank you for the patch.
On Mon, Feb 26, 2024 at 04:54:13PM +0100, Michal Simek wrote:
> Remove undocumented DT property. Suggested solution was to apply quirk
> via glue logic driver that's why make no sense to have it listed in DT.
>
> Signed-off-by: Michal Simek
Reviewed-by:
On Tue, 13 Feb 2024 09:39:26 -0500, Tom Rini wrote:
> To make CI runs rely less on external servers, build a coreboot release
> from source and populate /opt/coreboot with the output.
>
>
Applied to u-boot/master, thanks!
--
Tom
The addition of the "SPI_NOR_OCTAL_READ" flag enables the use of 7Ch
4-byte octal output fast read command for IS25LX512M flash.
Signed-off-by: Tejas Bhumkar
---
drivers/mtd/spi/spi-nor-ids.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/spi/spi-nor-ids.c
On Tue, Feb 27, 2024 at 3:19 PM Adam Ford wrote:
>
> On Mon, Feb 26, 2024 at 2:05 AM Sumit Garg wrote:
> >
> > pcie_imx doesn't seem to share any useful code for iMX8 SoC and it is
> > tied to quite old port of pcie_designware driver from Linux which
> > suffices only iMX6 specific needs.
> >
>
Any thoughts on how to proceed with the issue mentioned about tinycrypt
warnings/checks?
Also, I'd like your advice - I was thinking for the larger patch that I'd
do it in two commits. The first would be the addition of the tinycrypt
files and the second is the actual changes and additions to
Hi Andrew
On 28/02/24 20:41, Andrew Davis wrote:
On 2/28/24 5:20 AM, Neha Malcom Francis wrote:
Add defconfig for J721E SK R5 and A72 configuration.
This includes and modifies the J721E EVM defconfigs:
j721e_evm_r5_defconfig -> j721e_sk_r5_defconfig
j721e_evm_a72_defconfig ->
On Wed, 31 Jan 2024 15:33:45 +0200, Roger Quadros wrote:
> MUX driver should autoprobe if the device tree has "idle-states"
> property. Drop using the custom "u-boot,mux-autoprobe" property
> in TI device trees.
>
> cheers,
> -roger
>
> [...]
Applied to u-boot/next, thanks!
--
Tom
On Wed, 28 Feb 2024 at 22:07, Tim Harvey wrote:
>
> On Tue, Feb 27, 2024 at 3:19 PM Adam Ford wrote:
> >
> > On Mon, Feb 26, 2024 at 2:05 AM Sumit Garg wrote:
> > >
> > > pcie_imx doesn't seem to share any useful code for iMX8 SoC and it is
> > > tied to quite old port of pcie_designware driver
On Thu, Feb 22, 2024 at 03:07:01PM -0800, Bob Wolff wrote:
> Peter,
> Thanks for helping lead me down the right path here.
>
> WRT tinycrypt, the license is quite permissive.
> https://github.com/intel/tinycrypt
>
> Also, I'd like your advice - I was thinking for the larger patch that I'd
> do
On Wed, 28 Feb 2024 at 20:50, Tom Rini wrote:
>
> On Wed, Feb 28, 2024 at 07:44:42PM +0530, Sumit Garg wrote:
> > + Shawn, Krzysztof, Conor
> >
> > Hi Tom,
> >
> > On Wed, 28 Feb 2024 at 18:40, Tom Rini wrote:
> > >
> > > On Wed, Feb 28, 2024 at 10:09:13AM +0300, Dan Carpenter wrote:
> > > > On
61 matches
Mail list logo
