From: Stefan Roese <sr@denx.de>
To: Tom Rini <trini@konsulko.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Please pull u-boot-marvell/next
Date: Fri, 24 Mar 2023 15:49:07 +0100 [thread overview]
Message-ID: <94d2961e-e1bd-7156-0942-ca0f703dd8bb@denx.de> (raw)
Hi Tom,
please pull the following Marvell MVEBU related patches into next:
----------------------------------------------------------------
- mvebu: kwboot: Fix UART booting (Pali)
- mvebu: doc: Misc updates / fixes (Pali)
- kirkwood: Early init enhancements, e.g. for DEBUG UART (Pali & Tony)
- mvebu: Enable NAND flash for Thecus N2350 board (Tony)
- mvebu: Set common SPI flash default speed and mode (Tony)
----------------------------------------------------------------
Here the Azure build, without any issues:
https://dev.azure.com/sr0718/u-boot/_build/results?buildId=289&view=results
Thanks,
Stefan
The following changes since commit 884d626d8357853c012d535bf26c143bb7b5e6a5:
Merge branch '2023-03-22-assorted-minor-code-cleanups' into next
(2023-03-22 20:57:39 -0400)
are available in the Git repository at:
git@source.denx.de:u-boot/custodians/u-boot-marvell.git next
for you to fetch changes up to 66cf977716e7118819801482d0a9566661120e94:
tools: kwboot: Document information about NOR XIP (2023-03-24
13:13:57 +0100)
----------------------------------------------------------------
Pali Rohár (9):
doc/kwboot.1: Update Armada 38x BootROM bug description
arm: kirkwood: Move internal registers in arch_very_early_init()
function
ddr: marvell: a38x: Remove unused file seq_exec.h
tools: kwbimage: Fix invalid UART kwbimage v1 headersz
tools: kwboot: Fix invalid UART kwbimage v1 headersz
tools: kwboot: Fix inserting UART data checksum without -B option
tools: kwboot: Fix sending very small images
tools: kwboot: Workaround A38x BootROM bug for images with a gap
tools: kwboot: Document information about NOR XIP
Tony Dinh (3):
arm: mvebu: Enable NAND flash for Thecus N2350 board
arm: mvebu: Set common SPI flash default speed and mode
arm: kirkwood: Enable Debug UART for Zyxel NSA310S
arch/arm/mach-kirkwood/Kconfig | 2 ++
arch/arm/mach-kirkwood/Makefile | 1 +
arch/arm/mach-kirkwood/cpu.c | 3 --
arch/arm/mach-kirkwood/lowlevel.S | 12 +++++++
arch/arm/mach-mvebu/Kconfig | 10 ++++++
configs/n2350_defconfig | 3 ++
configs/nsa310s_defconfig | 4 +++
doc/kwboot.1 | 2 +-
drivers/ddr/marvell/a38x/ddr3_init.h | 1 -
drivers/ddr/marvell/a38x/seq_exec.h | 64
------------------------------------
tools/kwbimage.c | 10 ++++++
tools/kwboot.c | 42 ++++++++++++++++++++++-
12 files changed, 84 insertions(+), 70 deletions(-)
create mode 100644 arch/arm/mach-kirkwood/lowlevel.S
delete mode 100644 drivers/ddr/marvell/a38x/seq_exec.h
next reply other threads:[~2023-03-24 14:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 14:49 Stefan Roese [this message]
2023-03-25 13:39 ` Please pull u-boot-marvell/next Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2026-06-10 12:21 Stefan Roese
2026-06-10 19:59 ` Tom Rini
2023-03-30 8:22 Stefan Roese
2023-03-30 14:35 ` Tom Rini
2023-03-01 15:49 Stefan Roese
2023-03-01 19:54 ` Tom Rini
2022-09-20 6:59 Stefan Roese
2022-09-20 18:16 ` Tom Rini
2021-12-21 8:27 Stefan Roese
2021-12-23 1:55 ` Tom Rini
2021-12-18 13:51 Stefan Roese
2021-12-18 14:12 ` Tom Rini
2021-10-01 12:36 Stefan Roese
2021-10-01 13:16 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94d2961e-e1bd-7156-0942-ca0f703dd8bb@denx.de \
--to=sr@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox