<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/include/configs, branch v2026.04-rc2</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/include/configs?h=v2026.04-rc2</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/include/configs?h=v2026.04-rc2'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2026-02-02T20:25:48Z</updated>
<entry>
<title>Merge patch series "m68k: Add support for QEMU virt machine"</title>
<updated>2026-02-02T20:25:48Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-02-02T20:24:56Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1de103fc29761fa729dffaa15d0cfb2766be05e4'/>
<id>urn:sha1:1de103fc29761fa729dffaa15d0cfb2766be05e4</id>
<content type='text'>
Kuan-Wei Chiu &lt;visitorckw@gmail.com&gt; says:

Add support for the QEMU 'virt' machine on the m68k architecture. The
QEMU virt machine models a generic system utilizing Goldfish virtual
peripherals and is capable of emulating various classic 68k CPUs.

Currently, U-Boot's m68k architecture support focuses on ColdFire
variants. This series expands support to include the classic M680x0
architecture, implementing the necessary exception vectors, startup
code, and a bootinfo parser compatible with the QEMU interface.

Drivers for Goldfish peripherals (TTY, Timer, RTC) and the QEMU
Virtual System Controller (sysreset) are also added to enable serial
console, timekeeping, and system reset functionality.

The implementation has been verified on QEMU targeting the M68040 CPU,
confirming successful hardware initialization and boot to the U-Boot
command shell. Additionally, the CI configuration was verified locally
using gitlab-ci-local "qemu_m68k_virt test.py", resulting in
PASS qemu_m68k_virt test.py.

Link: https://lore.kernel.org/r/20260107201838.3448806-1-visitorckw@gmail.com
[trini: Re-sort MAINTAINERS entries]
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>board: Add QEMU m68k virt board support</title>
<updated>2026-02-02T20:24:41Z</updated>
<author>
<name>Kuan-Wei Chiu</name>
<email>visitorckw@gmail.com</email>
</author>
<published>2026-01-07T20:18:35Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=516afc8f76268fceb98f6b891a653484e931b26a'/>
<id>urn:sha1:516afc8f76268fceb98f6b891a653484e931b26a</id>
<content type='text'>
Add support for the QEMU 'virt' machine on the m68k architecture. This
board emulates a generic machine based on the Motorola 68040 CPU
equipped with Goldfish virtual peripherals.

Introduce the necessary board configuration and initialization
infrastructure. The implementation includes logic to parse the QEMU
bootinfo interface, enabling dynamic detection of system RAM size to
adapt to the virtual machine's configuration.

Enable the Goldfish TTY driver for serial console output. Additionally,
enable Goldfish RTC and timer drivers to support real-time clock
functionality and nanosecond-resolution delays. Include comprehensive
documentation covering build instructions and usage examples.

Signed-off-by: Kuan-Wei Chiu &lt;visitorckw@gmail.com&gt;
Tested-by: Daniel Palmer &lt;daniel@0x0f.com&gt;
Reviewed-by: Simon Glass &lt;simon.glass@canonical.com&gt;
</content>
</entry>
<entry>
<title>Merge patch series "arm: mach-k3: j721s2: Provide a way to obtain boot device for non SPLs"</title>
<updated>2026-02-02T19:39:52Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-02-02T19:39:52Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=4b287e0a3ae4ab3159584cb5ae12c9b470716be8'/>
<id>urn:sha1:4b287e0a3ae4ab3159584cb5ae12c9b470716be8</id>
<content type='text'>
This series from Dominik Haller &lt;d.haller@phytec.de&gt; provides a way for
TI K3 platforms to determine their boot device outside of SPL and then
adds support for the PHYTEC phyCORE-AM68x/TDA4x SoM.

Link: https://lore.kernel.org/r/20260116014116.767555-1-d.haller@phytec.de
</content>
</entry>
<entry>
<title>board: phytec: Add PHYTEC phyCORE-AM68x/TDA4x SoM</title>
<updated>2026-02-02T19:39:42Z</updated>
<author>
<name>Dominik Haller</name>
<email>d.haller@phytec.de</email>
</author>
<published>2026-01-16T01:41:12Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e9fa9a2fe325e7030f01f3bd62bf4d571ec6a6c1'/>
<id>urn:sha1:e9fa9a2fe325e7030f01f3bd62bf4d571ec6a6c1</id>
<content type='text'>
Add support for the PHYTEC phyCORE-AM68x/TDA4x (J721S2 family) SoM.

Supported features:
- 4GB LPDDR4 RAM
- eMMC
- SD-Card
- Ethernet
- OSPI
- AVS
- debug UART

Signed-off-by: Dominik Haller &lt;d.haller@phytec.de&gt;
Reviewed-by: Wadim Egorov &lt;w.egorov@phytec.de&gt;
</content>
</entry>
<entry>
<title>armv7: Add CPLD support via IFC to the ls1021a-iot board.</title>
<updated>2026-01-28T06:26:50Z</updated>
<author>
<name>Mateus Lima Alves</name>
<email>mateuslima.ti@gmail.com</email>
</author>
<published>2026-01-26T16:05:19Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=424b324165ea0343598c5a8b52591ea504dcde52'/>
<id>urn:sha1:424b324165ea0343598c5a8b52591ea504dcde52</id>
<content type='text'>
This patch adds CPLD support via IFC to the ls1021a-iot board.

