* [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
@ 2026-10-22 7:34 Peng Fan
2026-10-22 14:42 ` Bradley Morgan
0 siblings, 1 reply; 23+ messages in thread
From: Peng Fan @ 2026-10-22 7:34 UTC (permalink / raw)
To: Tom Rini
Cc: u-boot, Bradley Morgan, Vincent Jardin, Bryan Brattlof,
Tomas Alvarez Vanoli
Hi Tom,
Please pull fsl-qoriq-for-2027-01-rc1
---------------------------------------------------
Drop various legacy powerpc support from Bradley
Make BASE_DISCOVER_AGENT it optional following spec
Various update for lx2160a serdes from Vincent
Check LSB_FIRST for fsl_espi
---------------------------------------------------
CI: https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq/-/pipelines/1672
Thanks
Peng
The following changes since commit e36b675ebc4c41f1f4187c46d363d581c371d538:
Merge patch series "rsa: fix rsa_gen_key_prop() buffer-sizing and zero-modulus handling" (2026-10-19 16:52:34 -0600)
are available in the Git repository at:
https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq.git tags/fsl-qoriq-for-2027-01-rc1
for you to fetch changes up to 20adeef914d05628583138733449596f17450b3d:
MAINTAINERS: powerpc: Add me as PowerPC maintainer (2026-10-22 07:32:56 +0800)
----------------------------------------------------------------
Bradley Morgan (26):
board: powerpc: Remove MPC8548CDS support
board: powerpc: Remove MPC837XERDB support
board: powerpc: Remove P2020RDB-PC support
board: powerpc: Remove P3041DS support
board: powerpc: Remove P4080DS support
board: powerpc: Remove P5040DS support
board: powerpc: Remove T1042D4RDB support
powerpc: mpc85xx: Remove P3041 support
powerpc: mpc85xx: Remove P4080 support
powerpc: mpc85xx: Remove P5040 support
powerpc: mpc83xx: Remove MPC837x support
powerpc: mpc85xx: Remove C29x support
powerpc: mpc85xx: Remove P1011 support
powerpc: mpc85xx: Remove P1023 support
powerpc: mpc85xx: Remove P1025 support
powerpc: mpc85xx: Remove MPC8536 support
powerpc: mpc85xx: Remove MPC8540 support
powerpc: mpc85xx: Remove MPC8560 support
powerpc: mpc85xx: Remove BSC9132 support
powerpc: mpc83xx: Remove MPC831x support
powerpc: mpc83xx: Remove MPC834x support
powerpc: mpc85xx: Remove P1024 support
powerpc: mpc85xx: Remove BSC9131 support
powerpc: mpc83xx: Remove MPC8309 support
powerpc: Remove MPC86xx support
MAINTAINERS: powerpc: Add me as PowerPC maintainer
Bryan Brattlof (1):
firmware: scmi: check if BASE_DISCOVER_AGENT is implemented
Tomas Alvarez Vanoli (1):
spi: fsl_espi: check user's LSB_FIRST
Vincent Jardin (18):
power: regulator: pmbus: check the device in the exported helpers
power: regulator: pmbus: read back the VOUT_COMMAND setpoint
test: dm: pmbus: test pmbus_regulator_read_vout_command()
board: nbxv3: VID handoff writes table value, no droop compensation
armv8: fsl-layerscape: icid: also find DWC3 nodes as fsl, ls1028a-dwc3
board: lx2160a: serdes: drop the split subcommand
board: lx2160a: serdes: rename serdes1:split to serdes1:100g4x25g
board: lx2160a: serdes: rename SPLIT_POLL_US to SRDS_POLL_US
board: lx2160a: serdes: move the SD1 halt and reset into helpers
board: lx2160a: serdes: set SD1 with a table
board: lx2160a: serdes: report unknown SD1 cases
board: lx2160a: serdes: no SD1 config once MC runs
board: lx2160a: serdes: add serdes1:2x40g
board: lx2160a: serdes: enter a SD1 mode through the mode it starts from
board: lx2160a: serdes: add serdes1:40g4x10g
board: lx2160a: serdes: add serdes1:100g4x10g
doc: lx2160a: document the sd1 hwconfig option
board: nbxv3: apply sd1 hwconfig before MC starts
MAINTAINERS | 3 +-
README | 2 +-
api/api_platform-powerpc.c | 2 +-
arch/Kconfig | 7 +-
arch/Kconfig.nxp | 9 +-
arch/arm/cpu/armv8/fsl-layerscape/doc/README.soc | 7 +
arch/arm/cpu/armv8/fsl-layerscape/icid.c | 18 +-
arch/powerpc/cpu/Makefile | 1 -
arch/powerpc/cpu/mpc83xx/Kconfig | 44 --
arch/powerpc/cpu/mpc83xx/cpu.c | 17 +-
arch/powerpc/cpu/mpc83xx/cpu_init.c | 24 -
arch/powerpc/cpu/mpc83xx/fdt.c | 47 +-
arch/powerpc/cpu/mpc83xx/hid/Kconfig | 4 +-
arch/powerpc/cpu/mpc83xx/hid/hid.h | 5 -
arch/powerpc/cpu/mpc83xx/hrcw/Kconfig | 82 +--
arch/powerpc/cpu/mpc83xx/initreg/Kconfig.lcrr | 6 +-
arch/powerpc/cpu/mpc83xx/initreg/Kconfig.spcr | 2 +-
arch/powerpc/cpu/mpc83xx/pci.c | 2 -
arch/powerpc/cpu/mpc83xx/spd_sdram.c | 4 +-
arch/powerpc/cpu/mpc83xx/speed.c | 112 +---
arch/powerpc/cpu/mpc83xx/traps.c | 1 -
arch/powerpc/cpu/mpc85xx/Kconfig | 443 +-------------
arch/powerpc/cpu/mpc85xx/Makefile | 14 -
arch/powerpc/cpu/mpc85xx/bsc9132_serdes.c | 101 ----
arch/powerpc/cpu/mpc85xx/c29x_serdes.c | 70 ---
arch/powerpc/cpu/mpc85xx/cmd_errata.c | 43 +-
arch/powerpc/cpu/mpc85xx/cpu.c | 17 -
arch/powerpc/cpu/mpc85xx/cpu_init.c | 49 +-
arch/powerpc/cpu/mpc85xx/fdt.c | 28 +-
arch/powerpc/cpu/mpc85xx/fsl_corenet_serdes.c | 665 ---------------------
arch/powerpc/cpu/mpc85xx/fsl_corenet_serdes.h | 4 -
arch/powerpc/cpu/mpc85xx/mpc8536_serdes.c | 250 --------
arch/powerpc/cpu/mpc85xx/mpc8548_serdes.c | 57 --
arch/powerpc/cpu/mpc85xx/p1023_serdes.c | 59 --
arch/powerpc/cpu/mpc85xx/p3041_ids.c | 112 ----
arch/powerpc/cpu/mpc85xx/p3041_serdes.c | 133 -----
arch/powerpc/cpu/mpc85xx/p4080_ids.c | 112 ----
arch/powerpc/cpu/mpc85xx/p4080_serdes.c | 80 ---
arch/powerpc/cpu/mpc85xx/p5040_ids.c | 111 ----
arch/powerpc/cpu/mpc85xx/p5040_serdes.c | 99 ---
arch/powerpc/cpu/mpc85xx/release.S | 23 +-
arch/powerpc/cpu/mpc85xx/speed.c | 6 +-
arch/powerpc/cpu/mpc8xxx/Makefile | 1 -
arch/powerpc/cpu/mpc8xxx/cpu.c | 23 +-
arch/powerpc/cpu/mpc8xxx/fdt.c | 8 +-
arch/powerpc/cpu/mpc8xxx/srio.c | 6 -
arch/powerpc/dts/Makefile | 7 -
arch/powerpc/dts/mpc8379erdb.dts | 153 -----
arch/powerpc/dts/mpc8548-post.dtsi | 36 --
arch/powerpc/dts/mpc8548.dtsi | 27 -
arch/powerpc/dts/mpc8548cds.dts | 29 -
arch/powerpc/dts/mpc8548cds_36b.dts | 29 -
arch/powerpc/dts/p2020rdb-pc.dts | 59 --
arch/powerpc/dts/p2020rdb-pc.dtsi | 50 --
arch/powerpc/dts/p2020rdb-pc_36b.dts | 59 --
arch/powerpc/dts/p3041.dtsi | 149 -----
arch/powerpc/dts/p3041ds.dts | 158 -----
arch/powerpc/dts/p3041si-post.dtsi | 43 --
arch/powerpc/dts/p4080.dtsi | 148 -----
arch/powerpc/dts/p4080ds.dts | 220 -------
arch/powerpc/dts/p4080si-post.dtsi | 62 --
arch/powerpc/dts/p5040.dtsi | 137 -----
arch/powerpc/dts/p5040ds.dts | 281 ---------
arch/powerpc/dts/p5040si-post.dtsi | 70 ---
arch/powerpc/dts/t1042d4rdb-u-boot.dtsi | 12 -
arch/powerpc/dts/t1042d4rdb.dts | 89 ---
arch/powerpc/dts/t104x.dtsi | 148 -----
arch/powerpc/include/asm/arch-mpc83xx/gpio.h | 4 +-
arch/powerpc/include/asm/arch-mpc83xx/soc.h | 37 +-
arch/powerpc/include/asm/config.h | 1 -
arch/powerpc/include/asm/config_mpc85xx.h | 56 +-
arch/powerpc/include/asm/fsl_law.h | 8 -
arch/powerpc/include/asm/fsl_lbc.h | 15 +-
arch/powerpc/include/asm/fsl_pci.h | 7 -
arch/powerpc/include/asm/fsl_secure_boot.h | 1 -
arch/powerpc/include/asm/fsl_serdes.h | 3 -
arch/powerpc/include/asm/global_data.h | 19 +-
arch/powerpc/include/asm/immap_83xx.h | 123 +---
arch/powerpc/include/asm/immap_85xx.h | 253 +-------
arch/powerpc/include/asm/mpc8349_pci.h | 165 -----
arch/powerpc/include/asm/mpc8xxx_spi.h | 5 +-
arch/powerpc/include/asm/ppc.h | 14 +-
arch/powerpc/include/asm/processor.h | 36 +-
arch/powerpc/lib/bdinfo.c | 2 +-
arch/powerpc/lib/bootm.c | 7 -
arch/powerpc/lib/ppccache.S | 4 +-
arch/powerpc/lib/stack.c | 2 +-
board/nxp/common/Makefile | 11 -
board/nxp/common/cds_pci_ft.c | 17 -
board/nxp/common/cds_via.c | 95 ---
board/nxp/common/ics307_clk.c | 149 -----
board/nxp/common/ics307_clk.h | 14 -
board/nxp/common/ngpixis.c | 247 --------
board/nxp/common/ngpixis.h | 60 --
board/nxp/common/sdhc_boot.c | 2 +-
board/nxp/lx2160a/eth_lx2160aqds.c | 4 +-
board/nxp/lx2160a/nbxv3/eth_nbxv3.c | 3 +
board/nxp/lx2160a/nbxv3/vid_handoff.c | 77 +--
board/nxp/lx2160a/serdes_split.c | 532 ++++++++++++++---
board/nxp/lx2160a/serdes_split.h | 16 +-
board/nxp/mpc837xerdb/Kconfig | 15 -
board/nxp/mpc837xerdb/MAINTAINERS | 6 -
board/nxp/mpc837xerdb/Makefile | 6 -
board/nxp/mpc837xerdb/README | 97 ---
board/nxp/mpc837xerdb/mpc837xerdb.c | 242 --------
board/nxp/mpc8548cds/Kconfig | 24 -
board/nxp/mpc8548cds/MAINTAINERS | 8 -
board/nxp/mpc8548cds/Makefile | 10 -
board/nxp/mpc8548cds/ddr.c | 51 --
board/nxp/mpc8548cds/law.c | 18 -
board/nxp/mpc8548cds/mpc8548cds.c | 170 ------
board/nxp/mpc8548cds/tlb.c | 87 ---
board/nxp/p1_p2_rdb_pc/Kconfig | 3 +-
board/nxp/p1_p2_rdb_pc/MAINTAINERS | 8 -
board/nxp/p1_p2_rdb_pc/README | 7 +-
board/nxp/p1_p2_rdb_pc/ddr.c | 68 ---
board/nxp/p1_p2_rdb_pc/p1_p2_rdb_pc.c | 2 -
board/nxp/t104xrdb/Kconfig | 12 -
board/nxp/t104xrdb/MAINTAINERS | 13 -
board/nxp/t104xrdb/Makefile | 13 -
board/nxp/t104xrdb/README | 386 ------------
board/nxp/t104xrdb/cpld.c | 116 ----
board/nxp/t104xrdb/cpld.h | 45 --
board/nxp/t104xrdb/ddr.c | 148 -----
board/nxp/t104xrdb/ddr.h | 56 --
board/nxp/t104xrdb/law.c | 31 -
board/nxp/t104xrdb/spl.c | 131 ----
board/nxp/t104xrdb/t1040_nand_rcw.cfg | 7 -
board/nxp/t104xrdb/t1040_sd_rcw.cfg | 7 -
board/nxp/t104xrdb/t1040_spi_rcw.cfg | 7 -
board/nxp/t104xrdb/t1040d4_nand_rcw.cfg | 7 -
board/nxp/t104xrdb/t1040d4_sd_rcw.cfg | 7 -
board/nxp/t104xrdb/t1040d4_spi_rcw.cfg | 7 -
board/nxp/t104xrdb/t1042_nand_rcw.cfg | 7 -
board/nxp/t104xrdb/t1042_pi_nand_rcw.cfg | 7 -
board/nxp/t104xrdb/t1042_pi_sd_rcw.cfg | 7 -
board/nxp/t104xrdb/t1042_pi_spi_rcw.cfg | 7 -
board/nxp/t104xrdb/t1042_sd_rcw.cfg | 7 -
board/nxp/t104xrdb/t1042_spi_rcw.cfg | 7 -
board/nxp/t104xrdb/t1042d4_nand_rcw.cfg | 7 -
board/nxp/t104xrdb/t1042d4_sd_rcw.cfg | 7 -
board/nxp/t104xrdb/t1042d4_spi_rcw.cfg | 7 -
board/nxp/t104xrdb/t104x_pbi.cfg | 36 --
board/nxp/t104xrdb/t104x_pbi_sb.cfg | 38 --
board/nxp/t104xrdb/t104xrdb.c | 159 -----
board/nxp/t104xrdb/t104xrdb.h | 11 -
board/nxp/t104xrdb/tlb.c | 132 ----
boot/Kconfig | 4 +-
common/board_r.c | 2 +-
configs/MPC837XERDB_defconfig | 193 ------
configs/MPC8548CDS_36BIT_defconfig | 108 ----
configs/MPC8548CDS_defconfig | 106 ----
configs/MPC8548CDS_legacy_defconfig | 106 ----
configs/P2020RDB-PC_36BIT_NAND_defconfig | 164 -----
configs/P2020RDB-PC_36BIT_SDCARD_defconfig | 145 -----
configs/P2020RDB-PC_36BIT_SPIFLASH_defconfig | 147 -----
configs/P2020RDB-PC_36BIT_defconfig | 125 ----
configs/P2020RDB-PC_NAND_defconfig | 162 -----
configs/P2020RDB-PC_SDCARD_defconfig | 142 -----
configs/P2020RDB-PC_SPIFLASH_defconfig | 145 -----
configs/P2020RDB-PC_defconfig | 123 ----
configs/T1042D4RDB_NAND_defconfig | 144 -----
configs/T1042D4RDB_SDCARD_defconfig | 138 -----
configs/T1042D4RDB_SPIFLASH_defconfig | 141 -----
configs/T1042D4RDB_defconfig | 114 ----
doc/README.fsl-hwconfig | 70 +++
doc/README.mpc83xxads | 97 ---
doc/README.mpc85xx-sd-spi-boot | 8 -
doc/README.mpc85xxcds | 225 -------
doc/README.pblimage | 6 +-
doc/README.sata | 68 ---
doc/README.srio-pcie-boot-corenet | 118 ----
doc/device-tree-bindings/clock/fsl,mpc83xx-clk.txt | 7 +-
doc/device-tree-bindings/cpu/fsl,mpc83xx.txt | 13 +-
.../gpio/fsl,mpc83xx-spisel-boot.txt | 4 +-
drivers/clk/mpc83xx_clk.c | 19 +-
drivers/clk/mpc83xx_clk.h | 30 +-
drivers/cpu/mpc83xx_cpu.c | 62 +-
drivers/cpu/mpc83xx_cpu.h | 44 --
drivers/crypto/fsl/jr.c | 14 +-
drivers/ddr/fsl/Kconfig | 8 +-
drivers/ddr/fsl/ctrl_regs.c | 1 -
drivers/dma/fsl_dma.c | 4 -
drivers/firmware/scmi/base.c | 5 +
drivers/gpio/mpc83xx_spisel_boot.c | 1 -
drivers/gpio/mpc8xxx_gpio.c | 1 -
drivers/mmc/Kconfig | 3 +-
drivers/net/Kconfig | 4 -
drivers/net/fm/Makefile | 6 +-
drivers/net/fm/fm.h | 4 -
drivers/net/fm/p1023.c | 72 ---
drivers/net/fm/p4080.c | 98 ---
drivers/net/fm/p5040.c | 106 ----
drivers/pci/Kconfig | 2 +-
drivers/pci/pci_auto.c | 14 -
drivers/pci/pcie_fsl.c | 23 -
drivers/power/regulator/pmbus_helper.c | 64 +-
drivers/qe/Kconfig | 3 +-
drivers/qe/qe.c | 1 -
drivers/ram/mpc83xx_sdram.c | 14 +-
drivers/spi/fsl_espi.c | 7 +-
drivers/usb/common/fsl-errata.c | 15 -
drivers/usb/host/Kconfig | 2 +-
env/Kconfig | 3 +-
include/asm-generic/u-boot.h | 2 +-
include/configs/MPC837XERDB.h | 218 -------
include/configs/MPC8548CDS.h | 312 ----------
include/configs/T104xRDB.h | 397 ------------
include/configs/p1_p2_rdb_pc.h | 21 -
include/dt-bindings/clk/mpc83xx-clk.h | 1 -
include/fsl_immap.h | 2 +-
include/fsl_sec.h | 3 -
include/mpc83xx.h | 319 +---------
include/pci_ids.h | 4 -
include/pmbus.h | 14 +
include/serial.h | 1 -
test/dm/pmbus.c | 41 ++
217 files changed, 860 insertions(+), 13052 deletions(-)
delete mode 100644 arch/powerpc/cpu/mpc85xx/bsc9132_serdes.c
delete mode 100644 arch/powerpc/cpu/mpc85xx/c29x_serdes.c
delete mode 100644 arch/powerpc/cpu/mpc85xx/mpc8536_serdes.c
delete mode 100644 arch/powerpc/cpu/mpc85xx/mpc8548_serdes.c
delete mode 100644 arch/powerpc/cpu/mpc85xx/p1023_serdes.c
delete mode 100644 arch/powerpc/cpu/mpc85xx/p3041_ids.c
delete mode 100644 arch/powerpc/cpu/mpc85xx/p3041_serdes.c
delete mode 100644 arch/powerpc/cpu/mpc85xx/p4080_ids.c
delete mode 100644 arch/powerpc/cpu/mpc85xx/p4080_serdes.c
delete mode 100644 arch/powerpc/cpu/mpc85xx/p5040_ids.c
delete mode 100644 arch/powerpc/cpu/mpc85xx/p5040_serdes.c
delete mode 100644 arch/powerpc/dts/mpc8379erdb.dts
delete mode 100644 arch/powerpc/dts/mpc8548-post.dtsi
delete mode 100644 arch/powerpc/dts/mpc8548.dtsi
delete mode 100644 arch/powerpc/dts/mpc8548cds.dts
delete mode 100644 arch/powerpc/dts/mpc8548cds_36b.dts
delete mode 100644 arch/powerpc/dts/p2020rdb-pc.dts
delete mode 100644 arch/powerpc/dts/p2020rdb-pc.dtsi
delete mode 100644 arch/powerpc/dts/p2020rdb-pc_36b.dts
delete mode 100644 arch/powerpc/dts/p3041.dtsi
delete mode 100644 arch/powerpc/dts/p3041ds.dts
delete mode 100644 arch/powerpc/dts/p3041si-post.dtsi
delete mode 100644 arch/powerpc/dts/p4080.dtsi
delete mode 100644 arch/powerpc/dts/p4080ds.dts
delete mode 100644 arch/powerpc/dts/p4080si-post.dtsi
delete mode 100644 arch/powerpc/dts/p5040.dtsi
delete mode 100644 arch/powerpc/dts/p5040ds.dts
delete mode 100644 arch/powerpc/dts/p5040si-post.dtsi
delete mode 100644 arch/powerpc/dts/t1042d4rdb-u-boot.dtsi
delete mode 100644 arch/powerpc/dts/t1042d4rdb.dts
delete mode 100644 arch/powerpc/dts/t104x.dtsi
delete mode 100644 arch/powerpc/include/asm/mpc8349_pci.h
delete mode 100644 board/nxp/common/cds_pci_ft.c
delete mode 100644 board/nxp/common/cds_via.c
delete mode 100644 board/nxp/common/ics307_clk.c
delete mode 100644 board/nxp/common/ics307_clk.h
delete mode 100644 board/nxp/common/ngpixis.c
delete mode 100644 board/nxp/common/ngpixis.h
delete mode 100644 board/nxp/mpc837xerdb/Kconfig
delete mode 100644 board/nxp/mpc837xerdb/MAINTAINERS
delete mode 100644 board/nxp/mpc837xerdb/Makefile
delete mode 100644 board/nxp/mpc837xerdb/README
delete mode 100644 board/nxp/mpc837xerdb/mpc837xerdb.c
delete mode 100644 board/nxp/mpc8548cds/Kconfig
delete mode 100644 board/nxp/mpc8548cds/MAINTAINERS
delete mode 100644 board/nxp/mpc8548cds/Makefile
delete mode 100644 board/nxp/mpc8548cds/ddr.c
delete mode 100644 board/nxp/mpc8548cds/law.c
delete mode 100644 board/nxp/mpc8548cds/mpc8548cds.c
delete mode 100644 board/nxp/mpc8548cds/tlb.c
delete mode 100644 board/nxp/t104xrdb/Kconfig
delete mode 100644 board/nxp/t104xrdb/MAINTAINERS
delete mode 100644 board/nxp/t104xrdb/Makefile
delete mode 100644 board/nxp/t104xrdb/README
delete mode 100644 board/nxp/t104xrdb/cpld.c
delete mode 100644 board/nxp/t104xrdb/cpld.h
delete mode 100644 board/nxp/t104xrdb/ddr.c
delete mode 100644 board/nxp/t104xrdb/ddr.h
delete mode 100644 board/nxp/t104xrdb/law.c
delete mode 100644 board/nxp/t104xrdb/spl.c
delete mode 100644 board/nxp/t104xrdb/t1040_nand_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1040_sd_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1040_spi_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1040d4_nand_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1040d4_sd_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1040d4_spi_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1042_nand_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1042_pi_nand_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1042_pi_sd_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1042_pi_spi_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1042_sd_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1042_spi_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1042d4_nand_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1042d4_sd_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t1042d4_spi_rcw.cfg
delete mode 100644 board/nxp/t104xrdb/t104x_pbi.cfg
delete mode 100644 board/nxp/t104xrdb/t104x_pbi_sb.cfg
delete mode 100644 board/nxp/t104xrdb/t104xrdb.c
delete mode 100644 board/nxp/t104xrdb/t104xrdb.h
delete mode 100644 board/nxp/t104xrdb/tlb.c
delete mode 100644 configs/MPC837XERDB_defconfig
delete mode 100644 configs/MPC8548CDS_36BIT_defconfig
delete mode 100644 configs/MPC8548CDS_defconfig
delete mode 100644 configs/MPC8548CDS_legacy_defconfig
delete mode 100644 configs/P2020RDB-PC_36BIT_NAND_defconfig
delete mode 100644 configs/P2020RDB-PC_36BIT_SDCARD_defconfig
delete mode 100644 configs/P2020RDB-PC_36BIT_SPIFLASH_defconfig
delete mode 100644 configs/P2020RDB-PC_36BIT_defconfig
delete mode 100644 configs/P2020RDB-PC_NAND_defconfig
delete mode 100644 configs/P2020RDB-PC_SDCARD_defconfig
delete mode 100644 configs/P2020RDB-PC_SPIFLASH_defconfig
delete mode 100644 configs/P2020RDB-PC_defconfig
delete mode 100644 configs/T1042D4RDB_NAND_defconfig
delete mode 100644 configs/T1042D4RDB_SDCARD_defconfig
delete mode 100644 configs/T1042D4RDB_SPIFLASH_defconfig
delete mode 100644 configs/T1042D4RDB_defconfig
delete mode 100644 doc/README.mpc83xxads
delete mode 100644 doc/README.mpc85xxcds
delete mode 100644 doc/README.sata
delete mode 100644 doc/README.srio-pcie-boot-corenet
delete mode 100644 drivers/net/fm/p1023.c
delete mode 100644 drivers/net/fm/p4080.c
delete mode 100644 drivers/net/fm/p5040.c
delete mode 100644 include/configs/MPC837XERDB.h
delete mode 100644 include/configs/MPC8548CDS.h
delete mode 100644 include/configs/T104xRDB.h
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-22 7:34 [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1 Peng Fan
@ 2026-10-22 14:42 ` Bradley Morgan
2026-10-26 8:43 ` Vincent Jardin
0 siblings, 1 reply; 23+ messages in thread
From: Bradley Morgan @ 2026-10-22 14:42 UTC (permalink / raw)
To: Peng Fan, Tom Rini
Cc: u-boot, Vincent Jardin, Bryan Brattlof, Tomas Alvarez Vanoli
On 22 October 2026 08:34:37 BST, Peng Fan <peng.fan@oss.nxp.com> wrote:
>Hi Tom,
>
>Please pull fsl-qoriq-for-2027-01-rc1
>
>---------------------------------------------------
>Drop various legacy powerpc support from Bradley
>Make BASE_DISCOVER_AGENT it optional following spec
>Various update for lx2160a serdes from Vincent
>Check LSB_FIRST for fsl_espi
>---------------------------------------------------
>
>CI: https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq/-/pipelines/1672
>
>Thanks
>Peng
>
>The following changes since commit
>e36b675ebc4c41f1f4187c46d363d581c371d538:
>
> Merge patch series "rsa: fix rsa_gen_key_prop() buffer-sizing and zero-modulus handling" (2026-10-19 16:52:34 -0600)
>
>are available in the Git repository at:
>
> https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq.git tags/fsl-qoriq-for-2027-01-rc1
>
>for you to fetch changes up to 20adeef914d05628583138733449596f17450b3d:
>
> MAINTAINERS: powerpc: Add me as PowerPC maintainer (2026-10-22 07:32:56 +0800)
>
>----------------------------------------------------------------
>Bradley Morgan (26):
> board: powerpc: Remove MPC8548CDS support
> board: powerpc: Remove MPC837XERDB support
Sinan (the maintainer) NAKed this ^
> board: powerpc: Remove P2020RDB-PC support
> board: powerpc: Remove P3041DS support
> board: powerpc: Remove P4080DS support
> board: powerpc: Remove P5040DS support
> board: powerpc: Remove T1042D4RDB support
> powerpc: mpc85xx: Remove P3041 support
> powerpc: mpc85xx: Remove P4080 support
> powerpc: mpc85xx: Remove P5040 support
> powerpc: mpc83xx: Remove MPC837x support
> powerpc: mpc85xx: Remove C29x support
> powerpc: mpc85xx: Remove P1011 support
> powerpc: mpc85xx: Remove P1023 support
> powerpc: mpc85xx: Remove P1025 support
> powerpc: mpc85xx: Remove MPC8536 support
> powerpc: mpc85xx: Remove MPC8540 support
> powerpc: mpc85xx: Remove MPC8560 support
> powerpc: mpc85xx: Remove BSC9132 support
> powerpc: mpc83xx: Remove MPC831x support
> powerpc: mpc83xx: Remove MPC834x support
> powerpc: mpc85xx: Remove P1024 support
> powerpc: mpc85xx: Remove BSC9131 support
> powerpc: mpc83xx: Remove MPC8309 support
> powerpc: Remove MPC86xx support
> MAINTAINERS: powerpc: Add me as PowerPC maintainer
>
>Bryan Brattlof (1):
> firmware: scmi: check if BASE_DISCOVER_AGENT is implemented
>
>Tomas Alvarez Vanoli (1):
> spi: fsl_espi: check user's LSB_FIRST
>
>Vincent Jardin (18):
> power: regulator: pmbus: check the device in the exported helpers
> power: regulator: pmbus: read back the VOUT_COMMAND setpoint
> test: dm: pmbus: test pmbus_regulator_read_vout_command()
> board: nbxv3: VID handoff writes table value, no droop compensation
> armv8: fsl-layerscape: icid: also find DWC3 nodes as fsl, ls1028a-dwc3
> board: lx2160a: serdes: drop the split subcommand
> board: lx2160a: serdes: rename serdes1:split to serdes1:100g4x25g
> board: lx2160a: serdes: rename SPLIT_POLL_US to SRDS_POLL_US
> board: lx2160a: serdes: move the SD1 halt and reset into helpers
> board: lx2160a: serdes: set SD1 with a table
> board: lx2160a: serdes: report unknown SD1 cases
> board: lx2160a: serdes: no SD1 config once MC runs
> board: lx2160a: serdes: add serdes1:2x40g
> board: lx2160a: serdes: enter a SD1 mode through the mode it starts from
> board: lx2160a: serdes: add serdes1:40g4x10g
> board: lx2160a: serdes: add serdes1:100g4x10g
> doc: lx2160a: document the sd1 hwconfig option
> board: nbxv3: apply sd1 hwconfig before MC starts
>
> MAINTAINERS | 3 +-
> README | 2 +-
> api/api_platform-powerpc.c | 2 +-
> arch/Kconfig | 7 +-
> arch/Kconfig.nxp | 9 +-
> arch/arm/cpu/armv8/fsl-layerscape/doc/README.soc | 7 +
> arch/arm/cpu/armv8/fsl-layerscape/icid.c | 18 +-
> arch/powerpc/cpu/Makefile | 1 -
> arch/powerpc/cpu/mpc83xx/Kconfig | 44 --
> arch/powerpc/cpu/mpc83xx/cpu.c | 17 +-
> arch/powerpc/cpu/mpc83xx/cpu_init.c | 24 -
> arch/powerpc/cpu/mpc83xx/fdt.c | 47 +-
> arch/powerpc/cpu/mpc83xx/hid/Kconfig | 4 +-
> arch/powerpc/cpu/mpc83xx/hid/hid.h | 5 -
> arch/powerpc/cpu/mpc83xx/hrcw/Kconfig | 82 +--
> arch/powerpc/cpu/mpc83xx/initreg/Kconfig.lcrr | 6 +-
> arch/powerpc/cpu/mpc83xx/initreg/Kconfig.spcr | 2 +-
> arch/powerpc/cpu/mpc83xx/pci.c | 2 -
> arch/powerpc/cpu/mpc83xx/spd_sdram.c | 4 +-
> arch/powerpc/cpu/mpc83xx/speed.c | 112 +---
> arch/powerpc/cpu/mpc83xx/traps.c | 1 -
> arch/powerpc/cpu/mpc85xx/Kconfig | 443 +-------------
> arch/powerpc/cpu/mpc85xx/Makefile | 14 -
> arch/powerpc/cpu/mpc85xx/bsc9132_serdes.c | 101 ----
> arch/powerpc/cpu/mpc85xx/c29x_serdes.c | 70 ---
> arch/powerpc/cpu/mpc85xx/cmd_errata.c | 43 +-
> arch/powerpc/cpu/mpc85xx/cpu.c | 17 -
> arch/powerpc/cpu/mpc85xx/cpu_init.c | 49 +-
> arch/powerpc/cpu/mpc85xx/fdt.c | 28 +-
> arch/powerpc/cpu/mpc85xx/fsl_corenet_serdes.c | 665
> ---------------------
> arch/powerpc/cpu/mpc85xx/fsl_corenet_serdes.h | 4 -
> arch/powerpc/cpu/mpc85xx/mpc8536_serdes.c | 250 --------
> arch/powerpc/cpu/mpc85xx/mpc8548_serdes.c | 57 --
> arch/powerpc/cpu/mpc85xx/p1023_serdes.c | 59 --
> arch/powerpc/cpu/mpc85xx/p3041_ids.c | 112 ----
> arch/powerpc/cpu/mpc85xx/p3041_serdes.c | 133 -----
> arch/powerpc/cpu/mpc85xx/p4080_ids.c | 112 ----
> arch/powerpc/cpu/mpc85xx/p4080_serdes.c | 80 ---
> arch/powerpc/cpu/mpc85xx/p5040_ids.c | 111 ----
> arch/powerpc/cpu/mpc85xx/p5040_serdes.c | 99 ---
> arch/powerpc/cpu/mpc85xx/release.S | 23 +-
> arch/powerpc/cpu/mpc85xx/speed.c | 6 +-
> arch/powerpc/cpu/mpc8xxx/Makefile | 1 -
> arch/powerpc/cpu/mpc8xxx/cpu.c | 23 +-
> arch/powerpc/cpu/mpc8xxx/fdt.c | 8 +-
> arch/powerpc/cpu/mpc8xxx/srio.c | 6 -
> arch/powerpc/dts/Makefile | 7 -
> arch/powerpc/dts/mpc8379erdb.dts | 153 -----
> arch/powerpc/dts/mpc8548-post.dtsi | 36 --
> arch/powerpc/dts/mpc8548.dtsi | 27 -
> arch/powerpc/dts/mpc8548cds.dts | 29 -
> arch/powerpc/dts/mpc8548cds_36b.dts | 29 -
> arch/powerpc/dts/p2020rdb-pc.dts | 59 --
> arch/powerpc/dts/p2020rdb-pc.dtsi | 50 --
> arch/powerpc/dts/p2020rdb-pc_36b.dts | 59 --
> arch/powerpc/dts/p3041.dtsi | 149 -----
> arch/powerpc/dts/p3041ds.dts | 158 -----
> arch/powerpc/dts/p3041si-post.dtsi | 43 --
> arch/powerpc/dts/p4080.dtsi | 148 -----
> arch/powerpc/dts/p4080ds.dts | 220 -------
> arch/powerpc/dts/p4080si-post.dtsi | 62 --
> arch/powerpc/dts/p5040.dtsi | 137 -----
> arch/powerpc/dts/p5040ds.dts | 281 ---------
> arch/powerpc/dts/p5040si-post.dtsi | 70 ---
> arch/powerpc/dts/t1042d4rdb-u-boot.dtsi | 12 -
> arch/powerpc/dts/t1042d4rdb.dts | 89 ---
> arch/powerpc/dts/t104x.dtsi | 148 -----
> arch/powerpc/include/asm/arch-mpc83xx/gpio.h | 4 +-
> arch/powerpc/include/asm/arch-mpc83xx/soc.h | 37 +-
> arch/powerpc/include/asm/config.h | 1 -
> arch/powerpc/include/asm/config_mpc85xx.h | 56 +-
> arch/powerpc/include/asm/fsl_law.h | 8 -
> arch/powerpc/include/asm/fsl_lbc.h | 15 +-
> arch/powerpc/include/asm/fsl_pci.h | 7 -
> arch/powerpc/include/asm/fsl_secure_boot.h | 1 -
> arch/powerpc/include/asm/fsl_serdes.h | 3 -
> arch/powerpc/include/asm/global_data.h | 19 +-
> arch/powerpc/include/asm/immap_83xx.h | 123 +---
> arch/powerpc/include/asm/immap_85xx.h | 253 +-------
> arch/powerpc/include/asm/mpc8349_pci.h | 165 -----
> arch/powerpc/include/asm/mpc8xxx_spi.h | 5 +-
> arch/powerpc/include/asm/ppc.h | 14 +-
> arch/powerpc/include/asm/processor.h | 36 +-
> arch/powerpc/lib/bdinfo.c | 2 +-
> arch/powerpc/lib/bootm.c | 7 -
> arch/powerpc/lib/ppccache.S | 4 +-
> arch/powerpc/lib/stack.c | 2 +-
> board/nxp/common/Makefile | 11 -
> board/nxp/common/cds_pci_ft.c | 17 -
> board/nxp/common/cds_via.c | 95 ---
> board/nxp/common/ics307_clk.c | 149 -----
> board/nxp/common/ics307_clk.h | 14 -
> board/nxp/common/ngpixis.c | 247 --------
> board/nxp/common/ngpixis.h | 60 --
> board/nxp/common/sdhc_boot.c | 2 +-
> board/nxp/lx2160a/eth_lx2160aqds.c | 4 +-
> board/nxp/lx2160a/nbxv3/eth_nbxv3.c | 3 +
> board/nxp/lx2160a/nbxv3/vid_handoff.c | 77 +--
> board/nxp/lx2160a/serdes_split.c | 532
> ++++++++++++++---
> board/nxp/lx2160a/serdes_split.h | 16 +-
> board/nxp/mpc837xerdb/Kconfig | 15 -
> board/nxp/mpc837xerdb/MAINTAINERS | 6 -
> board/nxp/mpc837xerdb/Makefile | 6 -
> board/nxp/mpc837xerdb/README | 97 ---
> board/nxp/mpc837xerdb/mpc837xerdb.c | 242 --------
> board/nxp/mpc8548cds/Kconfig | 24 -
> board/nxp/mpc8548cds/MAINTAINERS | 8 -
> board/nxp/mpc8548cds/Makefile | 10 -
> board/nxp/mpc8548cds/ddr.c | 51 --
> board/nxp/mpc8548cds/law.c | 18 -
> board/nxp/mpc8548cds/mpc8548cds.c | 170 ------
> board/nxp/mpc8548cds/tlb.c | 87 ---
> board/nxp/p1_p2_rdb_pc/Kconfig | 3 +-
> board/nxp/p1_p2_rdb_pc/MAINTAINERS | 8 -
> board/nxp/p1_p2_rdb_pc/README | 7 +-
> board/nxp/p1_p2_rdb_pc/ddr.c | 68 ---
> board/nxp/p1_p2_rdb_pc/p1_p2_rdb_pc.c | 2 -
> board/nxp/t104xrdb/Kconfig | 12 -
> board/nxp/t104xrdb/MAINTAINERS | 13 -
> board/nxp/t104xrdb/Makefile | 13 -
> board/nxp/t104xrdb/README | 386 ------------
> board/nxp/t104xrdb/cpld.c | 116 ----
> board/nxp/t104xrdb/cpld.h | 45 --
> board/nxp/t104xrdb/ddr.c | 148 -----
> board/nxp/t104xrdb/ddr.h | 56 --
> board/nxp/t104xrdb/law.c | 31 -
> board/nxp/t104xrdb/spl.c | 131 ----
> board/nxp/t104xrdb/t1040_nand_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1040_sd_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1040_spi_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1040d4_nand_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1040d4_sd_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1040d4_spi_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1042_nand_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1042_pi_nand_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1042_pi_sd_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1042_pi_spi_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1042_sd_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1042_spi_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1042d4_nand_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1042d4_sd_rcw.cfg | 7 -
> board/nxp/t104xrdb/t1042d4_spi_rcw.cfg | 7 -
> board/nxp/t104xrdb/t104x_pbi.cfg | 36 --
> board/nxp/t104xrdb/t104x_pbi_sb.cfg | 38 --
> board/nxp/t104xrdb/t104xrdb.c | 159 -----
> board/nxp/t104xrdb/t104xrdb.h | 11 -
> board/nxp/t104xrdb/tlb.c | 132 ----
> boot/Kconfig | 4 +-
> common/board_r.c | 2 +-
> configs/MPC837XERDB_defconfig | 193 ------
> configs/MPC8548CDS_36BIT_defconfig | 108 ----
> configs/MPC8548CDS_defconfig | 106 ----
> configs/MPC8548CDS_legacy_defconfig | 106 ----
> configs/P2020RDB-PC_36BIT_NAND_defconfig | 164 -----
> configs/P2020RDB-PC_36BIT_SDCARD_defconfig | 145 -----
> configs/P2020RDB-PC_36BIT_SPIFLASH_defconfig | 147 -----
> configs/P2020RDB-PC_36BIT_defconfig | 125 ----
> configs/P2020RDB-PC_NAND_defconfig | 162 -----
> configs/P2020RDB-PC_SDCARD_defconfig | 142 -----
> configs/P2020RDB-PC_SPIFLASH_defconfig | 145 -----
> configs/P2020RDB-PC_defconfig | 123 ----
> configs/T1042D4RDB_NAND_defconfig | 144 -----
> configs/T1042D4RDB_SDCARD_defconfig | 138 -----
> configs/T1042D4RDB_SPIFLASH_defconfig | 141 -----
> configs/T1042D4RDB_defconfig | 114 ----
> doc/README.fsl-hwconfig | 70 +++
> doc/README.mpc83xxads | 97 ---
> doc/README.mpc85xx-sd-spi-boot | 8 -
> doc/README.mpc85xxcds | 225 -------
> doc/README.pblimage | 6 +-
> doc/README.sata | 68 ---
> doc/README.srio-pcie-boot-corenet | 118 ----
> doc/device-tree-bindings/clock/fsl,mpc83xx-clk.txt | 7 +-
> doc/device-tree-bindings/cpu/fsl,mpc83xx.txt | 13 +-
> .../gpio/fsl,mpc83xx-spisel-boot.txt | 4 +-
> drivers/clk/mpc83xx_clk.c | 19 +-
> drivers/clk/mpc83xx_clk.h | 30 +-
> drivers/cpu/mpc83xx_cpu.c | 62 +-
> drivers/cpu/mpc83xx_cpu.h | 44 --
> drivers/crypto/fsl/jr.c | 14 +-
> drivers/ddr/fsl/Kconfig | 8 +-
> drivers/ddr/fsl/ctrl_regs.c | 1 -
> drivers/dma/fsl_dma.c | 4 -
> drivers/firmware/scmi/base.c | 5 +
> drivers/gpio/mpc83xx_spisel_boot.c | 1 -
> drivers/gpio/mpc8xxx_gpio.c | 1 -
> drivers/mmc/Kconfig | 3 +-
> drivers/net/Kconfig | 4 -
> drivers/net/fm/Makefile | 6 +-
> drivers/net/fm/fm.h | 4 -
> drivers/net/fm/p1023.c | 72 ---
> drivers/net/fm/p4080.c | 98 ---
> drivers/net/fm/p5040.c | 106 ----
> drivers/pci/Kconfig | 2 +-
> drivers/pci/pci_auto.c | 14 -
> drivers/pci/pcie_fsl.c | 23 -
> drivers/power/regulator/pmbus_helper.c | 64 +-
> drivers/qe/Kconfig | 3 +-
> drivers/qe/qe.c | 1 -
> drivers/ram/mpc83xx_sdram.c | 14 +-
> drivers/spi/fsl_espi.c | 7 +-
> drivers/usb/common/fsl-errata.c | 15 -
> drivers/usb/host/Kconfig | 2 +-
> env/Kconfig | 3 +-
> include/asm-generic/u-boot.h | 2 +-
> include/configs/MPC837XERDB.h | 218 -------
> include/configs/MPC8548CDS.h | 312 ----------
> include/configs/T104xRDB.h | 397 ------------
> include/configs/p1_p2_rdb_pc.h | 21 -
> include/dt-bindings/clk/mpc83xx-clk.h | 1 -
> include/fsl_immap.h | 2 +-
> include/fsl_sec.h | 3 -
> include/mpc83xx.h | 319 +---------
> include/pci_ids.h | 4 -
> include/pmbus.h | 14 +
> include/serial.h | 1 -
> test/dm/pmbus.c | 41 ++
> 217 files changed, 860 insertions(+), 13052 deletions(-)
> delete mode 100644 arch/powerpc/cpu/mpc85xx/bsc9132_serdes.c
> delete mode 100644 arch/powerpc/cpu/mpc85xx/c29x_serdes.c
> delete mode 100644 arch/powerpc/cpu/mpc85xx/mpc8536_serdes.c
> delete mode 100644 arch/powerpc/cpu/mpc85xx/mpc8548_serdes.c
> delete mode 100644 arch/powerpc/cpu/mpc85xx/p1023_serdes.c
> delete mode 100644 arch/powerpc/cpu/mpc85xx/p3041_ids.c
> delete mode 100644 arch/powerpc/cpu/mpc85xx/p3041_serdes.c
> delete mode 100644 arch/powerpc/cpu/mpc85xx/p4080_ids.c
> delete mode 100644 arch/powerpc/cpu/mpc85xx/p4080_serdes.c
> delete mode 100644 arch/powerpc/cpu/mpc85xx/p5040_ids.c
> delete mode 100644 arch/powerpc/cpu/mpc85xx/p5040_serdes.c
> delete mode 100644 arch/powerpc/dts/mpc8379erdb.dts
> delete mode 100644 arch/powerpc/dts/mpc8548-post.dtsi
> delete mode 100644 arch/powerpc/dts/mpc8548.dtsi
> delete mode 100644 arch/powerpc/dts/mpc8548cds.dts
> delete mode 100644 arch/powerpc/dts/mpc8548cds_36b.dts
> delete mode 100644 arch/powerpc/dts/p2020rdb-pc.dts
> delete mode 100644 arch/powerpc/dts/p2020rdb-pc.dtsi
> delete mode 100644 arch/powerpc/dts/p2020rdb-pc_36b.dts
> delete mode 100644 arch/powerpc/dts/p3041.dtsi
> delete mode 100644 arch/powerpc/dts/p3041ds.dts
> delete mode 100644 arch/powerpc/dts/p3041si-post.dtsi
> delete mode 100644 arch/powerpc/dts/p4080.dtsi
> delete mode 100644 arch/powerpc/dts/p4080ds.dts
> delete mode 100644 arch/powerpc/dts/p4080si-post.dtsi
> delete mode 100644 arch/powerpc/dts/p5040.dtsi
> delete mode 100644 arch/powerpc/dts/p5040ds.dts
> delete mode 100644 arch/powerpc/dts/p5040si-post.dtsi
> delete mode 100644 arch/powerpc/dts/t1042d4rdb-u-boot.dtsi
> delete mode 100644 arch/powerpc/dts/t1042d4rdb.dts
> delete mode 100644 arch/powerpc/dts/t104x.dtsi
> delete mode 100644 arch/powerpc/include/asm/mpc8349_pci.h
> delete mode 100644 board/nxp/common/cds_pci_ft.c
> delete mode 100644 board/nxp/common/cds_via.c
> delete mode 100644 board/nxp/common/ics307_clk.c
> delete mode 100644 board/nxp/common/ics307_clk.h
> delete mode 100644 board/nxp/common/ngpixis.c
> delete mode 100644 board/nxp/common/ngpixis.h
> delete mode 100644 board/nxp/mpc837xerdb/Kconfig
> delete mode 100644 board/nxp/mpc837xerdb/MAINTAINERS
> delete mode 100644 board/nxp/mpc837xerdb/Makefile
> delete mode 100644 board/nxp/mpc837xerdb/README
> delete mode 100644 board/nxp/mpc837xerdb/mpc837xerdb.c
> delete mode 100644 board/nxp/mpc8548cds/Kconfig
> delete mode 100644 board/nxp/mpc8548cds/MAINTAINERS
> delete mode 100644 board/nxp/mpc8548cds/Makefile
> delete mode 100644 board/nxp/mpc8548cds/ddr.c
> delete mode 100644 board/nxp/mpc8548cds/law.c
> delete mode 100644 board/nxp/mpc8548cds/mpc8548cds.c
> delete mode 100644 board/nxp/mpc8548cds/tlb.c
> delete mode 100644 board/nxp/t104xrdb/Kconfig
> delete mode 100644 board/nxp/t104xrdb/MAINTAINERS
> delete mode 100644 board/nxp/t104xrdb/Makefile
> delete mode 100644 board/nxp/t104xrdb/README
> delete mode 100644 board/nxp/t104xrdb/cpld.c
> delete mode 100644 board/nxp/t104xrdb/cpld.h
> delete mode 100644 board/nxp/t104xrdb/ddr.c
> delete mode 100644 board/nxp/t104xrdb/ddr.h
> delete mode 100644 board/nxp/t104xrdb/law.c
> delete mode 100644 board/nxp/t104xrdb/spl.c
> delete mode 100644 board/nxp/t104xrdb/t1040_nand_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1040_sd_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1040_spi_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1040d4_nand_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1040d4_sd_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1040d4_spi_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1042_nand_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1042_pi_nand_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1042_pi_sd_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1042_pi_spi_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1042_sd_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1042_spi_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1042d4_nand_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1042d4_sd_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t1042d4_spi_rcw.cfg
> delete mode 100644 board/nxp/t104xrdb/t104x_pbi.cfg
> delete mode 100644 board/nxp/t104xrdb/t104x_pbi_sb.cfg
> delete mode 100644 board/nxp/t104xrdb/t104xrdb.c
> delete mode 100644 board/nxp/t104xrdb/t104xrdb.h
> delete mode 100644 board/nxp/t104xrdb/tlb.c
> delete mode 100644 configs/MPC837XERDB_defconfig
> delete mode 100644 configs/MPC8548CDS_36BIT_defconfig
> delete mode 100644 configs/MPC8548CDS_defconfig
> delete mode 100644 configs/MPC8548CDS_legacy_defconfig
> delete mode 100644 configs/P2020RDB-PC_36BIT_NAND_defconfig
> delete mode 100644 configs/P2020RDB-PC_36BIT_SDCARD_defconfig
> delete mode 100644 configs/P2020RDB-PC_36BIT_SPIFLASH_defconfig
> delete mode 100644 configs/P2020RDB-PC_36BIT_defconfig
> delete mode 100644 configs/P2020RDB-PC_NAND_defconfig
> delete mode 100644 configs/P2020RDB-PC_SDCARD_defconfig
> delete mode 100644 configs/P2020RDB-PC_SPIFLASH_defconfig
> delete mode 100644 configs/P2020RDB-PC_defconfig
> delete mode 100644 configs/T1042D4RDB_NAND_defconfig
> delete mode 100644 configs/T1042D4RDB_SDCARD_defconfig
> delete mode 100644 configs/T1042D4RDB_SPIFLASH_defconfig
> delete mode 100644 configs/T1042D4RDB_defconfig
> delete mode 100644 doc/README.mpc83xxads
> delete mode 100644 doc/README.mpc85xxcds
> delete mode 100644 doc/README.sata
> delete mode 100644 doc/README.srio-pcie-boot-corenet
> delete mode 100644 drivers/net/fm/p1023.c
> delete mode 100644 drivers/net/fm/p4080.c
> delete mode 100644 drivers/net/fm/p5040.c
> delete mode 100644 include/configs/MPC837XERDB.h
> delete mode 100644 include/configs/MPC8548CDS.h
> delete mode 100644 include/configs/T104xRDB.h
>
--- Thanks!
"I'm not a very positive person" - Linus torvalds
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-22 14:42 ` Bradley Morgan
@ 2026-10-26 8:43 ` Vincent Jardin
2026-10-26 9:25 ` Bradley Morgan
0 siblings, 1 reply; 23+ messages in thread
From: Vincent Jardin @ 2026-10-26 8:43 UTC (permalink / raw)
To: Peng Fan
Cc: Tom Rini, u-boot, Bradley Morgan, Sinan Akman, Bryan Brattlof,
Tomas Alvarez Vanoli
Hi Peng,
Thank you for applying the the lx2160a series and the other patches.
If the powerpc removals need more time after Sinan's remark and Tom's
request to wait for the board maintainers:
https://lore.kernel.org/u-boot/20261022014554.GN3275858@bill-the-cat/
would a pull limited to the first 20 commits be an option for rc1 ?
They are below Bradley's series, up to the commit
e7fbf8d2233 ("board: nbxv3: apply sd1 hwconfig before MC starts")
so the SCMI, fsl_espi, pmbus, ICID and SerDes patches would not change.
Whatever you prefer is fine with me, I only want to make sure the
question is asked before rc1 and we do not miss the merge window.
Thank you,
Vincent
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 8:43 ` Vincent Jardin
@ 2026-10-26 9:25 ` Bradley Morgan
2026-10-26 14:20 ` Tom Rini
0 siblings, 1 reply; 23+ messages in thread
From: Bradley Morgan @ 2026-10-26 9:25 UTC (permalink / raw)
To: Vincent Jardin, Peng Fan
Cc: Tom Rini, u-boot, Sinan Akman, Bryan Brattlof,
Tomas Alvarez Vanoli
On 26 October 2026 08:43:32 GMT, Vincent Jardin <vjardin@free.fr> wrote:
>Hi Peng,
>
>Thank you for applying the the lx2160a series and the other patches.
>
>If the powerpc removals need more time after Sinan's remark and Tom's
>request to wait for the board maintainers:
> https://lore.kernel.org/u-boot/20261022014554.GN3275858@bill-the-cat/
>would a pull limited to the first 20 commits be an option for rc1 ?
>They are below Bradley's series, up to the commit
>e7fbf8d2233 ("board: nbxv3: apply sd1 hwconfig before MC starts")
>so the SCMI, fsl_espi, pmbus, ICID and SerDes patches would not change.
Tom reckoned that today would be his merge day on IRC, but things could
change, I feel these board maintainers are deliberately not responding
tho.:(
>
>Whatever you prefer is fine with me, I only want to make sure the
>question is asked before rc1 and we do not miss the merge window.
>
>Thank you,
> Vincent
--- Thanks!
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 9:25 ` Bradley Morgan
@ 2026-10-26 14:20 ` Tom Rini
2026-10-26 14:58 ` Bradley Morgan
0 siblings, 1 reply; 23+ messages in thread
From: Tom Rini @ 2026-10-26 14:20 UTC (permalink / raw)
To: Bradley Morgan
Cc: Vincent Jardin, Peng Fan, u-boot, Sinan Akman, Bryan Brattlof,
Tomas Alvarez Vanoli
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
On Mon, Oct 26, 2026 at 09:25:25AM +0000, Bradley Morgan wrote:
> On 26 October 2026 08:43:32 GMT, Vincent Jardin <vjardin@free.fr> wrote:
> >Hi Peng,
> >
> >Thank you for applying the the lx2160a series and the other patches.
> >
> >If the powerpc removals need more time after Sinan's remark and Tom's
> >request to wait for the board maintainers:
> > https://lore.kernel.org/u-boot/20261022014554.GN3275858@bill-the-cat/
> >would a pull limited to the first 20 commits be an option for rc1 ?
> >They are below Bradley's series, up to the commit
> >e7fbf8d2233 ("board: nbxv3: apply sd1 hwconfig before MC starts")
> >so the SCMI, fsl_espi, pmbus, ICID and SerDes patches would not change.
We can always take fixes now and dropping platforms a little later, the
merge window isn't as strict here as the linux kernel.
> Tom reckoned that today would be his merge day on IRC, but things could
> change, I feel these board maintainers are deliberately not responding
> tho.:(
PowerPC just isn't a very active area and hasn't been for a long while.
The general rule of thumb for non-urgent changes is two weeks between
posting and merging.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 14:20 ` Tom Rini
@ 2026-10-26 14:58 ` Bradley Morgan
2026-10-26 16:19 ` Vincent Jardin
0 siblings, 1 reply; 23+ messages in thread
From: Bradley Morgan @ 2026-10-26 14:58 UTC (permalink / raw)
To: Tom Rini
Cc: Vincent Jardin, Peng Fan, u-boot, Sinan Akman, Bryan Brattlof,
Tomas Alvarez Vanoli
On 26 October 2026 14:20:23 GMT, Tom Rini <trini@konsulko.com> wrote:
>On Mon, Oct 26, 2026 at 09:25:25AM +0000, Bradley Morgan wrote:
>> On 26 October 2026 08:43:32 GMT, Vincent Jardin <vjardin@free.fr> wrote:
>> >Hi Peng,
>> >
>> >Thank you for applying the the lx2160a series and the other patches.
>> >
>> >If the powerpc removals need more time after Sinan's remark and Tom's
>> >request to wait for the board maintainers:
>> > https://lore.kernel.org/u-boot/20261022014554.GN3275858@bill-the-cat/
>> >would a pull limited to the first 20 commits be an option for rc1 ?
>> >They are below Bradley's series, up to the commit
>> >e7fbf8d2233 ("board: nbxv3: apply sd1 hwconfig before MC starts")
>> >so the SCMI, fsl_espi, pmbus, ICID and SerDes patches would not change.
>
>We can always take fixes now and dropping platforms a little later, the
>merge window isn't as strict here as the linux kernel.
Fair enough
>
>> Tom reckoned that today would be his merge day on IRC, but things could
>> change, I feel these board maintainers are deliberately not responding
>> tho.:(
>
>PowerPC just isn't a very active area and hasn't been for a long while.
>The general rule of thumb for non-urgent changes is two weeks between
>posting and merging.
Isn't that a double edged sword?
I mean, since PowerPC is SO inactive that like nobody will respond, and
it'll be limbo limbo limbo, just to merge say 24 removals and a
maintainers patch, especially the maintainers patch, that has nothing to do with the removals and that'll get all stuck up with the removals I think unless you have other plans, which is annoyance, because it is "oh so inactive"
And I also made a additional maintainers patch that IDK where it will go!!
Either to my custodian tree (p,s: maintainers patch isn't merged yet!!)
Or to another tree, yeah, odd, hm?
(Sorry, I had a small vent, :c)
Hm, I will probably submit the maintainers patch separately, since that
should have very minimal to no conflict, idk what to do here, tom, any
advice?
>
>
--- Thanks!
https://lore.kernel.org/all/EE579805-42F2-4C58-B752-F28779EEB717@grrlz.net/
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 14:58 ` Bradley Morgan
@ 2026-10-26 16:19 ` Vincent Jardin
2026-10-26 16:26 ` Bradley Morgan
0 siblings, 1 reply; 23+ messages in thread
From: Vincent Jardin @ 2026-10-26 16:19 UTC (permalink / raw)
To: Bradley Morgan
Cc: Tom Rini, Peng Fan, u-boot, Sinan Akman, Bryan Brattlof,
Tomas Alvarez Vanoli
Hi,
> Isn't that a double edged sword?
>
> I mean, since PowerPC is SO inactive that like nobody will respond, and
> it'll be limbo limbo limbo, just to merge say 24 removals and a
> maintainers patch, especially the maintainers patch, that has nothing to do with the removals and that'll get all stuck up with the removals I think unless you have other plans, which is annoyance, because it is "oh so inactive"
>
> And I also made a additional maintainers patch that IDK where it will go!!
> Either to my custodian tree (p,s: maintainers patch isn't merged yet!!)
>
> Or to another tree, yeah, odd, hm?
>
> (Sorry, I had a small vent, :c)
I would not drop PPCs so quickly ; there are still many systems running PPCs
even if folks are more in "don't touch things that work", I feel it'll change
withint the upcoming months because of the scale of CVEs of those old systems
and some new regulations in EU. Let's wait/watch, maybe one more year,
before dropping.
It seems long, but looking backward EU regulations will start to be effective only
by end of 2027 and LLM -> explode of new CVEs are just starting...
so the mindset of "don't touch, it works", it'll have to change.
my 2 cents,
Vincent
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 16:19 ` Vincent Jardin
@ 2026-10-26 16:26 ` Bradley Morgan
2026-10-26 16:39 ` Tomas Alvarez Vanoli
0 siblings, 1 reply; 23+ messages in thread
From: Bradley Morgan @ 2026-10-26 16:26 UTC (permalink / raw)
To: Vincent Jardin
Cc: Tom Rini, Peng Fan, u-boot, Sinan Akman, Bryan Brattlof,
Tomas Alvarez Vanoli
On 26 October 2026 16:19:20 GMT, Vincent Jardin <vjardin@free.fr> wrote:
>Hi,
>
>> Isn't that a double edged sword?
>>
>> I mean, since PowerPC is SO inactive that like nobody will respond, and
>> it'll be limbo limbo limbo, just to merge say 24 removals and a
>> maintainers patch, especially the maintainers patch, that has nothing
>to do with the removals and that'll get all stuck up with the removals I
>think unless you have other plans, which is annoyance, because it is "oh
>so inactive"
>>
>> And I also made a additional maintainers patch that IDK where it will
>go!!
>> Either to my custodian tree (p,s: maintainers patch isn't merged yet!!)
>>
>> Or to another tree, yeah, odd, hm?
>>
>> (Sorry, I had a small vent, :c)
>
>I would not drop PPCs so quickly ; there are still many systems running
>PPCs
>even if folks are more in "don't touch things that work", I feel it'll
>change
>withint the upcoming months because of the scale of CVEs of those old
>systems
>and some new regulations in EU. Let's wait/watch, maybe one more year,
>before dropping.
>
>It seems long, but looking backward EU regulations will start to be
>effective only
>by end of 2027 and LLM -> explode of new CVEs are just starting...
>so the mindset of "don't touch, it works", it'll have to change.
Yeah, I removed so many systems because it was 1: EOL, 2: Old, unmaintained
rubbish (well, some of them)
But my concern is the one patch that has nothing to do with it.
26/26, the maintainers patch, I already got a tree and stuff, but I
wouldn't know if like it'll
A: get merged when they merge your fixes
Or
B: Merge when the removals get merged :(
I'd prefer A personally, because of the fact that the patch has nothing to
do with it. If that makes sense.
Id personally think a cleanup is more than due for this, I have millads
more cleanups to do when my maintainers patch gets merged, PowerPC as I
see it at the moment is in a slight disarray, well, it works, but it needs
to be cleaned and organised a bit.
Id say 19+ more patches would be required in order to make this actually
clean ISH.
Because for 1: power(8,9,10) isn't even implemented yet! What!?
Well, I'm not sure about that being a priority because for 1: it can be
booted thru LPAR. Which, is odd. (Thanks IBM! :c)
Personally, PowerPC needs a nice dustpan and brush across before it could
be classed as an actually clean architecture subsystem!
And god forbid the bugs. Somebody with a AI will be having a field day
covering their ears going "la la la la bugs", because I can see bugs all
over the place!
But thank god people still use ppc on u-boot, and for anybody reading this
using u-boot on their PowerPC as we speak, thank you so much for using it,
and me, as a maintainer(tm) and the whole community sends our unreserved
thanks for your use of it.
>
>my 2 cents,
> Vincent
--- Thanks!
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 16:26 ` Bradley Morgan
@ 2026-10-26 16:39 ` Tomas Alvarez Vanoli
2026-10-26 16:42 ` Bradley Morgan
0 siblings, 1 reply; 23+ messages in thread
From: Tomas Alvarez Vanoli @ 2026-10-26 16:39 UTC (permalink / raw)
To: Bradley Morgan, Vincent Jardin
Cc: Tom Rini, Peng Fan, u-boot@lists.u-boot-project.org, Sinan Akman,
Bryan Brattlof, Holger Brunck
>On 26 October 2026 16:19:20 GMT, Vincent Jardin <vjardin@free.fr> wrote:
>>Hi,
>>
>>> Isn't that a double edged sword?
>>>
>>> I mean, since PowerPC is SO inactive that like nobody will respond, and
>>> it'll be limbo limbo limbo, just to merge say 24 removals and a
>>> maintainers patch, especially the maintainers patch, that has nothing
>>to do with the removals and that'll get all stuck up with the removals I
>>think unless you have other plans, which is annoyance, because it is "oh
>>so inactive"
>>>
>>> And I also made a additional maintainers patch that IDK where it will
>>go!!
>>> Either to my custodian tree (p,s: maintainers patch isn't merged yet!!)
>>>
>>> Or to another tree, yeah, odd, hm?
>>>
>>> (Sorry, I had a small vent, :c)
>>
>>I would not drop PPCs so quickly ; there are still many systems running
>>PPCs
>>even if folks are more in "don't touch things that work", I feel it'll
>>change
>>withint the upcoming months because of the scale of CVEs of those old
>>systems
>>and some new regulations in EU. Let's wait/watch, maybe one more year,
>>before dropping.
>>
>>It seems long, but looking backward EU regulations will start to be
>>effective only
>>by end of 2027 and LLM -> explode of new CVEs are just starting...
>>so the mindset of "don't touch, it works", it'll have to change.
>
>Yeah, I removed so many systems because it was 1: EOL, 2: Old, unmaintained
>rubbish (well, some of them)
>
>But my concern is the one patch that has nothing to do with it.
>
>26/26, the maintainers patch, I already got a tree and stuff, but I
>wouldn't know if like it'll
>
>A: get merged when they merge your fixes
>
>Or
>
>B: Merge when the removals get merged :(
>
>I'd prefer A personally, because of the fact that the patch has nothing to
>do with it. If that makes sense.
>
>Id personally think a cleanup is more than due for this, I have millads
>more cleanups to do when my maintainers patch gets merged, PowerPC as I
>see it at the moment is in a slight disarray, well, it works, but it needs
>to be cleaned and organised a bit.
>
>Id say 19+ more patches would be required in order to make this actually
>clean ISH.
>
>Because for 1: power(8,9,10) isn't even implemented yet! What!?
>
>Well, I'm not sure about that being a priority because for 1: it can be
>booted thru LPAR. Which, is odd. (Thanks IBM! :c)
>
>Personally, PowerPC needs a nice dustpan and brush across before it could
>be classed as an actually clean architecture subsystem!
>
>And god forbid the bugs. Somebody with a AI will be having a field day
>covering their ears going "la la la la bugs", because I can see bugs all
>over the place!
>
>But thank god people still use ppc on u-boot, and for anybody reading this
>using u-boot on their PowerPC as we speak, thank you so much for using it,
>and me, as a maintainer(tm) and the whole community sends our unreserved
>thanks for your use of it.
>
>
>
>>
>>my 2 cents,
>> Vincent
>
>--- Thanks!
Hi all,
Just a data point from a user: we are using U-Boot on a T1040 (QorIQ /
mpc85xx) in a product, and we intend to keep up with mainline as much as
we can. We'd appreciate PowerPC support staying in tree, and we're happy
to test patches on T1040 hardware and report back.
We run u-boot in 32-bit mode (not sure if it is possible to use 64-bit) and
linux in 64-bit.
I am in the process of bringing it up to our 2025.07 branch and potentially
mainlining as much as possible. We have some remnants of it under
`board/keymile/kmcent2`.
If any of the planned removals or cleanups touch T104x/QorIQ code or
boards, please keep me and holger.brunck@hitachienergy.com on Cc.
Thanks to everyone maintaining this.
Best regards,
Tomas
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 16:39 ` Tomas Alvarez Vanoli
@ 2026-10-26 16:42 ` Bradley Morgan
2026-10-26 16:55 ` Tomas Alvarez Vanoli
0 siblings, 1 reply; 23+ messages in thread
From: Bradley Morgan @ 2026-10-26 16:42 UTC (permalink / raw)
To: Tomas Alvarez Vanoli, Vincent Jardin
Cc: Tom Rini, Peng Fan, u-boot@lists.u-boot-project.org, Sinan Akman,
Bryan Brattlof, Holger Brunck
On 26 October 2026 16:39:21 GMT, Tomas Alvarez Vanoli
<tomas.alvarez-vanoli@hitachienergy.com> wrote:
>>On 26 October 2026 16:19:20 GMT, Vincent Jardin <vjardin@free.fr> wrote:
>>>Hi,
>>>
>>>> Isn't that a double edged sword?
>>>>
>>>> I mean, since PowerPC is SO inactive that like nobody will respond,
>and
>>>> it'll be limbo limbo limbo, just to merge say 24 removals and a
>>>> maintainers patch, especially the maintainers patch, that has nothing
>>>to do with the removals and that'll get all stuck up with the removals I
>>>think unless you have other plans, which is annoyance, because it is "oh
>>>so inactive"
>>>>
>>>> And I also made a additional maintainers patch that IDK where it will
>>>go!!
>>>> Either to my custodian tree (p,s: maintainers patch isn't merged
>yet!!)
>>>>
>>>> Or to another tree, yeah, odd, hm?
>>>>
>>>> (Sorry, I had a small vent, :c)
>>>
>>>I would not drop PPCs so quickly ; there are still many systems running
>>>PPCs
>>>even if folks are more in "don't touch things that work", I feel it'll
>>>change
>>>withint the upcoming months because of the scale of CVEs of those old
>>>systems
>>>and some new regulations in EU. Let's wait/watch, maybe one more year,
>>>before dropping.
>>>
>>>It seems long, but looking backward EU regulations will start to be
>>>effective only
>>>by end of 2027 and LLM -> explode of new CVEs are just starting...
>>>so the mindset of "don't touch, it works", it'll have to change.
>>
>>Yeah, I removed so many systems because it was 1: EOL, 2: Old,
>unmaintained
>>rubbish (well, some of them)
>>
>>But my concern is the one patch that has nothing to do with it.
>>
>>26/26, the maintainers patch, I already got a tree and stuff, but I
>>wouldn't know if like it'll
>>
>>A: get merged when they merge your fixes
>>
>>Or
>>
>>B: Merge when the removals get merged :(
>>
>>I'd prefer A personally, because of the fact that the patch has nothing
>to
>>do with it. If that makes sense.
>>
>>Id personally think a cleanup is more than due for this, I have millads
>>more cleanups to do when my maintainers patch gets merged, PowerPC as I
>>see it at the moment is in a slight disarray, well, it works, but it
>needs
>>to be cleaned and organised a bit.
>>
>>Id say 19+ more patches would be required in order to make this actually
>>clean ISH.
>>
>>Because for 1: power(8,9,10) isn't even implemented yet! What!?
>>
>>Well, I'm not sure about that being a priority because for 1: it can be
>>booted thru LPAR. Which, is odd. (Thanks IBM! :c)
>>
>>Personally, PowerPC needs a nice dustpan and brush across before it could
>>be classed as an actually clean architecture subsystem!
>>
>>And god forbid the bugs. Somebody with a AI will be having a field day
>>covering their ears going "la la la la bugs", because I can see bugs all
>>over the place!
>>
>>But thank god people still use ppc on u-boot, and for anybody reading
>this
>>using u-boot on their PowerPC as we speak, thank you so much for using
>it,
>>and me, as a maintainer(tm) and the whole community sends our unreserved
>>thanks for your use of it.
>>
>>
>>
>>>
>>>my 2 cents,
>>> Vincent
>>
>>--- Thanks!
>
>
>Hi all,
>
>Just a data point from a user: we are using U-Boot on a T1040 (QorIQ /
>mpc85xx) in a product, and we intend to keep up with mainline as much as
>we can. We'd appreciate PowerPC support staying in tree, and we're happy
>to test patches on T1040 hardware and report back.
>We run u-boot in 32-bit mode (not sure if it is possible to use 64-bit)
>and
>linux in 64-bit.
>I am in the process of bringing it up to our 2025.07 branch and
>potentially
>mainlining as much as possible. We have some remnants of it under
>`board/keymile/kmcent2`.
Would T1042D4RDB affect you?
>
>If any of the planned removals or cleanups touch T104x/QorIQ code or
>boards, please keep me and holger.brunck@hitachienergy.com on Cc.
>
>Thanks to everyone maintaining this.
>
>Best regards,
>Tomas
>
--- Thanks!
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 16:42 ` Bradley Morgan
@ 2026-10-26 16:55 ` Tomas Alvarez Vanoli
2026-10-26 16:58 ` Bradley Morgan
2026-10-26 17:19 ` Tom Rini
0 siblings, 2 replies; 23+ messages in thread
From: Tomas Alvarez Vanoli @ 2026-10-26 16:55 UTC (permalink / raw)
To: Bradley Morgan, Vincent Jardin
Cc: Tom Rini, Peng Fan, u-boot@lists.u-boot-project.org, Sinan Akman,
Bryan Brattlof, Holger Brunck
>>
>>Hi all,
>>
>>Just a data point from a user: we are using U-Boot on a T1040 (QorIQ /
>>mpc85xx) in a product, and we intend to keep up with mainline as much as
>>we can. We'd appreciate PowerPC support staying in tree, and we're happy
>>to test patches on T1040 hardware and report back.
>>We run u-boot in 32-bit mode (not sure if it is possible to use 64-bit)
>>and
>>linux in 64-bit.
>>I am in the process of bringing it up to our 2025.07 branch and
>>potentially
>>mainlining as much as possible. We have some remnants of it under
>>`board/keymile/kmcent2`.
>
>Would T1042D4RDB affect you?
Not directly from what I see in the code, as long as the shared code with
ARCH_T1040 is kept. Sorry for the false alarm, just wanted to report that
there are dozens of us using powerpc :)
>
>>
>>If any of the planned removals or cleanups touch T104x/QorIQ code or
>>boards, please keep me and holger.brunck@hitachienergy.com on Cc.
>>
>>Thanks to everyone maintaining this.
>>
>>Best regards,
>>Tomas
>>
>
>--- Thanks!
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 16:55 ` Tomas Alvarez Vanoli
@ 2026-10-26 16:58 ` Bradley Morgan
2026-10-26 17:00 ` Bradley Morgan
2026-10-26 17:19 ` Tom Rini
1 sibling, 1 reply; 23+ messages in thread
From: Bradley Morgan @ 2026-10-26 16:58 UTC (permalink / raw)
To: Tomas Alvarez Vanoli, Vincent Jardin
Cc: Tom Rini, Peng Fan, u-boot@lists.u-boot-project.org, Sinan Akman,
Bryan Brattlof, Holger Brunck
On 26 October 2026 16:55:09 GMT, Tomas Alvarez Vanoli
<tomas.alvarez-vanoli@hitachienergy.com> wrote:
>>>
>>>Hi all,
>>>
>>>Just a data point from a user: we are using U-Boot on a T1040 (QorIQ /
>>>mpc85xx) in a product, and we intend to keep up with mainline as much as
>>>we can. We'd appreciate PowerPC support staying in tree, and we're happy
>>>to test patches on T1040 hardware and report back.
>>>We run u-boot in 32-bit mode (not sure if it is possible to use 64-bit)
>>>and
>>>linux in 64-bit.
>>>I am in the process of bringing it up to our 2025.07 branch and
>>>potentially
>>>mainlining as much as possible. We have some remnants of it under
>>>`board/keymile/kmcent2`.
>>
>>Would T1042D4RDB affect you?
>
>Not directly from what I see in the code, as long as the shared code with
>ARCH_T1040 is kept. Sorry for the false alarm, just wanted to report that
>there are dozens of us using powerpc :)
What you could do if you would like is to test the whole series to see if
it unaffected you.
Btw tom I had a idea: you merge Vincent's bug fix and my maintainers
patch,you make a PowerPC custodian tree, and I handle the series and the
naks and stuff and the comments.
>
>>
>>>
>>>If any of the planned removals or cleanups touch T104x/QorIQ code or
>>>boards, please keep me and holger.brunck@hitachienergy.com on Cc.
>>>
>>>Thanks to everyone maintaining this.
>>>
>>>Best regards,
>>>Tomas
>>>
>>
>>--- Thanks!
>
>
>
>
>
--- Thanks!
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 16:58 ` Bradley Morgan
@ 2026-10-26 17:00 ` Bradley Morgan
2026-10-26 17:23 ` Tom Rini
0 siblings, 1 reply; 23+ messages in thread
From: Bradley Morgan @ 2026-10-26 17:00 UTC (permalink / raw)
To: Tomas Alvarez Vanoli, Vincent Jardin
Cc: Tom Rini, Peng Fan, u-boot@lists.u-boot-project.org, Sinan Akman,
Bryan Brattlof, Holger Brunck
On 26 October 2026 16:58:47 GMT, Bradley Morgan <brads@mainlining.org>
wrote:
>On 26 October 2026 16:55:09 GMT, Tomas Alvarez Vanoli
><tomas.alvarez-vanoli@hitachienergy.com> wrote:
>>>>
>>>>Hi all,
>>>>
>>>>Just a data point from a user: we are using U-Boot on a T1040 (QorIQ /
>>>>mpc85xx) in a product, and we intend to keep up with mainline as much
>as
>>>>we can. We'd appreciate PowerPC support staying in tree, and we're
>happy
>>>>to test patches on T1040 hardware and report back.
>>>>We run u-boot in 32-bit mode (not sure if it is possible to use 64-bit)
>>>>and
>>>>linux in 64-bit.
>>>>I am in the process of bringing it up to our 2025.07 branch and
>>>>potentially
>>>>mainlining as much as possible. We have some remnants of it under
>>>>`board/keymile/kmcent2`.
>>>
>>>Would T1042D4RDB affect you?
>>
>>Not directly from what I see in the code, as long as the shared code with
>>ARCH_T1040 is kept. Sorry for the false alarm, just wanted to report that
>>there are dozens of us using powerpc :)
>
>What you could do if you would like is to test the whole series to see if
>it unaffected you.
>
>
>Btw tom I had a idea: you merge Vincent's bug fix and my maintainers
>patch,you make a PowerPC custodian tree, and I handle the series and the
>naks and stuff and the comments.
and btw yes I'll make the pr with the finished patches so you can merge
them cleanly
>
>>
>>>
>>>>
>>>>If any of the planned removals or cleanups touch T104x/QorIQ code or
>>>>boards, please keep me and holger.brunck@hitachienergy.com on Cc.
>>>>
>>>>Thanks to everyone maintaining this.
>>>>
>>>>Best regards,
>>>>Tomas
>>>>
>>>
>>>--- Thanks!
>>
>>
>>
>>
>>
>
>--- Thanks!
--- Thanks!
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 16:55 ` Tomas Alvarez Vanoli
2026-10-26 16:58 ` Bradley Morgan
@ 2026-10-26 17:19 ` Tom Rini
1 sibling, 0 replies; 23+ messages in thread
From: Tom Rini @ 2026-10-26 17:19 UTC (permalink / raw)
To: Tomas Alvarez Vanoli
Cc: Bradley Morgan, Vincent Jardin, Peng Fan,
u-boot@lists.u-boot-project.org, Sinan Akman, Bryan Brattlof,
Holger Brunck
[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]
On Mon, Oct 26, 2026 at 04:55:09PM +0000, Tomas Alvarez Vanoli wrote:
> >>
> >>Hi all,
> >>
> >>Just a data point from a user: we are using U-Boot on a T1040 (QorIQ /
> >>mpc85xx) in a product, and we intend to keep up with mainline as much as
> >>we can. We'd appreciate PowerPC support staying in tree, and we're happy
> >>to test patches on T1040 hardware and report back.
> >>We run u-boot in 32-bit mode (not sure if it is possible to use 64-bit)
> >>and
> >>linux in 64-bit.
> >>I am in the process of bringing it up to our 2025.07 branch and
> >>potentially
> >>mainlining as much as possible. We have some remnants of it under
> >>`board/keymile/kmcent2`.
> >
> >Would T1042D4RDB affect you?
>
> Not directly from what I see in the code, as long as the shared code with
> ARCH_T1040 is kept. Sorry for the false alarm, just wanted to report that
> there are dozens of us using powerpc :)
This is why I'm trying to go slowly with dropping the PowerPC boards
that *probably* no one is caring about. Size growth has been (although I
dare say I will be haunted by this statement) kept relatively under
control for a good while. In all of PowerPC there is one DM migration
build time warning. So to borrow a phrase, if it ain't broke, it doesn't
need to be removed. The amount of active maintenance it requires is
small.
> >>If any of the planned removals or cleanups touch T104x/QorIQ code or
> >>boards, please keep me and holger.brunck@hitachienergy.com on Cc.
Holger shows up for 3 keymile boards, and you show up for one of those
as well. A thing that would really help is adding yourselves to
MAINTAINER entries for any other platforms, especially reference
platforms, that you also still have interest in.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 17:00 ` Bradley Morgan
@ 2026-10-26 17:23 ` Tom Rini
2026-10-26 17:27 ` Bradley Morgan
0 siblings, 1 reply; 23+ messages in thread
From: Tom Rini @ 2026-10-26 17:23 UTC (permalink / raw)
To: Bradley Morgan
Cc: Tomas Alvarez Vanoli, Vincent Jardin, Peng Fan,
u-boot@lists.u-boot-project.org, Sinan Akman, Bryan Brattlof,
Holger Brunck
[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]
On Mon, Oct 26, 2026 at 05:00:19PM +0000, Bradley Morgan wrote:
> On 26 October 2026 16:58:47 GMT, Bradley Morgan <brads@mainlining.org>
> wrote:
> >On 26 October 2026 16:55:09 GMT, Tomas Alvarez Vanoli
> ><tomas.alvarez-vanoli@hitachienergy.com> wrote:
> >>>>
> >>>>Hi all,
> >>>>
> >>>>Just a data point from a user: we are using U-Boot on a T1040 (QorIQ /
> >>>>mpc85xx) in a product, and we intend to keep up with mainline as much
> >as
> >>>>we can. We'd appreciate PowerPC support staying in tree, and we're
> >happy
> >>>>to test patches on T1040 hardware and report back.
> >>>>We run u-boot in 32-bit mode (not sure if it is possible to use 64-bit)
> >>>>and
> >>>>linux in 64-bit.
> >>>>I am in the process of bringing it up to our 2025.07 branch and
> >>>>potentially
> >>>>mainlining as much as possible. We have some remnants of it under
> >>>>`board/keymile/kmcent2`.
> >>>
> >>>Would T1042D4RDB affect you?
> >>
> >>Not directly from what I see in the code, as long as the shared code with
> >>ARCH_T1040 is kept. Sorry for the false alarm, just wanted to report that
> >>there are dozens of us using powerpc :)
> >
> >What you could do if you would like is to test the whole series to see if
> >it unaffected you.
> >
> >
> >Btw tom I had a idea: you merge Vincent's bug fix and my maintainers
> >patch,you make a PowerPC custodian tree, and I handle the series and the
> >naks and stuff and the comments.
>
> and btw yes I'll make the pr with the finished patches so you can merge
> them cleanly
Trees are relatively cheap, but I'm not sure we need another one either
for the subset of formerly-Freescale and not-QorIQ PowerPC parts. Since
I added you to the fsl-qoriq tree, you can also just pick up the
outstanding fixes and your maintainer patches (and leave dropping stuff
for now, as this series shows today we're just getting people having a
chance to see and reply to this stuff) and send me a PR. Thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 17:23 ` Tom Rini
@ 2026-10-26 17:27 ` Bradley Morgan
2026-10-26 18:30 ` Tom Rini
0 siblings, 1 reply; 23+ messages in thread
From: Bradley Morgan @ 2026-10-26 17:27 UTC (permalink / raw)
To: Tom Rini
Cc: Tomas Alvarez Vanoli, Vincent Jardin, Peng Fan,
u-boot@lists.u-boot-project.org, Sinan Akman, Bryan Brattlof,
Holger Brunck
On 26 October 2026 17:23:32 GMT, Tom Rini <trini@konsulko.com> wrote:
>On Mon, Oct 26, 2026 at 05:00:19PM +0000, Bradley Morgan wrote:
>> On 26 October 2026 16:58:47 GMT, Bradley Morgan <brads@mainlining.org>
>> wrote:
>> >On 26 October 2026 16:55:09 GMT, Tomas Alvarez Vanoli
>> ><tomas.alvarez-vanoli@hitachienergy.com> wrote:
>> >>>>
>> >>>>Hi all,
>> >>>>
>> >>>>Just a data point from a user: we are using U-Boot on a T1040 (QorIQ
>/
>> >>>>mpc85xx) in a product, and we intend to keep up with mainline as
>much
>> >as
>> >>>>we can. We'd appreciate PowerPC support staying in tree, and we're
>> >happy
>> >>>>to test patches on T1040 hardware and report back.
>> >>>>We run u-boot in 32-bit mode (not sure if it is possible to use
>64-bit)
>> >>>>and
>> >>>>linux in 64-bit.
>> >>>>I am in the process of bringing it up to our 2025.07 branch and
>> >>>>potentially
>> >>>>mainlining as much as possible. We have some remnants of it under
>> >>>>`board/keymile/kmcent2`.
>> >>>
>> >>>Would T1042D4RDB affect you?
>> >>
>> >>Not directly from what I see in the code, as long as the shared code
>with
>> >>ARCH_T1040 is kept. Sorry for the false alarm, just wanted to report
>that
>> >>there are dozens of us using powerpc :)
>> >
>> >What you could do if you would like is to test the whole series to see
>if
>> >it unaffected you.
>> >
>> >
>> >Btw tom I had a idea: you merge Vincent's bug fix and my maintainers
>> >patch,you make a PowerPC custodian tree, and I handle the series and
>the
>> >naks and stuff and the comments.
>>
>> and btw yes I'll make the pr with the finished patches so you can merge
>> them cleanly
>
>Trees are relatively cheap, but I'm not sure we need another one either
>for the subset of formerly-Freescale and not-QorIQ PowerPC parts. Since
>I added you to the fsl-qoriq tree, you can also just pick up the
>outstanding fixes and your maintainer patches (and leave dropping stuff
>for now, as this series shows today we're just getting people having a
>chance to see and reply to this stuff) and send me a PR. Thanks.
Hi, sorry, I didn't clarify enough, so I had a chat for some people from
the open src firmware slack, yes?
And here is their answer
"Ah, Peng Fan maintains the FSL QoriQ tree:
https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq
That is the vendor one though.
So yea, I'd go with a general PowerPC tree.
Also because QoriQ is both Arm and PPC series. :sweat_smile:"
And even my slopper suggests the tree, for sanity purposes :D
>
>
--- Thanks!
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 17:27 ` Bradley Morgan
@ 2026-10-26 18:30 ` Tom Rini
2026-10-26 21:14 ` Bradley Morgan
0 siblings, 1 reply; 23+ messages in thread
From: Tom Rini @ 2026-10-26 18:30 UTC (permalink / raw)
To: Bradley Morgan
Cc: Tomas Alvarez Vanoli, Vincent Jardin, Peng Fan,
u-boot@lists.u-boot-project.org, Sinan Akman, Bryan Brattlof,
Holger Brunck
[-- Attachment #1: Type: text/plain, Size: 2896 bytes --]
On Mon, Oct 26, 2026 at 05:27:05PM +0000, Bradley Morgan wrote:
> On 26 October 2026 17:23:32 GMT, Tom Rini <trini@konsulko.com> wrote:
> >On Mon, Oct 26, 2026 at 05:00:19PM +0000, Bradley Morgan wrote:
> >> On 26 October 2026 16:58:47 GMT, Bradley Morgan <brads@mainlining.org>
> >> wrote:
> >> >On 26 October 2026 16:55:09 GMT, Tomas Alvarez Vanoli
> >> ><tomas.alvarez-vanoli@hitachienergy.com> wrote:
> >> >>>>
> >> >>>>Hi all,
> >> >>>>
> >> >>>>Just a data point from a user: we are using U-Boot on a T1040 (QorIQ
> >/
> >> >>>>mpc85xx) in a product, and we intend to keep up with mainline as
> >much
> >> >as
> >> >>>>we can. We'd appreciate PowerPC support staying in tree, and we're
> >> >happy
> >> >>>>to test patches on T1040 hardware and report back.
> >> >>>>We run u-boot in 32-bit mode (not sure if it is possible to use
> >64-bit)
> >> >>>>and
> >> >>>>linux in 64-bit.
> >> >>>>I am in the process of bringing it up to our 2025.07 branch and
> >> >>>>potentially
> >> >>>>mainlining as much as possible. We have some remnants of it under
> >> >>>>`board/keymile/kmcent2`.
> >> >>>
> >> >>>Would T1042D4RDB affect you?
> >> >>
> >> >>Not directly from what I see in the code, as long as the shared code
> >with
> >> >>ARCH_T1040 is kept. Sorry for the false alarm, just wanted to report
> >that
> >> >>there are dozens of us using powerpc :)
> >> >
> >> >What you could do if you would like is to test the whole series to see
> >if
> >> >it unaffected you.
> >> >
> >> >
> >> >Btw tom I had a idea: you merge Vincent's bug fix and my maintainers
> >> >patch,you make a PowerPC custodian tree, and I handle the series and
> >the
> >> >naks and stuff and the comments.
> >>
> >> and btw yes I'll make the pr with the finished patches so you can merge
> >> them cleanly
> >
> >Trees are relatively cheap, but I'm not sure we need another one either
> >for the subset of formerly-Freescale and not-QorIQ PowerPC parts. Since
> >I added you to the fsl-qoriq tree, you can also just pick up the
> >outstanding fixes and your maintainer patches (and leave dropping stuff
> >for now, as this series shows today we're just getting people having a
> >chance to see and reply to this stuff) and send me a PR. Thanks.
>
> Hi, sorry, I didn't clarify enough, so I had a chat for some people from
> the open src firmware slack, yes?
>
> And here is their answer
>
> "Ah, Peng Fan maintains the FSL QoriQ tree:
> https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq
>
> That is the vendor one though.
> So yea, I'd go with a general PowerPC tree.
>
> Also because QoriQ is both Arm and PPC series. :sweat_smile:"
>
> And even my slopper suggests the tree, for sanity purposes :D
Fine, trees are still cheap. There's u-boot-ppc now. But please keep in
mind everything else I said, thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 18:30 ` Tom Rini
@ 2026-10-26 21:14 ` Bradley Morgan
2026-10-26 21:19 ` Tom Rini
0 siblings, 1 reply; 23+ messages in thread
From: Bradley Morgan @ 2026-10-26 21:14 UTC (permalink / raw)
To: Tom Rini
Cc: Tomas Alvarez Vanoli, Vincent Jardin, Peng Fan,
u-boot@lists.u-boot-project.org, Sinan Akman, Bryan Brattlof,
Holger Brunck
On 26 October 2026 18:30:10 GMT, Tom Rini <trini@konsulko.com> wrote:
>On Mon, Oct 26, 2026 at 05:27:05PM +0000, Bradley Morgan wrote:
>> On 26 October 2026 17:23:32 GMT, Tom Rini <trini@konsulko.com> wrote:
>> >On Mon, Oct 26, 2026 at 05:00:19PM +0000, Bradley Morgan wrote:
>> >> On 26 October 2026 16:58:47 GMT, Bradley Morgan
><brads@mainlining.org>
>> >> wrote:
>> >> >On 26 October 2026 16:55:09 GMT, Tomas Alvarez Vanoli
>> >> ><tomas.alvarez-vanoli@hitachienergy.com> wrote:
>> >> >>>>
>> >> >>>>Hi all,
>> >> >>>>
>> >> >>>>Just a data point from a user: we are using U-Boot on a T1040
>(QorIQ
>> >/
>> >> >>>>mpc85xx) in a product, and we intend to keep up with mainline as
>> >much
>> >> >as
>> >> >>>>we can. We'd appreciate PowerPC support staying in tree, and
>we're
>> >> >happy
>> >> >>>>to test patches on T1040 hardware and report back.
>> >> >>>>We run u-boot in 32-bit mode (not sure if it is possible to use
>> >64-bit)
>> >> >>>>and
>> >> >>>>linux in 64-bit.
>> >> >>>>I am in the process of bringing it up to our 2025.07 branch and
>> >> >>>>potentially
>> >> >>>>mainlining as much as possible. We have some remnants of it under
>> >> >>>>`board/keymile/kmcent2`.
>> >> >>>
>> >> >>>Would T1042D4RDB affect you?
>> >> >>
>> >> >>Not directly from what I see in the code, as long as the shared
>code
>> >with
>> >> >>ARCH_T1040 is kept. Sorry for the false alarm, just wanted to
>report
>> >that
>> >> >>there are dozens of us using powerpc :)
>> >> >
>> >> >What you could do if you would like is to test the whole series to
>see
>> >if
>> >> >it unaffected you.
>> >> >
>> >> >
>> >> >Btw tom I had a idea: you merge Vincent's bug fix and my maintainers
>> >> >patch,you make a PowerPC custodian tree, and I handle the series and
>> >the
>> >> >naks and stuff and the comments.
>> >>
>> >> and btw yes I'll make the pr with the finished patches so you can
>merge
>> >> them cleanly
>> >
>> >Trees are relatively cheap, but I'm not sure we need another one either
>> >for the subset of formerly-Freescale and not-QorIQ PowerPC parts. Since
>> >I added you to the fsl-qoriq tree, you can also just pick up the
>> >outstanding fixes and your maintainer patches (and leave dropping stuff
>> >for now, as this series shows today we're just getting people having a
>> >chance to see and reply to this stuff) and send me a PR. Thanks.
>>
>> Hi, sorry, I didn't clarify enough, so I had a chat for some people from
>> the open src firmware slack, yes?
>>
>> And here is their answer
>>
>> "Ah, Peng Fan maintains the FSL QoriQ tree:
>> https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq
>>
>> That is the vendor one though.
>> So yea, I'd go with a general PowerPC tree.
>>
>> Also because QoriQ is both Arm and PPC series. :sweat_smile:"
>>
>> And even my slopper suggests the tree, for sanity purposes :D
>
>Fine, trees are still cheap. There's u-boot-ppc now. But please keep in
>mind everything else I said, thanks.
Thx.
Question: will you merge the maintainers patch on this PR, so I can focus on my add-on maintainers patch and the removals?
>
>
--- Thanks!
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 21:14 ` Bradley Morgan
@ 2026-10-26 21:19 ` Tom Rini
2026-10-26 21:27 ` Bradley Morgan
0 siblings, 1 reply; 23+ messages in thread
From: Tom Rini @ 2026-10-26 21:19 UTC (permalink / raw)
To: Bradley Morgan
Cc: Tomas Alvarez Vanoli, Vincent Jardin, Peng Fan,
u-boot@lists.u-boot-project.org, Sinan Akman, Bryan Brattlof,
Holger Brunck
[-- Attachment #1: Type: text/plain, Size: 3483 bytes --]
On Mon, Oct 26, 2026 at 09:14:37PM +0000, Bradley Morgan wrote:
> On 26 October 2026 18:30:10 GMT, Tom Rini <trini@konsulko.com> wrote:
> >On Mon, Oct 26, 2026 at 05:27:05PM +0000, Bradley Morgan wrote:
> >> On 26 October 2026 17:23:32 GMT, Tom Rini <trini@konsulko.com> wrote:
> >> >On Mon, Oct 26, 2026 at 05:00:19PM +0000, Bradley Morgan wrote:
> >> >> On 26 October 2026 16:58:47 GMT, Bradley Morgan
> ><brads@mainlining.org>
> >> >> wrote:
> >> >> >On 26 October 2026 16:55:09 GMT, Tomas Alvarez Vanoli
> >> >> ><tomas.alvarez-vanoli@hitachienergy.com> wrote:
> >> >> >>>>
> >> >> >>>>Hi all,
> >> >> >>>>
> >> >> >>>>Just a data point from a user: we are using U-Boot on a T1040
> >(QorIQ
> >> >/
> >> >> >>>>mpc85xx) in a product, and we intend to keep up with mainline as
> >> >much
> >> >> >as
> >> >> >>>>we can. We'd appreciate PowerPC support staying in tree, and
> >we're
> >> >> >happy
> >> >> >>>>to test patches on T1040 hardware and report back.
> >> >> >>>>We run u-boot in 32-bit mode (not sure if it is possible to use
> >> >64-bit)
> >> >> >>>>and
> >> >> >>>>linux in 64-bit.
> >> >> >>>>I am in the process of bringing it up to our 2025.07 branch and
> >> >> >>>>potentially
> >> >> >>>>mainlining as much as possible. We have some remnants of it under
> >> >> >>>>`board/keymile/kmcent2`.
> >> >> >>>
> >> >> >>>Would T1042D4RDB affect you?
> >> >> >>
> >> >> >>Not directly from what I see in the code, as long as the shared
> >code
> >> >with
> >> >> >>ARCH_T1040 is kept. Sorry for the false alarm, just wanted to
> >report
> >> >that
> >> >> >>there are dozens of us using powerpc :)
> >> >> >
> >> >> >What you could do if you would like is to test the whole series to
> >see
> >> >if
> >> >> >it unaffected you.
> >> >> >
> >> >> >
> >> >> >Btw tom I had a idea: you merge Vincent's bug fix and my maintainers
> >> >> >patch,you make a PowerPC custodian tree, and I handle the series and
> >> >the
> >> >> >naks and stuff and the comments.
> >> >>
> >> >> and btw yes I'll make the pr with the finished patches so you can
> >merge
> >> >> them cleanly
> >> >
> >> >Trees are relatively cheap, but I'm not sure we need another one either
> >> >for the subset of formerly-Freescale and not-QorIQ PowerPC parts. Since
> >> >I added you to the fsl-qoriq tree, you can also just pick up the
> >> >outstanding fixes and your maintainer patches (and leave dropping stuff
> >> >for now, as this series shows today we're just getting people having a
> >> >chance to see and reply to this stuff) and send me a PR. Thanks.
> >>
> >> Hi, sorry, I didn't clarify enough, so I had a chat for some people from
> >> the open src firmware slack, yes?
> >>
> >> And here is their answer
> >>
> >> "Ah, Peng Fan maintains the FSL QoriQ tree:
> >> https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq
> >>
> >> That is the vendor one though.
> >> So yea, I'd go with a general PowerPC tree.
> >>
> >> Also because QoriQ is both Arm and PPC series. :sweat_smile:"
> >>
> >> And even my slopper suggests the tree, for sanity purposes :D
> >
> >Fine, trees are still cheap. There's u-boot-ppc now. But please keep in
> >mind everything else I said, thanks.
>
> Thx.
>
> Question: will you merge the maintainers patch on this PR, so I can focus on my add-on maintainers patch and the removals?
Lets hold off on the removals a bit more, as I was saying.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 21:19 ` Tom Rini
@ 2026-10-26 21:27 ` Bradley Morgan
2026-10-27 0:19 ` Tom Rini
0 siblings, 1 reply; 23+ messages in thread
From: Bradley Morgan @ 2026-10-26 21:27 UTC (permalink / raw)
To: Tom Rini
Cc: Tomas Alvarez Vanoli, Vincent Jardin, Peng Fan,
u-boot@lists.u-boot-project.org, Sinan Akman, Bryan Brattlof,
Holger Brunck
On 26 October 2026 21:19:52 GMT, Tom Rini <trini@konsulko.com> wrote:
>On Mon, Oct 26, 2026 at 09:14:37PM +0000, Bradley Morgan wrote:
>> On 26 October 2026 18:30:10 GMT, Tom Rini <trini@konsulko.com> wrote:
>> >On Mon, Oct 26, 2026 at 05:27:05PM +0000, Bradley Morgan wrote:
>> >> On 26 October 2026 17:23:32 GMT, Tom Rini <trini@konsulko.com> wrote:
>> >> >On Mon, Oct 26, 2026 at 05:00:19PM +0000, Bradley Morgan wrote:
>> >> >> On 26 October 2026 16:58:47 GMT, Bradley Morgan
>> ><brads@mainlining.org>
>> >> >> wrote:
>> >> >> >On 26 October 2026 16:55:09 GMT, Tomas Alvarez Vanoli
>> >> >> ><tomas.alvarez-vanoli@hitachienergy.com> wrote:
>> >> >> >>>>
>> >> >> >>>>Hi all,
>> >> >> >>>>
>> >> >> >>>>Just a data point from a user: we are using U-Boot on a T1040
>> >(QorIQ
>> >> >/
>> >> >> >>>>mpc85xx) in a product, and we intend to keep up with mainline
>as
>> >> >much
>> >> >> >as
>> >> >> >>>>we can. We'd appreciate PowerPC support staying in tree, and
>> >we're
>> >> >> >happy
>> >> >> >>>>to test patches on T1040 hardware and report back.
>> >> >> >>>>We run u-boot in 32-bit mode (not sure if it is possible to
>use
>> >> >64-bit)
>> >> >> >>>>and
>> >> >> >>>>linux in 64-bit.
>> >> >> >>>>I am in the process of bringing it up to our 2025.07 branch
>and
>> >> >> >>>>potentially
>> >> >> >>>>mainlining as much as possible. We have some remnants of it
>under
>> >> >> >>>>`board/keymile/kmcent2`.
>> >> >> >>>
>> >> >> >>>Would T1042D4RDB affect you?
>> >> >> >>
>> >> >> >>Not directly from what I see in the code, as long as the shared
>> >code
>> >> >with
>> >> >> >>ARCH_T1040 is kept. Sorry for the false alarm, just wanted to
>> >report
>> >> >that
>> >> >> >>there are dozens of us using powerpc :)
>> >> >> >
>> >> >> >What you could do if you would like is to test the whole series
>to
>> >see
>> >> >if
>> >> >> >it unaffected you.
>> >> >> >
>> >> >> >
>> >> >> >Btw tom I had a idea: you merge Vincent's bug fix and my
>maintainers
>> >> >> >patch,you make a PowerPC custodian tree, and I handle the series
>and
>> >> >the
>> >> >> >naks and stuff and the comments.
>> >> >>
>> >> >> and btw yes I'll make the pr with the finished patches so you can
>> >merge
>> >> >> them cleanly
>> >> >
>> >> >Trees are relatively cheap, but I'm not sure we need another one
>either
>> >> >for the subset of formerly-Freescale and not-QorIQ PowerPC parts.
>Since
>> >> >I added you to the fsl-qoriq tree, you can also just pick up the
>> >> >outstanding fixes and your maintainer patches (and leave dropping
>stuff
>> >> >for now, as this series shows today we're just getting people having
>a
>> >> >chance to see and reply to this stuff) and send me a PR. Thanks.
>> >>
>> >> Hi, sorry, I didn't clarify enough, so I had a chat for some people
>from
>> >> the open src firmware slack, yes?
>> >>
>> >> And here is their answer
>> >>
>> >> "Ah, Peng Fan maintains the FSL QoriQ tree:
>> >> https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq
>> >>
>> >> That is the vendor one though.
>> >> So yea, I'd go with a general PowerPC tree.
>> >>
>> >> Also because QoriQ is both Arm and PPC series. :sweat_smile:"
>> >>
>> >> And even my slopper suggests the tree, for sanity purposes :D
>> >
>> >Fine, trees are still cheap. There's u-boot-ppc now. But please keep in
>> >mind everything else I said, thanks.
>>
>> Thx.
>>
>> Question: will you merge the maintainers patch on this PR, so I can
>focus on my add-on maintainers patch and the removals?
>
>Lets hold off on the removals a bit more, as I was saying.
That's not what I meant
I meant, you'd merge ONLY the maintainers patch in this PR
Then, I'll go and take up the removals, and give it say, a couple weeks to
let it marinade, and give it responses THEN submit a PR with the removals
in it. Then happy days.
Or I could also take the maintainers patch with me too...
>
>
--- Thanks!
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-26 21:27 ` Bradley Morgan
@ 2026-10-27 0:19 ` Tom Rini
2026-10-27 0:25 ` Bradley Morgan
0 siblings, 1 reply; 23+ messages in thread
From: Tom Rini @ 2026-10-27 0:19 UTC (permalink / raw)
To: Bradley Morgan
Cc: Tomas Alvarez Vanoli, Vincent Jardin, Peng Fan,
u-boot@lists.u-boot-project.org, Sinan Akman, Bryan Brattlof,
Holger Brunck
[-- Attachment #1: Type: text/plain, Size: 4427 bytes --]
On Mon, Oct 26, 2026 at 09:27:05PM +0000, Bradley Morgan wrote:
> On 26 October 2026 21:19:52 GMT, Tom Rini <trini@konsulko.com> wrote:
> >On Mon, Oct 26, 2026 at 09:14:37PM +0000, Bradley Morgan wrote:
> >> On 26 October 2026 18:30:10 GMT, Tom Rini <trini@konsulko.com> wrote:
> >> >On Mon, Oct 26, 2026 at 05:27:05PM +0000, Bradley Morgan wrote:
> >> >> On 26 October 2026 17:23:32 GMT, Tom Rini <trini@konsulko.com> wrote:
> >> >> >On Mon, Oct 26, 2026 at 05:00:19PM +0000, Bradley Morgan wrote:
> >> >> >> On 26 October 2026 16:58:47 GMT, Bradley Morgan
> >> ><brads@mainlining.org>
> >> >> >> wrote:
> >> >> >> >On 26 October 2026 16:55:09 GMT, Tomas Alvarez Vanoli
> >> >> >> ><tomas.alvarez-vanoli@hitachienergy.com> wrote:
> >> >> >> >>>>
> >> >> >> >>>>Hi all,
> >> >> >> >>>>
> >> >> >> >>>>Just a data point from a user: we are using U-Boot on a T1040
> >> >(QorIQ
> >> >> >/
> >> >> >> >>>>mpc85xx) in a product, and we intend to keep up with mainline
> >as
> >> >> >much
> >> >> >> >as
> >> >> >> >>>>we can. We'd appreciate PowerPC support staying in tree, and
> >> >we're
> >> >> >> >happy
> >> >> >> >>>>to test patches on T1040 hardware and report back.
> >> >> >> >>>>We run u-boot in 32-bit mode (not sure if it is possible to
> >use
> >> >> >64-bit)
> >> >> >> >>>>and
> >> >> >> >>>>linux in 64-bit.
> >> >> >> >>>>I am in the process of bringing it up to our 2025.07 branch
> >and
> >> >> >> >>>>potentially
> >> >> >> >>>>mainlining as much as possible. We have some remnants of it
> >under
> >> >> >> >>>>`board/keymile/kmcent2`.
> >> >> >> >>>
> >> >> >> >>>Would T1042D4RDB affect you?
> >> >> >> >>
> >> >> >> >>Not directly from what I see in the code, as long as the shared
> >> >code
> >> >> >with
> >> >> >> >>ARCH_T1040 is kept. Sorry for the false alarm, just wanted to
> >> >report
> >> >> >that
> >> >> >> >>there are dozens of us using powerpc :)
> >> >> >> >
> >> >> >> >What you could do if you would like is to test the whole series
> >to
> >> >see
> >> >> >if
> >> >> >> >it unaffected you.
> >> >> >> >
> >> >> >> >
> >> >> >> >Btw tom I had a idea: you merge Vincent's bug fix and my
> >maintainers
> >> >> >> >patch,you make a PowerPC custodian tree, and I handle the series
> >and
> >> >> >the
> >> >> >> >naks and stuff and the comments.
> >> >> >>
> >> >> >> and btw yes I'll make the pr with the finished patches so you can
> >> >merge
> >> >> >> them cleanly
> >> >> >
> >> >> >Trees are relatively cheap, but I'm not sure we need another one
> >either
> >> >> >for the subset of formerly-Freescale and not-QorIQ PowerPC parts.
> >Since
> >> >> >I added you to the fsl-qoriq tree, you can also just pick up the
> >> >> >outstanding fixes and your maintainer patches (and leave dropping
> >stuff
> >> >> >for now, as this series shows today we're just getting people having
> >a
> >> >> >chance to see and reply to this stuff) and send me a PR. Thanks.
> >> >>
> >> >> Hi, sorry, I didn't clarify enough, so I had a chat for some people
> >from
> >> >> the open src firmware slack, yes?
> >> >>
> >> >> And here is their answer
> >> >>
> >> >> "Ah, Peng Fan maintains the FSL QoriQ tree:
> >> >> https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq
> >> >>
> >> >> That is the vendor one though.
> >> >> So yea, I'd go with a general PowerPC tree.
> >> >>
> >> >> Also because QoriQ is both Arm and PPC series. :sweat_smile:"
> >> >>
> >> >> And even my slopper suggests the tree, for sanity purposes :D
> >> >
> >> >Fine, trees are still cheap. There's u-boot-ppc now. But please keep in
> >> >mind everything else I said, thanks.
> >>
> >> Thx.
> >>
> >> Question: will you merge the maintainers patch on this PR, so I can
> >focus on my add-on maintainers patch and the removals?
> >
> >Lets hold off on the removals a bit more, as I was saying.
>
> That's not what I meant
>
> I meant, you'd merge ONLY the maintainers patch in this PR
>
> Then, I'll go and take up the removals, and give it say, a couple weeks to
> let it marinade, and give it responses THEN submit a PR with the removals
> in it. Then happy days.
>
>
> Or I could also take the maintainers patch with me too...
Yes, please pick up the maintainers patches and if I follow what's in
Peng's queue right, there are a few other powerpc fixes out there.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-27 0:19 ` Tom Rini
@ 2026-10-27 0:25 ` Bradley Morgan
2026-10-27 0:34 ` Tom Rini
0 siblings, 1 reply; 23+ messages in thread
From: Bradley Morgan @ 2026-10-27 0:25 UTC (permalink / raw)
To: Tom Rini
Cc: Tomas Alvarez Vanoli, Vincent Jardin, Peng Fan,
u-boot@lists.u-boot-project.org, Sinan Akman, Bryan Brattlof,
Holger Brunck
On 27 October 2026 00:19:23 GMT, Tom Rini <trini@konsulko.com> wrote:
>On Mon, Oct 26, 2026 at 09:27:05PM +0000, Bradley Morgan wrote:
>> On 26 October 2026 21:19:52 GMT, Tom Rini <trini@konsulko.com> wrote:
>> >On Mon, Oct 26, 2026 at 09:14:37PM +0000, Bradley Morgan wrote:
>> >> On 26 October 2026 18:30:10 GMT, Tom Rini <trini@konsulko.com> wrote:
>> >> >On Mon, Oct 26, 2026 at 05:27:05PM +0000, Bradley Morgan wrote:
>> >> >> On 26 October 2026 17:23:32 GMT, Tom Rini <trini@konsulko.com>
>wrote:
>> >> >> >On Mon, Oct 26, 2026 at 05:00:19PM +0000, Bradley Morgan wrote:
>> >> >> >> On 26 October 2026 16:58:47 GMT, Bradley Morgan
>> >> ><brads@mainlining.org>
>> >> >> >> wrote:
>> >> >> >> >On 26 October 2026 16:55:09 GMT, Tomas Alvarez Vanoli
>> >> >> >> ><tomas.alvarez-vanoli@hitachienergy.com> wrote:
>> >> >> >> >>>>
>> >> >> >> >>>>Hi all,
>> >> >> >> >>>>
>> >> >> >> >>>>Just a data point from a user: we are using U-Boot on a
>T1040
>> >> >(QorIQ
>> >> >> >/
>> >> >> >> >>>>mpc85xx) in a product, and we intend to keep up with
>mainline
>> >as
>> >> >> >much
>> >> >> >> >as
>> >> >> >> >>>>we can. We'd appreciate PowerPC support staying in tree,
>and
>> >> >we're
>> >> >> >> >happy
>> >> >> >> >>>>to test patches on T1040 hardware and report back.
>> >> >> >> >>>>We run u-boot in 32-bit mode (not sure if it is possible to
>> >use
>> >> >> >64-bit)
>> >> >> >> >>>>and
>> >> >> >> >>>>linux in 64-bit.
>> >> >> >> >>>>I am in the process of bringing it up to our 2025.07 branch
>> >and
>> >> >> >> >>>>potentially
>> >> >> >> >>>>mainlining as much as possible. We have some remnants of it
>> >under
>> >> >> >> >>>>`board/keymile/kmcent2`.
>> >> >> >> >>>
>> >> >> >> >>>Would T1042D4RDB affect you?
>> >> >> >> >>
>> >> >> >> >>Not directly from what I see in the code, as long as the
>shared
>> >> >code
>> >> >> >with
>> >> >> >> >>ARCH_T1040 is kept. Sorry for the false alarm, just wanted to
>> >> >report
>> >> >> >that
>> >> >> >> >>there are dozens of us using powerpc :)
>> >> >> >> >
>> >> >> >> >What you could do if you would like is to test the whole
>series
>> >to
>> >> >see
>> >> >> >if
>> >> >> >> >it unaffected you.
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >Btw tom I had a idea: you merge Vincent's bug fix and my
>> >maintainers
>> >> >> >> >patch,you make a PowerPC custodian tree, and I handle the
>series
>> >and
>> >> >> >the
>> >> >> >> >naks and stuff and the comments.
>> >> >> >>
>> >> >> >> and btw yes I'll make the pr with the finished patches so you
>can
>> >> >merge
>> >> >> >> them cleanly
>> >> >> >
>> >> >> >Trees are relatively cheap, but I'm not sure we need another one
>> >either
>> >> >> >for the subset of formerly-Freescale and not-QorIQ PowerPC parts.
>> >Since
>> >> >> >I added you to the fsl-qoriq tree, you can also just pick up the
>> >> >> >outstanding fixes and your maintainer patches (and leave dropping
>> >stuff
>> >> >> >for now, as this series shows today we're just getting people
>having
>> >a
>> >> >> >chance to see and reply to this stuff) and send me a PR. Thanks.
>> >> >>
>> >> >> Hi, sorry, I didn't clarify enough, so I had a chat for some
>people
>> >from
>> >> >> the open src firmware slack, yes?
>> >> >>
>> >> >> And here is their answer
>> >> >>
>> >> >> "Ah, Peng Fan maintains the FSL QoriQ tree:
>> >> >> https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq
>> >> >>
>> >> >> That is the vendor one though.
>> >> >> So yea, I'd go with a general PowerPC tree.
>> >> >>
>> >> >> Also because QoriQ is both Arm and PPC series. :sweat_smile:"
>> >> >>
>> >> >> And even my slopper suggests the tree, for sanity purposes :D
>> >> >
>> >> >Fine, trees are still cheap. There's u-boot-ppc now. But please keep
>in
>> >> >mind everything else I said, thanks.
>> >>
>> >> Thx.
>> >>
>> >> Question: will you merge the maintainers patch on this PR, so I can
>> >focus on my add-on maintainers patch and the removals?
>> >
>> >Lets hold off on the removals a bit more, as I was saying.
>>
>> That's not what I meant
>>
>> I meant, you'd merge ONLY the maintainers patch in this PR
>>
>> Then, I'll go and take up the removals, and give it say, a couple weeks
>to
>> let it marinade, and give it responses THEN submit a PR with the
>removals
>> in it. Then happy days.
>>
>>
>> Or I could also take the maintainers patch with me too...
>
>Yes, please pick up the maintainers patches and if I follow what's in
>Peng's queue right, there are a few other powerpc fixes out there.
>
Not in this PR, maybe any on lore that stands out?
lx2160a is ARM
nbxv3 is arm too.
I'll look harder (maybe I'm wrong) soon
>
--- Thanks!
https://lore.kernel.org/all/EE579805-42F2-4C58-B752-F28779EEB717@grrlz.net/
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
2026-10-27 0:25 ` Bradley Morgan
@ 2026-10-27 0:34 ` Tom Rini
0 siblings, 0 replies; 23+ messages in thread
From: Tom Rini @ 2026-10-27 0:34 UTC (permalink / raw)
To: Bradley Morgan
Cc: Tomas Alvarez Vanoli, Vincent Jardin, Peng Fan,
u-boot@lists.u-boot-project.org, Sinan Akman, Bryan Brattlof,
Holger Brunck
[-- Attachment #1: Type: text/plain, Size: 5165 bytes --]
On Tue, Oct 27, 2026 at 12:25:48AM +0000, Bradley Morgan wrote:
> On 27 October 2026 00:19:23 GMT, Tom Rini <trini@konsulko.com> wrote:
> >On Mon, Oct 26, 2026 at 09:27:05PM +0000, Bradley Morgan wrote:
> >> On 26 October 2026 21:19:52 GMT, Tom Rini <trini@konsulko.com> wrote:
> >> >On Mon, Oct 26, 2026 at 09:14:37PM +0000, Bradley Morgan wrote:
> >> >> On 26 October 2026 18:30:10 GMT, Tom Rini <trini@konsulko.com> wrote:
> >> >> >On Mon, Oct 26, 2026 at 05:27:05PM +0000, Bradley Morgan wrote:
> >> >> >> On 26 October 2026 17:23:32 GMT, Tom Rini <trini@konsulko.com>
> >wrote:
> >> >> >> >On Mon, Oct 26, 2026 at 05:00:19PM +0000, Bradley Morgan wrote:
> >> >> >> >> On 26 October 2026 16:58:47 GMT, Bradley Morgan
> >> >> ><brads@mainlining.org>
> >> >> >> >> wrote:
> >> >> >> >> >On 26 October 2026 16:55:09 GMT, Tomas Alvarez Vanoli
> >> >> >> >> ><tomas.alvarez-vanoli@hitachienergy.com> wrote:
> >> >> >> >> >>>>
> >> >> >> >> >>>>Hi all,
> >> >> >> >> >>>>
> >> >> >> >> >>>>Just a data point from a user: we are using U-Boot on a
> >T1040
> >> >> >(QorIQ
> >> >> >> >/
> >> >> >> >> >>>>mpc85xx) in a product, and we intend to keep up with
> >mainline
> >> >as
> >> >> >> >much
> >> >> >> >> >as
> >> >> >> >> >>>>we can. We'd appreciate PowerPC support staying in tree,
> >and
> >> >> >we're
> >> >> >> >> >happy
> >> >> >> >> >>>>to test patches on T1040 hardware and report back.
> >> >> >> >> >>>>We run u-boot in 32-bit mode (not sure if it is possible to
> >> >use
> >> >> >> >64-bit)
> >> >> >> >> >>>>and
> >> >> >> >> >>>>linux in 64-bit.
> >> >> >> >> >>>>I am in the process of bringing it up to our 2025.07 branch
> >> >and
> >> >> >> >> >>>>potentially
> >> >> >> >> >>>>mainlining as much as possible. We have some remnants of it
> >> >under
> >> >> >> >> >>>>`board/keymile/kmcent2`.
> >> >> >> >> >>>
> >> >> >> >> >>>Would T1042D4RDB affect you?
> >> >> >> >> >>
> >> >> >> >> >>Not directly from what I see in the code, as long as the
> >shared
> >> >> >code
> >> >> >> >with
> >> >> >> >> >>ARCH_T1040 is kept. Sorry for the false alarm, just wanted to
> >> >> >report
> >> >> >> >that
> >> >> >> >> >>there are dozens of us using powerpc :)
> >> >> >> >> >
> >> >> >> >> >What you could do if you would like is to test the whole
> >series
> >> >to
> >> >> >see
> >> >> >> >if
> >> >> >> >> >it unaffected you.
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >Btw tom I had a idea: you merge Vincent's bug fix and my
> >> >maintainers
> >> >> >> >> >patch,you make a PowerPC custodian tree, and I handle the
> >series
> >> >and
> >> >> >> >the
> >> >> >> >> >naks and stuff and the comments.
> >> >> >> >>
> >> >> >> >> and btw yes I'll make the pr with the finished patches so you
> >can
> >> >> >merge
> >> >> >> >> them cleanly
> >> >> >> >
> >> >> >> >Trees are relatively cheap, but I'm not sure we need another one
> >> >either
> >> >> >> >for the subset of formerly-Freescale and not-QorIQ PowerPC parts.
> >> >Since
> >> >> >> >I added you to the fsl-qoriq tree, you can also just pick up the
> >> >> >> >outstanding fixes and your maintainer patches (and leave dropping
> >> >stuff
> >> >> >> >for now, as this series shows today we're just getting people
> >having
> >> >a
> >> >> >> >chance to see and reply to this stuff) and send me a PR. Thanks.
> >> >> >>
> >> >> >> Hi, sorry, I didn't clarify enough, so I had a chat for some
> >people
> >> >from
> >> >> >> the open src firmware slack, yes?
> >> >> >>
> >> >> >> And here is their answer
> >> >> >>
> >> >> >> "Ah, Peng Fan maintains the FSL QoriQ tree:
> >> >> >> https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq
> >> >> >>
> >> >> >> That is the vendor one though.
> >> >> >> So yea, I'd go with a general PowerPC tree.
> >> >> >>
> >> >> >> Also because QoriQ is both Arm and PPC series. :sweat_smile:"
> >> >> >>
> >> >> >> And even my slopper suggests the tree, for sanity purposes :D
> >> >> >
> >> >> >Fine, trees are still cheap. There's u-boot-ppc now. But please keep
> >in
> >> >> >mind everything else I said, thanks.
> >> >>
> >> >> Thx.
> >> >>
> >> >> Question: will you merge the maintainers patch on this PR, so I can
> >> >focus on my add-on maintainers patch and the removals?
> >> >
> >> >Lets hold off on the removals a bit more, as I was saying.
> >>
> >> That's not what I meant
> >>
> >> I meant, you'd merge ONLY the maintainers patch in this PR
> >>
> >> Then, I'll go and take up the removals, and give it say, a couple weeks
> >to
> >> let it marinade, and give it responses THEN submit a PR with the
> >removals
> >> in it. Then happy days.
> >>
> >>
> >> Or I could also take the maintainers patch with me too...
> >
> >Yes, please pick up the maintainers patches and if I follow what's in
> >Peng's queue right, there are a few other powerpc fixes out there.
> >
>
> Not in this PR, maybe any on lore that stands out?
>
> lx2160a is ARM
>
> nbxv3 is arm too.
>
> I'll look harder (maybe I'm wrong) soon
Maybe I'm just mis-remembering, thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread
end of thread, other threads:[~2026-10-27 0:34 UTC | newest]
Thread overview: 23+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-10-22 7:34 [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1 Peng Fan
2026-10-22 14:42 ` Bradley Morgan
2026-10-26 8:43 ` Vincent Jardin
2026-10-26 9:25 ` Bradley Morgan
2026-10-26 14:20 ` Tom Rini
2026-10-26 14:58 ` Bradley Morgan
2026-10-26 16:19 ` Vincent Jardin
2026-10-26 16:26 ` Bradley Morgan
2026-10-26 16:39 ` Tomas Alvarez Vanoli
2026-10-26 16:42 ` Bradley Morgan
2026-10-26 16:55 ` Tomas Alvarez Vanoli
2026-10-26 16:58 ` Bradley Morgan
2026-10-26 17:00 ` Bradley Morgan
2026-10-26 17:23 ` Tom Rini
2026-10-26 17:27 ` Bradley Morgan
2026-10-26 18:30 ` Tom Rini
2026-10-26 21:14 ` Bradley Morgan
2026-10-26 21:19 ` Tom Rini
2026-10-26 21:27 ` Bradley Morgan
2026-10-27 0:19 ` Tom Rini
2026-10-27 0:25 ` Bradley Morgan
2026-10-27 0:34 ` Tom Rini
2026-10-26 17:19 ` Tom Rini
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.