<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/arch/m68k, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<entry>
<title>m68k: set proper u-boot image size for initial boot</title>
<updated>2026-05-04T20:19:49+00:00</updated>
<author>
<name>Angelo Dureghello</name>
<email>angelo@kernel-space.org</email>
</author>
<published>2026-03-30T07:09:54+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=44684aabc2983cabab7056cf5840a04c97c42b1f'/>
<id>44684aabc2983cabab7056cf5840a04c97c42b1f</id>
<content type='text'>
There is a value of 256K hardcoded as u-boot image size. This
produce bank tty as soon as the image size grows over the limit.
Fix it by using value preset by CONFIG_SYS_MONITOR_LEN.

Signed-off-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
There is a value of 256K hardcoded as u-boot image size. This
produce bank tty as soon as the image size grows over the limit.
Fix it by using value preset by CONFIG_SYS_MONITOR_LEN.

Signed-off-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>m68k: mcf5441x: create stub to use imx drivers</title>
<updated>2026-05-04T20:19:49+00:00</updated>
<author>
<name>Angelo Dureghello</name>
<email>angelo@kernel-space.org</email>
</author>
<published>2026-03-23T23:14:24+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=07d824e5bbc17ecc00a5b0afd24963d27a3fca94'/>
<id>07d824e5bbc17ecc00a5b0afd24963d27a3fca94</id>
<content type='text'>
Some NXP imx hardware ip module as the esdhc controller are exactly the
same in some new ColdFire cpus. For the specific case, mcf5441x needs to
use the existing fsl_esdhc_imx.c driver for the esdhc device.

Create a stub to be able to use NXP "imx" serie drivers as the
fsl_esdhc_imx in the ColdFire architecture.

Signed-off-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Some NXP imx hardware ip module as the esdhc controller are exactly the
same in some new ColdFire cpus. For the specific case, mcf5441x needs to
use the existing fsl_esdhc_imx.c driver for the esdhc device.

Create a stub to be able to use NXP "imx" serie drivers as the
fsl_esdhc_imx in the ColdFire architecture.

Signed-off-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>m68k: dts: stmark2: enable esdhc</title>
<updated>2026-05-04T20:19:49+00:00</updated>
<author>
<name>Angelo Dureghello</name>
<email>angelo@kernel-space.org</email>
</author>
<published>2026-03-23T21:19:25+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=81b7e4da508c9557880204c070c56f5ff5048bb7'/>
<id>81b7e4da508c9557880204c070c56f5ff5048bb7</id>
<content type='text'>
Enable esdhc device.

Signed-off-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Enable esdhc device.

Signed-off-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>m68k: dts: mcf5441x: add mmc device for mcf5441x</title>
<updated>2026-05-04T20:19:48+00:00</updated>
<author>
<name>Angelo Dureghello</name>
<email>angelo@kernel-space.org</email>
</author>
<published>2026-03-23T21:12:12+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=988c9833709cf78b7e91c525ef0cfd4aba2c0adc'/>
<id>988c9833709cf78b7e91c525ef0cfd4aba2c0adc</id>
<content type='text'>
Add mmc support for the mcf5441x family. There is only one esdhc
controller for this cpu family.

Signed-off-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add mmc support for the mcf5441x family. There is only one esdhc
controller for this cpu family.

Signed-off-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge patch series "serial: goldfish: Add debug uart support"</title>
<updated>2026-04-14T19:25:32+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-04-14T19:25:32+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8f6a5932aaec6f3fbe5fad1b28aa2322374a42f6'/>
<id>8f6a5932aaec6f3fbe5fad1b28aa2322374a42f6</id>
<content type='text'>
This series from Daniel Palmer &lt;daniel@0x0f.com&gt; improves debug UART
support on QEMU on M68K by adding debug uart support to the serial
driver.

Link: https://lore.kernel.org/r/20260309105110.672832-1-daniel@0x0f.com
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This series from Daniel Palmer &lt;daniel@0x0f.com&gt; improves debug UART
support on QEMU on M68K by adding debug uart support to the serial
driver.

Link: https://lore.kernel.org/r/20260309105110.672832-1-daniel@0x0f.com
</pre>
</div>
</content>
</entry>
<entry>
<title>m68k: m680x0: Initialise the debug uart</title>
<updated>2026-04-14T19:25:13+00:00</updated>
<author>
<name>Daniel Palmer</name>
<email>daniel@0x0f.com</email>
</author>
<published>2026-03-09T10:51:09+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=2df4926ca4f215d9b1a91d0c02c6fef49c845837'/>
<id>2df4926ca4f215d9b1a91d0c02c6fef49c845837</id>
<content type='text'>
Once the stack is ready we can init the debug uart to help
with debugging so do that.

Signed-off-by: Daniel Palmer &lt;daniel@0x0f.com&gt;
Acked-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Once the stack is ready we can init the debug uart to help
with debugging so do that.

Signed-off-by: Daniel Palmer &lt;daniel@0x0f.com&gt;
Acked-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge patch series "bootm: Clean up arch-specific, pre-OS clean-up"</title>
<updated>2026-03-19T00:36:50+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-03-19T00:36:50+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=eb00c710508d09b2a3b9aca75dd18280f1304703'/>
<id>eb00c710508d09b2a3b9aca75dd18280f1304703</id>
<content type='text'>
Simon Glass &lt;sjg@chromium.org&gt; says:

Each arch does something slightly different before booting the OS. Some
archs even do different things depending on the CPU type.

It is quite hard to know what actually happens in the final milliseconds
before the OS boot.

This series attempts to start cleaning up U-Boot in this area.