Signed-off-by: Mateus Lima Alves &lt;mateuslima.ti@gmail.com&gt;
</content>
</entry>
<entry>
<title>arm: Remove remainder of ARCH_ORION5X</title>
<updated>2026-01-21T18:05:15Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-01-15T21:27:22Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=b9d4a17b90fd3b98023da5cf3b45a1a5058fb0ad'/>
<id>urn:sha1:b9d4a17b90fd3b98023da5cf3b45a1a5058fb0ad</id>
<content type='text'>
With commit 5663b137e682 ("arm: Remove edminiv2 board") the last
ARCH_ORION5X platform was removed. Remove the rest of the architecture
code which is now unused.

Reviewed-by: Tony Dinh &lt;mibodhi@gmail.com&gt;
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'xilinx-for-v2026.04-rc1-v2' of https://source.denx.de/u-boot/custodians/u-boot-microblaze</title>
<updated>2026-01-19T19:08:48Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-01-19T19:08:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=55ca2110d74f8e5a594aecc11ce4103dc73e9e02'/>
<id>urn:sha1:55ca2110d74f8e5a594aecc11ce4103dc73e9e02</id>
<content type='text'>
AMD/Xilinx/FPGA changes for v2026.04-rc1 v2

microblaze:
- Fix spl_boot_list order

versal2:
- Fix EMMC distro boot setup
- Align distro boot variables with memory layout

zynqmp-phy:
- Sync with Linux kernel driver

zynqmp:
- Add verify_auth command
- DT sync
- Add placing variables to FAT/EXT4
- Enable PCIe driver by default

pcie - xilinx-nwl:
- Fix Link down crash

ufs:
- Align clock/reset with DT binding

# -----BEGIN PGP SIGNATURE-----
#
# iHUEABYIAB0WIQSXAixArPbWpRanWW+rB/7wTvUR9QUCaW3p3wAKCRCrB/7wTvUR
# 9VkwAP4jPRALpM34VpTimNe/iwigIx8hAHxbvkUU0oJ/DW6W8AEAhCSL+ydgreuv
# kKCyNiOF1sm8IrOh4TdtMIFn37d4Dwg=
# =AkKK
# -----END PGP SIGNATURE-----
# gpg: Signature made Mon 19 Jan 2026 02:22:55 AM CST
# gpg:                using EDDSA key 97022C40ACF6D6A516A7596FAB07FEF04EF511F5
# gpg: Can't check signature: No public key
</content>
</entry>
<entry>
<title>ARM: imx: Enable boot from both USB controllers on all i.MX6 DHSOM</title>
<updated>2026-01-17T18:00:42Z</updated>
<author>
<name>Marek Vasut</name>
<email>marex@nabladev.com</email>
</author>
<published>2026-01-10T20:34:19Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=9a030f4c5151056f16f6c2300de7a0ad6f2a812e'/>
<id>urn:sha1:9a030f4c5151056f16f6c2300de7a0ad6f2a812e</id>
<content type='text'>
Enable boot from both USB controller 0 and 1 on all i.MX6 DHSOM.

Signed-off-by: Marek Vasut &lt;marex@nabladev.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'qcom-main' of https://source.denx.de/u-boot/custodians/u-boot-snapdragon</title>
<updated>2026-01-16T21:14:37Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-01-16T21:14:37Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ff498a3c5efb424accc1d825cc45cede2540ca13'/>
<id>urn:sha1:ff498a3c5efb424accc1d825cc45cede2540ca13</id>
<content type='text'>
We have been getting a lot more patches from Qualcomm engineers, largely
focusing on IoT, router, and automotive platforms (those with QCS, IPQ,
and SA prefixes specifically).

Quite a variety of changes here:
- Watchdog overflow fix
- Hardcoded fastboot buffer addresses for a few board (hoppefully
  temporary until fastboot is updated to read $fastboot_addr_r)
- Enable memory protection (MMU_MGPROT) for ARCH_SNAPDRAGON
- pinctrl support for the QCS615 soc
- various USB/phy fixes including phy config for msm8996/qcs615
- mmc and i2c clock configuration fixes
- significant fixes for rpmh and regulator drivers
- added config fragment for pixel devices
- sa8775p clock fixes
- support for "flattened" dwc3 DT that recently landed upstream for
  sc7280 (qcs6490) and a few other platforms
</content>
</entry>
<entry>
<title>configs: mt8365: remove empty header file</title>
<updated>2026-01-16T19:04:16Z</updated>
<author>
<name>David Lechner</name>
<email>dlechner@baylibre.com</email>
</author>
<published>2026-01-07T19:58:58Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8241bd6a82e181bbb3b7f4440a52205a40e2e617'/>
<id>urn:sha1:8241bd6a82e181bbb3b7f4440a52205a40e2e617</id>
<content type='text'>
Remove the empty include/configs/mt8365.h header file as it is not
needed. The Kconfig entry that referenced it is also removed.

Signed-off-by: David Lechner &lt;dlechner@baylibre.com&gt;
</content>
</entry>
</feed>
