Hi Frieder,
On 07.06.21 14:36, Frieder Schrempf wrote:
From: Frieder Schrempf
The Kontron SoM-Line i.MX8MM (N801x) by Kontron Electronics GmbH is a SoM
module with an i.MX8M-Mini SoC, 1/2/4 GB LPDDR4 RAM, SPI NOR, eMMC and PMIC.
The matching evaluation boards (Board-Line) have 2 Ethernets, US
>-Original Message-
>From: Ioana Ciornei
>Sent: Monday, April 26, 2021 6:31 PM
>To: Priyanka Jain
>Cc: u-boot@lists.denx.de; Florin Laurentiu Chiculita
>; Wasim Khan (OSS)
>; Ioana Ciornei
>Subject: [PATCH v2 3/4] board: fsl: lx2160ardb: add dts fixup function for RevC
>
>From: Florin
>-Original Message-
>From: Wasim Khan (OSS)
>Sent: Wednesday, May 5, 2021 8:33 PM
>To: Wasim Khan (OSS) ; Priyanka Jain
>; Varun Sethi
>Cc: u-boot@lists.denx.de
>Subject: RE: [PATCH] armv8: lx2160ardb: Add thermal node fixup for revc board
>
>Hi Priyanka,
>These changes have been teste
Hi Stefano,
> -Original Message-
> From: Jagan Teki
> Sent: Monday, April 19, 2021 12:17 PM
> To: Kuldeep Singh
> Cc: U-Boot-Denx
> Subject: [EXT] Re: [PATCH 2/2] spi: nxp_fspi: Implement errata workaround for
> LS1028A
>
> Caution: EXT Email
>
> On Mon, Mar 22, 2021 at 12:00 PM Kulde
Hi Tom,
The following changes since commit 9301a5cc99dd0c298e2f7fe2fa98a7287fcda772:
Merge https://source.denx.de/u-boot/custodians/u-boot-marvell (2021-06-15
08:23:04 -0400)
are available in the Git repository at:
g...@source.denx.de:u-boot/custodians/u-boot-riscv.git
for you to fetch c
Hi Tom,
Please pull u-boot-riscv/next into -next.
The following changes since commit 173c3bcd7dca47f1a8f7371a229681d20c7821cc:
Merge tag 'ti-v2021.10-next-v2' of
https://source.denx.de/u-boot/custodians/u-boot-ti into next (2021-06-13
07:48:22 -0400)
are available in the Git repository at:
On 2021/5/27 23:41, Tim Harvey wrote:
Greetings,
I support various iMX8M PCB's via board/gateworks/venice that are SOM
based and we are starting to add SOM's that have different IMX8M variant
SoC's on them which for various reasons are not binary compatible. I'm
very interested in coming u
Hi,
Michal Simek 於 2021年6月16日 週三 上午10:05寫道：
>
> Hi,
>
> On 6/16/21 5:26 PM, Zhengxun Li wrote:
> > Hi Sean,
> >
> > Thank you for your reply.
> >
> > Sean Anderson 於 2021年6月15日 週二 下午2:52寫道：
> >>
> >>
> >>
> >> On 6/15/21 1:21 PM, Zhengxun Li wrote:
> >> > Hi Michal,
> >> >
> >> > Sean Anderso
On Fri, Jun 4, 2021 at 2:25 PM Chris Packham wrote:
>
> Add support for 1.3GHz, 1.35GHz and 1.4GHz parts. This is based on
> equivalent code in Broadcom's LDK 5.0.6.
>
> Signed-off-by: Chris Packham
>
Hi Tom,
This seems to have fallen between the cracks. Are you able to take it
through one of y
On Thu, Jun 17, 2021 at 06:58:01AM +0800, Bin Meng wrote:
> Hi Leo,
>
> On Wed, Jun 16, 2021 at 10:59 PM Tom Rini wrote:
> >
> > On Wed, Jun 16, 2021 at 08:48:40PM +0800, Leo Liang wrote:
> >
> > > Hi Tom,
> > >
> > > Please pull u-boot-riscv/next into -next.
> > >
> > > The following changes on
On Wed, Jun 16, 2021 at 10:59:18AM -0400, Tom Rini wrote:
> On Wed, Jun 16, 2021 at 08:48:40PM +0800, Leo Liang wrote:
>
> > Hi Tom,
> >
> > Please pull u-boot-riscv/next into -next.
> >
> > The following changes on the "next" branch since commit
> > c4737cd594b5c4c47aff789fc53f7dd36ed03c94:
>
Hi Leo,
On Wed, Jun 16, 2021 at 10:59 PM Tom Rini wrote:
>
> On Wed, Jun 16, 2021 at 08:48:40PM +0800, Leo Liang wrote:
>
> > Hi Tom,
> >
> > Please pull u-boot-riscv/next into -next.
> >
> > The following changes on the "next" branch since commit
> > c4737cd594b5c4c47aff789fc53f7dd36ed03c94:
>
On Wed, Jun 16, 2021 at 12:08:00PM -0400, Tom Rini wrote:
> On Wed, Jun 16, 2021 at 09:34:27AM -0500, Alex G. wrote:
> > On 6/15/21 6:34 PM, AKASHI Takahiro wrote:
> > > A gentle ping.
> > > What is the current review status?
> > > Who will take care of this patch?
> >
> > Patchwork automatically
On Wednesday 16 June 2021 17:20:20 Tom Rini wrote:
> On Wed, Jun 16, 2021 at 11:16:32PM +0200, Pali Rohár wrote:
> > On Wednesday 16 June 2021 17:12:13 Tom Rini wrote:
> > > Wait, why is thumb disabled? That's something I'd really like to know
> > > why on as my first guess is there's units with o
On Wed, Jun 16, 2021 at 11:16:32PM +0200, Pali Rohár wrote:
> On Wednesday 16 June 2021 17:12:13 Tom Rini wrote:
> > Wait, why is thumb disabled? That's something I'd really like to know
> > why on as my first guess is there's units with old enough cores that
> > have some thumb errata maybe?
>
>
On Wednesday 16 June 2021 17:12:13 Tom Rini wrote:
> Wait, why is thumb disabled? That's something I'd really like to know
> why on as my first guess is there's units with old enough cores that
> have some thumb errata maybe?
IIRC we disabled at time when N900 support was merged into U-Boot (abou
On Wed, Jun 16, 2021 at 10:44:52PM +0200, Merlijn Wajer wrote:
> Hi Tom,
>
> On 16/06/2021 19:37, Tom Rini wrote:
>
> > Fixing those requires enabling of OF_CONTROL and this in turn means the
> > board must be migrated to DT, unless I am missing something. That's why
> > my
> > "
On Thu, Jun 17, 2021 at 12:03:15AM +0300, Ivaylo Dimitrov wrote:
> Hi Tom,
>
> On 16.06.21 г. 20:37 ч., Tom Rini wrote:
> > On Wed, Jun 16, 2021 at 08:25:28PM +0300, Ivaylo Dimitrov wrote:
> > > Hi,
> > >
> > > On 16.06.21 г. 15:13 ч., Tom Rini wrote:
> > > > On Wed, Jun 16, 2021 at 08:10:08AM -0
Hi Tom,
On 16.06.21 г. 20:37 ч., Tom Rini wrote:
On Wed, Jun 16, 2021 at 08:25:28PM +0300, Ivaylo Dimitrov wrote:
Hi,
On 16.06.21 г. 15:13 ч., Tom Rini wrote:
On Wed, Jun 16, 2021 at 08:10:08AM -0400, Tom Rini wrote:
On Wed, Jun 16, 2021 at 09:02:16AM +0300, Ivaylo Dimitrov wrote:
Hi,
On 1
- Move to gcc-11.1.0 builds from kernel.org for supported platforms and
LLVM-11 for those tests.
- grub-2.06 does not build with gcc-11.1.0 on riscv32 as seen here:
https://www.mail-archive.com/grub-devel@gnu.org/msg30736.html
so drop it.
- Update to newer Xtensa (gcc-9.2.0) and ARC (gcc-10.2
- gcc-11.0 proper is coming soon to kernel.org, use this snapshot for
now to see what fails.
- grub-2.04 does not build with gcc-11.0 due to -Werror, grub-2.06-rc1
fails on riscv32-linux as seen here:
https://www.mail-archive.com/grub-devel@gnu.org/msg30736.html
Cc: Heinrich Schuchardt
Cc:
On 6/16/21 11:38 AM, Aswath Govindraju wrote:
> Earlier, the region 0x701c to 0x701d was firewalled off because of
> a bug in SYSFW. In the v2021.05 release of SYSFW this bug has been fixed
> and this region can now be used for other allocations.
>
> Therefore, move TF-A's load address to
On Wed, Jun 16, 2021 at 08:25:28PM +0300, Ivaylo Dimitrov wrote:
> Hi,
>
> On 16.06.21 г. 15:13 ч., Tom Rini wrote:
> > On Wed, Jun 16, 2021 at 08:10:08AM -0400, Tom Rini wrote:
> > > On Wed, Jun 16, 2021 at 09:02:16AM +0300, Ivaylo Dimitrov wrote:
> > > > Hi,
> > > >
> > > > On 15.06.21 г. 15:34
Hi Suman,
On 16/06/21 10:49 pm, Suman Anna wrote:
> On 6/16/21 11:38 AM, Aswath Govindraju wrote:
>> The final 128KB in SRAM is reserved by default for DMSC-lite code and
>> secure proxy communication buffer. The memory region used for DMSC-lite
>> code can be optionally freed up by secure firmwar
Hi,
On 16.06.21 г. 15:13 ч., Tom Rini wrote:
On Wed, Jun 16, 2021 at 08:10:08AM -0400, Tom Rini wrote:
On Wed, Jun 16, 2021 at 09:02:16AM +0300, Ivaylo Dimitrov wrote:
Hi,
On 15.06.21 г. 15:34 ч., Tom Rini wrote:
On Tue, Jun 15, 2021 at 08:40:30AM +0300, Ivaylo Dimitrov wrote:
Hi,
On 22.05
Hi,
On 16.06.21 г. 15:10 ч., Tom Rini wrote:
On Wed, Jun 16, 2021 at 09:02:16AM +0300, Ivaylo Dimitrov wrote:
Hi,
On 15.06.21 г. 15:34 ч., Tom Rini wrote:
On Tue, Jun 15, 2021 at 08:40:30AM +0300, Ivaylo Dimitrov wrote:
Hi,
On 22.05.21 г. 0:36 ч., Pali Rohár wrote:
On Friday 21 May 2021 10
On 6/16/21 11:38 AM, Aswath Govindraju wrote:
> The final 128KB in SRAM is reserved by default for DMSC-lite code and
> secure proxy communication buffer. The memory region used for DMSC-lite
> code can be optionally freed up by secure firmware API[1]. However, the
> buffer for secure proxy communi
The final 128KB in SRAM is reserved by default for DMSC-lite code and
secure proxy communication buffer. The memory region used for DMSC-lite
code can be optionally freed up by secure firmware API[1]. However, the
buffer for secure proxy communication is not configurable. This default
hardware conf
Earlier, the region 0x701c to 0x701d was firewalled off because of
a bug in SYSFW. In the v2021.05 release of SYSFW this bug has been fixed
and this region can now be used for other allocations.
Therefore, move TF-A's load address to 0x701c and update its location
in the device tree no
The following series of patches,
- Update the location of TF-A
- Indicate reserved locations for DMSC code and secure proxy
changes since v1:
- Moved the load address of TF-A to 0x701c to account for future
increments in the size of TF-A
- Reworded the title of patch 2
Aswath Govindraju (2)
On Wed, Jun 16, 2021 at 09:34:27AM -0500, Alex G. wrote:
> On 6/15/21 6:34 PM, AKASHI Takahiro wrote:
> > A gentle ping.
> > What is the current review status?
> > Who will take care of this patch?
>
> Patchwork automatically delegates this to a maintainer [1], but anyone is
> welcome to comment a
Set default fdtfile names for unleashed and unmatched boards, as used
in the upstream Linux kernel. This allows sysboot command to find and
load appropriate dtb for the matching kernel from universal stock
Ubuntu RISC-V rootfs images based on fdtdir setting in extlinux.conf.
Signed-off-by: Dimitri
On Sat, 12 Jun 2021 21:16:38 +0200
Daniel Maslowski wrote:
Hi,
> I am trying to get an OLinuXino-A64 board with a SPI flash to work:
>
> - U-Boot in the SPI flash, with TF-A, SPL and DTB
> - Linux in the SPI flash, loaded and run by U-Boot
Please keep in mind that the latter is not really the
/custodians/u-boot-imx.git
tags/u-boot-imx-20210616
for you to fetch changes up to 40496ac3b71b9589a9149d423b81133eebce07b1:
mx7d: Add Storopack's SMEGW01 board (2021-06-09 13:34:38 +0200)
u-boot-imx-202
On Wed, Jun 16, 2021 at 08:48:40PM +0800, Leo Liang wrote:
> Hi Tom,
>
> Please pull u-boot-riscv/next into -next.
>
> The following changes on the "next" branch since commit
> c4737cd594b5c4c47aff789fc53f7dd36ed03c94:
>
> Merge tag 'xilinx-for-v2021.07-rc5' of
> https://source.denx.de/u-bo
On 6/15/21 6:34 PM, AKASHI Takahiro wrote:
A gentle ping.
What is the current review status?
Who will take care of this patch?
Patchwork automatically delegates this to a maintainer [1], but anyone
is welcome to comment and review.
Alex
[1]
https://patchwork.ozlabs.org/project/uboot/patch/
Am 16. Juni 2021 16:18:35 MESZ schrieb Peter Robinson :
>On Wed, Jun 16, 2021 at 3:11 PM Icenowy Zheng wrote:
>>
>> 在 2021-06-16星期三的 15:06 +0100，Peter Robinson写道：
>> > On Wed, Jun 16, 2021 at 1:20 PM Icenowy Zheng
>> > wrote:
>> > >
>> > > 在 2021-06-16星期三的 06:59 +0200，Heinrich Schuchardt写道：
>> >
On Wed, Jun 16, 2021 at 3:11 PM Icenowy Zheng wrote:
>
> 在 2021-06-16星期三的 15:06 +0100，Peter Robinson写道：
> > On Wed, Jun 16, 2021 at 1:20 PM Icenowy Zheng
> > wrote:
> > >
> > > 在 2021-06-16星期三的 06:59 +0200，Heinrich Schuchardt写道：
> > > > Am 15. Juni 2021 23:10:28 MESZ schrieb Icenowy Zheng
> > > >
在 2021-06-16星期三的 15:06 +0100，Peter Robinson写道：
> On Wed, Jun 16, 2021 at 1:20 PM Icenowy Zheng
> wrote:
> >
> > 在 2021-06-16星期三的 06:59 +0200，Heinrich Schuchardt写道：
> > > Am 15. Juni 2021 23:10:28 MESZ schrieb Icenowy Zheng
> > > :
> > > > Sometimes EFI GOP support may be not wanted (e.g. because
在 2021-06-16星期三的 15:20 +0200，Heinrich Schuchardt写道：
> Am 16. Juni 2021 14:19:41 MESZ schrieb Icenowy Zheng
> :
> > 在 2021-06-16星期三的 06:59 +0200，Heinrich Schuchardt写道：
> > > Am 15. Juni 2021 23:10:28 MESZ schrieb Icenowy Zheng
> > > :
> > > > Sometimes EFI GOP support may be not wanted (e.g. because
On Wed, Jun 16, 2021 at 1:20 PM Icenowy Zheng wrote:
>
> 在 2021-06-16星期三的 06:59 +0200，Heinrich Schuchardt写道：
> > Am 15. Juni 2021 23:10:28 MESZ schrieb Icenowy Zheng
> > :
> > > Sometimes EFI GOP support may be not wanted (e.g. because the
> > > operating
> > > system cannot operate well with it)
From: Camelia Groza
The RGMII ports on LS1043ARDB platforms require both RX and TX internal
delays to be enabled. The device tree reports only the TX ID because the
RX ID used to be enabled by default.
With the addition of RX ID support for the Realtek 8211F PHY driver in
commit e32e4d0f58cb ("n
Am 16. Juni 2021 14:19:41 MESZ schrieb Icenowy Zheng :
>在 2021-06-16星期三的 06:59 +0200，Heinrich Schuchardt写道：
>> Am 15. Juni 2021 23:10:28 MESZ schrieb Icenowy Zheng
>> :
>> > Sometimes EFI GOP support may be not wanted (e.g. because the
>> > operating
>> > system cannot operate well with it) even if
Hi Tom,
Please pull u-boot-riscv/next into -next.
The following changes on the "next" branch since commit
c4737cd594b5c4c47aff789fc53f7dd36ed03c94:
Merge tag 'xilinx-for-v2021.07-rc5' of
https://source.denx.de/u-boot/custodians/u-boot-microblaze (2021-06-11 08:29:34
-0400)
are available in
在 2021-06-16星期三的 06:59 +0200，Heinrich Schuchardt写道：
> Am 15. Juni 2021 23:10:28 MESZ schrieb Icenowy Zheng
> :
> > Sometimes EFI GOP support may be not wanted (e.g. because the
> > operating
> > system cannot operate well with it) even if video support in U-Boot
> > is
> > needed.
>
> Which OS has
From: Wasim Khan
NXP platforms expect bootcmd and mcinitcmd to be updated
as per boot source.
commit cbf77d201870f2d12227e2d95718a416b16ec98b breaks this
behaviour.
Revert commit cbf77d201870f2d12227e2d95718a416b16ec98b
Signed-off-by: Wasim Khan
---
arch/arm/cpu/armv8/fsl-layerscape/soc.c | 2
On Wed, Jun 16, 2021 at 08:10:08AM -0400, Tom Rini wrote:
> On Wed, Jun 16, 2021 at 09:02:16AM +0300, Ivaylo Dimitrov wrote:
> > Hi,
> >
> > On 15.06.21 г. 15:34 ч., Tom Rini wrote:
> > > On Tue, Jun 15, 2021 at 08:40:30AM +0300, Ivaylo Dimitrov wrote:
> > > > Hi,
> > > >
> > > > On 22.05.21 г. 0
On Wed, Jun 16, 2021 at 09:02:16AM +0300, Ivaylo Dimitrov wrote:
> Hi,
>
> On 15.06.21 г. 15:34 ч., Tom Rini wrote:
> > On Tue, Jun 15, 2021 at 08:40:30AM +0300, Ivaylo Dimitrov wrote:
> > > Hi,
> > >
> > > On 22.05.21 г. 0:36 ч., Pali Rohár wrote:
> > > > On Friday 21 May 2021 10:44:18 Tom Rini
On Wed, Jun 16, 2021 at 04:28:21PM +0800, Leo Liang wrote:
> On Wed, Jun 16, 2021 at 04:07:26PM +0800, Bin Meng wrote:
> > Hi Leo,
> >
> > On Wed, Jun 16, 2021 at 3:44 PM Leo Liang wrote:
> > >
> > > Hi Tom,
> > >
> > > Please pull u-boot-riscv/next into -next.
> > >
> > > The following changes o
On Wed, Jun 16, 2021 at 12:34 AM Dimitri John Ledkov
wrote:
>
nits: please remove the ending . in the commit title
> Set default fdtfile names for unleashed and unmatched boards, as used
> in the upstream Linux kernel. This allows sysboot command to find and
> load appropriate dtb for the matchi
On Wednesday 16 June 2021 06:52:30 Adam Ford wrote:
> Have you experimented with enabling LTO? I was successful in enabling
> LTO on an OMAP3530 and a DM3730 which really helped reduce the code
> size and I didn't notice any obvious regressions.
Nokia N900 is one of the board where LTO was tested
On Wed, Jun 16, 2021 at 6:26 AM Ivaylo Dimitrov
wrote:
>
> Hi,
>
> On 15.06.21 г. 15:34 ч., Tom Rini wrote:
> > On Tue, Jun 15, 2021 at 08:40:30AM +0300, Ivaylo Dimitrov wrote:
> >> Hi,
> >>
> >> On 22.05.21 г. 0:36 ч., Pali Rohár wrote:
> >>> On Friday 21 May 2021 10:44:18 Tom Rini wrote:
>
From: weichangzheng
This adds platform code and the device tree for the Phytium Pomelo Board.
The initial support comprises the UART and the PCIE.
Signed-off-by: weichangzheng
---
arch/arm/Kconfig | 8 ++
arch/arm/dts/Makefile| 1 +
arch/arm/dts/phytium-pomelo
Hi,
On 15.06.21 г. 15:34 ч., Tom Rini wrote:
On Tue, Jun 15, 2021 at 08:40:30AM +0300, Ivaylo Dimitrov wrote:
Hi,
On 22.05.21 г. 0:36 ч., Pali Rohár wrote:
On Friday 21 May 2021 10:44:18 Tom Rini wrote:
On Wed, May 19, 2021 at 11:52:03AM -0400, Tom Rini wrote:
On Wed, May 19, 2021 at 03:27:
Hi,
On 6/16/21 5:26 PM, Zhengxun Li wrote:
> Hi Sean,
>
> Thank you for your reply.
>
> Sean Anderson 於 2021年6月15日 週二 下午2:52寫道：
>>
>>
>>
>> On 6/15/21 1:21 PM, Zhengxun Li wrote:
>> > Hi Michal,
>> >
>> > Sean Anderson 於 2021年6月11日 週五 下午3:07寫道：
>> >>
>> >>
>> >>
>> >> On 6/11/21 11:10 A
On 6/11/21 5:10 PM, Zhengxun wrote:
> The Clocking Wizard IP supports clock circuits customized
> to your clocking requirements. The wizard support for
> dynamically reconfiguring the clocking primitives for
> Multiply, Divide, Phase Shift/Offset, or Duty Cycle.
>
> Limited by U-Boot clk uclass
On Wed, Jun 16, 2021 at 04:07:26PM +0800, Bin Meng wrote:
> Hi Leo,
>
> On Wed, Jun 16, 2021 at 3:44 PM Leo Liang wrote:
> >
> > Hi Tom,
> >
> > Please pull u-boot-riscv/next into -next.
> >
> > The following changes on the "next" branch since commit
> > c4737cd594b5c4c47aff789fc53f7dd36ed03c94:
On Wed, Jun 16, 2021 at 5:40 AM Sheep Sun wrote:
>
> Fix typo in clock-snapdragon.c
>
> Signed-off-by: Sheep Sun
> ---
>
> arch/arm/mach-snapdragon/clock-snapdragon.c | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm/mach-snapdragon/clock-snapdragon.c
Hi Leo,
On Wed, Jun 16, 2021 at 3:44 PM Leo Liang wrote:
>
> Hi Tom,
>
> Please pull u-boot-riscv/next into -next.
>
> The following changes on the "next" branch since commit
> c4737cd594b5c4c47aff789fc53f7dd36ed03c94:
>
> Merge tag 'xilinx-for-v2021.07-rc5' of
> https://source.denx.de/u-boot
Hi Tom,
Please pull u-boot-riscv/next into -next.
The following changes on the "next" branch since commit
c4737cd594b5c4c47aff789fc53f7dd36ed03c94:
Merge tag 'xilinx-for-v2021.07-rc5' of
https://source.denx.de/u-boot/custodians/u-boot-microblaze (2021-06-11 08:29:34
-0400)
are available in
Hi Sean,
Thank you for your reply.
Sean Anderson 於 2021年6月15日 週二 下午2:52寫道：
>
>
>
> On 6/15/21 1:21 PM, Zhengxun Li wrote:
> > Hi Michal,
> >
> > Sean Anderson 於 2021年6月11日 週五 下午3:07寫道：
> >>
> >>
> >>
> >> On 6/11/21 11:10 AM, Zhengxun wrote:
> >> > Add the devicetree binding for the x
61 matches
Mail list logo