The basic intent is to create a new bootm_final() function which can be
called by all archs. It provides some flags for a couple of necessary
variations but otherwise it is generic.

All architectures are converted over to use this new function.

board_quiesce_devices() is moved into bootm_final() so that all archs
benefit from it.

This series fixes a bug in device_remove() is fixed where removing a
parent with specialised flags (e.g. DM_REMOVE_ACTIVE_ALL) could leave
children activated, since they do not match the flags. This fixes is
needed to avoid bootm_final() causing test failures on sandbox.

Future work could take this a little further:
- Convert EFI loader to use the same function
- Improve comments for cleanup_before_linux() across architectures
- Support fake-run tracing on all archs

Link: https://lore.kernel.org/r/20260306023638.2678886-1-sjg@chromium.org
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Simon Glass &lt;sjg@chromium.org&gt; says:

Each arch does something slightly different before booting the OS. Some
archs even do different things depending on the CPU type.

It is quite hard to know what actually happens in the final milliseconds
before the OS boot.

This series attempts to start cleaning up U-Boot in this area.

The basic intent is to create a new bootm_final() function which can be
called by all archs. It provides some flags for a couple of necessary
variations but otherwise it is generic.

All architectures are converted over to use this new function.

board_quiesce_devices() is moved into bootm_final() so that all archs
benefit from it.

This series fixes a bug in device_remove() is fixed where removing a
parent with specialised flags (e.g. DM_REMOVE_ACTIVE_ALL) could leave
children activated, since they do not match the flags. This fixes is
needed to avoid bootm_final() causing test failures on sandbox.

Future work could take this a little further:
- Convert EFI loader to use the same function
- Improve comments for cleanup_before_linux() across architectures
- Support fake-run tracing on all archs

Link: https://lore.kernel.org/r/20260306023638.2678886-1-sjg@chromium.org
</pre>
</div>
</content>
</entry>
<entry>
<title>m68k: Call bootm_final()</title>
<updated>2026-03-18T19:17:34+00:00</updated>
<author>
<name>Simon Glass</name>
<email>simon.glass@canonical.com</email>
</author>
<published>2026-03-06T02:36:22+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3b4bd773e093e777d35f2d951d1868de1a3cc2f3'/>
<id>3b4bd773e093e777d35f2d951d1868de1a3cc2f3</id>
<content type='text'>
Add a call to bootm_final() before jumping to the kernel. This adds
the "Starting kernel" message, bootstage tracking,
board_quiesce_devices() and dm_remove_devices_active() which were not
previously called on m68k.

Signed-off-by: Simon Glass &lt;simon.glass@canonical.com&gt;
Acked-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
Tested-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
Acked-by: Kuan-Wei Chiu &lt;visitorckw@gmail.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add a call to bootm_final() before jumping to the kernel. This adds
the "Starting kernel" message, bootstage tracking,
board_quiesce_devices() and dm_remove_devices_active() which were not
previously called on m68k.

Signed-off-by: Simon Glass &lt;simon.glass@canonical.com&gt;
Acked-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
Tested-by: Angelo Dureghello &lt;angelo@kernel-space.org&gt;
Acked-by: Kuan-Wei Chiu &lt;visitorckw@gmail.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge patch series "led: remove legacy API"</title>
<updated>2026-03-18T19:13:57+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-03-18T19:13:57+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=28608c808774a39ec47d31353b141db547136e58'/>
<id>28608c808774a39ec47d31353b141db547136e58</id>
<content type='text'>
Quentin Schulz &lt;quentin.schulz@cherry.de&gt; says:

This migrates the last user of the legacy LED API, IMX233-OLinuXino and
net/bootp.c, to the modern LED framework.

I do have concern about being able to use BOOTP in SPL? In which case, I
should probably add an additional check on CONFIG_IS_ENABLED(LED) in
addition to IS_ENABLED(CONFIG_LED_BOOT)?

I haven't tested this as I do not own an IMX233-OLinuXino, so please
give this a try if you own this device.

Then, since there's no user left of this legacy API, it is entirely
removed.

Link: https://lore.kernel.org/r/20251120-legacy-led-removal-v1-0-369d44338358@cherry.de
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Quentin Schulz &lt;quentin.schulz@cherry.de&gt; says:

This migrates the last user of the legacy LED API, IMX233-OLinuXino and
net/bootp.c, to the modern LED framework.

I do have concern about being able to use BOOTP in SPL? In which case, I
should probably add an additional check on CONFIG_IS_ENABLED(LED) in
addition to IS_ENABLED(CONFIG_LED_BOOT)?

I haven't tested this as I do not own an IMX233-OLinuXino, so please
give this a try if you own this device.

Then, since there's no user left of this legacy API, it is entirely
removed.

Link: https://lore.kernel.org/r/20251120-legacy-led-removal-v1-0-369d44338358@cherry.de
</pre>
</div>
</content>
</entry>
<entry>
<title>led: remove legacy API</title>
<updated>2026-03-18T19:07:36+00:00</updated>
<author>
<name>Quentin Schulz</name>
<email>quentin.schulz@cherry.de</email>
</author>
<published>2025-11-20T12:48:06+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=fcbf81694c9399a71ac100b4de15089c3e09dd8c'/>
<id>fcbf81694c9399a71ac100b4de15089c3e09dd8c</id>
<content type='text'>
No user of the legacy LED API anymore (except Sunxi with the PinePhone
but that is now a Sunxi-specific implementation), so let's remove
anything related.

Signed-off-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
No user of the legacy LED API anymore (except Sunxi with the PinePhone
but that is now a Sunxi-specific implementation), so let's remove
anything related.

Signed-off-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
</pre>
</div>
</content>
</entry>
</feed>
