Linux Input/HID development
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org,
	Miro Kropacek <miro.kropacek@gmail.com>,
	linux-input <linux-input@vger.kernel.org>
Subject: Re: [PATCH 1/5] m68k: Fix atari mouse movement
Date: Sat, 15 Aug 2026 11:15:33 +1200	[thread overview]
Message-ID: <ef9e0128-6309-546a-715a-3e7eb476910e@gmail.com> (raw)
In-Reply-To: <CAMuHMdUDvsqT5t93-ZO413pwS3rPYPB1_uy+5iRHsii8CYTdgA@mail.gmail.com>

Hi Geert,

thanks for your review!

Am 14.08.2026 um 19:53 schrieb Geert Uytterhoeven:
> Hi Michael,
>
> CC linux-input
>
> On Fri, 14 Aug 2026 at 05:17, Michael Schmitz <schmitzmic@gmail.com> wrote:
>> From: Miro Kropacek <miro.kropacek@gmail.com>
>>
>> Kernels are built with -funsigned-char since version 6.2, resulting
>> in signed mouse position deltas getting misinterpreted as unsigned.
>>
>> Cast deltas passed in (unsigned) scancode buffer to correctly
>> interpret sign.
>>
>> Fixes: 3bc753c06dd02a35 ("kbuild: treat char as always unsigned")
>> Link: https://lists.debian.org/debian-68k/2026/08/msg00000.html
>> Signed-off-by: Miro Kropacek <miro.kropacek@gmail.com>
>> Reviewed-by: Michael Schmitz <schmitzmic@gmail.com>
>
> Since you're now in the path to upstream, you should add your SoB here
> (applies to all patches).
>
>> --- a/drivers/input/mouse/atarimouse.c
>> +++ b/drivers/input/mouse/atarimouse.c
>> @@ -70,9 +70,12 @@ static void atamouse_interrupt(char *buf)
>
> Alternative, you could change/restore the function's signature to take a
> "signed char *".

Agreed, but without a way to test this, I'd rather wait for Miro 
confirming that change also fixed the issue.

Cheers,

	Michael

>>         atari_mouse_buttons = buttons;
>>  #endif
>>
>> -       /* only relative events get here */
>> -       dx = buf[1];
>> -       dy = buf[2];
>> +       /* only relative events get here; the IKBD sends signed 8-bit
>> +        * deltas, and the kernel builds with -funsigned-char since 6.2,
>> +        * so an explicit signed cast is required
>> +        */
>> +       dx = (s8)buf[1];
>> +       dy = (s8)buf[2];
>>
>>         input_report_rel(atamouse_dev, REL_X, dx);
>>         input_report_rel(atamouse_dev, REL_Y, dy);
>
> Regardless:
> Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
> Gr{oetje,eeting}s,
>
>                         Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                 -- Linus Torvalds
>

  reply	other threads:[~2026-08-14 23:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260814031745.17140-1-schmitzmic@gmail.com>
     [not found] ` <20260814031745.17140-2-schmitzmic@gmail.com>
2026-08-14  7:53   ` [PATCH 1/5] m68k: Fix atari mouse movement Geert Uytterhoeven
2026-08-14 23:15     ` Michael Schmitz [this message]
2026-08-16  5:03       ` Michael Schmitz

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=ef9e0128-6309-546a-715a-3e7eb476910e@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=miro.kropacek@gmail.com \
    /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