From: Finn Thain <fthain@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
stable@vger.kernel.org
Subject: [PATCH v3 0/3] m68k: Bug fix and cleanup for framebuffer debug console
Date: Fri, 28 Mar 2025 09:39:55 +1100 [thread overview]
Message-ID: <cover.1743115195.git.fthain@linux-m68k.org> (raw)
This series has a bug fix for the early bootconsole as well as some
related efficiency improvements and cleanup.
The relevant code is subject to CONSOLE_DEBUG, which is presently only
used with CONFIG_MAC. To test this series (in qemu-system-m68k, for example)
it's helpful to enable CONFIG_EARLY_PRINTK and
CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER and boot with
kernel parameters 'console=ttyS0 earlyprintk keep_bootcon'.
---
Changed since v1:
- Solved problem with line wrap while scrolling.
- Added two additional patches.
Changed since v2:
- Adopted addq and subq as suggested by Andreas.
Finn Thain (3):
m68k: Fix lost column on framebuffer debug console
m68k: Avoid pointless recursion in debug console rendering
m68k: Remove unused "cursor home" code from debug console
arch/m68k/kernel/head.S | 73 +++++++++++++++++++++--------------------
1 file changed, 37 insertions(+), 36 deletions(-)
--
2.45.3
next reply other threads:[~2025-03-27 22:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 22:39 Finn Thain [this message]
2025-03-27 22:39 ` [PATCH v3 2/3] m68k: Avoid pointless recursion in debug console rendering Finn Thain
2025-07-06 10:27 ` Geert Uytterhoeven
2025-03-27 22:39 ` [PATCH v3 1/3] m68k: Fix lost column on framebuffer debug console Finn Thain
2025-07-06 10:27 ` Geert Uytterhoeven
2025-03-27 22:39 ` [PATCH v3 3/3] m68k: Remove unused "cursor home" code from " Finn Thain
2025-07-06 10:27 ` Geert Uytterhoeven
2025-06-11 15:11 ` [PATCH v3 0/3] m68k: Bug fix and cleanup for framebuffer " Stan Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1743115195.git.fthain@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).