From: Finn Thain <fthain@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: stable@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Fix lost column on framebuffer debug console
Date: Tue, 18 Mar 2025 09:48:40 +1100 (AEDT) [thread overview]
Message-ID: <b504b718-0ffb-ff28-0c91-badf92282b32@linux-m68k.org> (raw)
In-Reply-To: <c03e60ce451e4ccdf12830192080be4262b31b89.1741338535.git.fthain@linux-m68k.org>
Please disregard the patch below. Further testing shows that it does not
completely solve the problem. In particular, when line-wrap also produces
vertical scrolling. I think the recursive console_putc call may have to
go.
On Fri, 7 Mar 2025, Finn Thain wrote:
> When long lines are sent to the debug console on the framebuffer, the
> right-most column is lost. Fix this by subtracting 1 from the column
> count before comparing it with console_struct_cur_column, as the latter
> counts from zero.
>
> Linewrap is handled with a recursive call to console_putc, but this
> alters the console_struct_cur_row global. Store the old value before
> calling console_putc, so the right-most character gets rendered on the
> correct line.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@vger.kernel.org
> Signed-off-by: Finn Thain <fthain@linux-m68k.org>
> ---
> arch/m68k/kernel/head.S | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/arch/m68k/kernel/head.S b/arch/m68k/kernel/head.S
> index 852255cf60de..9c60047764d0 100644
> --- a/arch/m68k/kernel/head.S
> +++ b/arch/m68k/kernel/head.S
> @@ -3583,11 +3583,16 @@ L(console_not_home):
> movel %a0@(Lconsole_struct_cur_column),%d0
> addql #1,%a0@(Lconsole_struct_cur_column)
> movel %a0@(Lconsole_struct_num_columns),%d1
> + subil #1,%d1
> cmpl %d1,%d0
> jcs 1f
> - console_putc #'\n' /* recursion is OK! */
> + /* recursion will alter console_struct so load d1 register first */
> + movel %a0@(Lconsole_struct_cur_row),%d1
> + console_putc #'\n'
> + jmp 2f
> 1:
> movel %a0@(Lconsole_struct_cur_row),%d1
> +2:
>
> /*
> * At this point we make a shift in register usage
>
prev parent reply other threads:[~2025-03-17 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 9:08 [PATCH] m68k: Fix lost column on framebuffer debug console Finn Thain
2025-03-17 22:48 ` Finn Thain [this message]
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=b504b718-0ffb-ff28-0c91-badf92282b32@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).